Skip to main content Skip to search

Creator Guidelines

Best practices for creating content that users love and trust

Why Create on Commands.com?

85% revenue share
Global developer audience
GitHub integration
Built-in analytics
Community feedback
Professional reputation building

Content Quality Standards

CLI Commands Excellence

✓ Must Have

  • Clear purpose: Solve a specific, real-world problem
  • Error handling: Check for prerequisites and fail gracefully
  • Safety checks: Warn before destructive operations
  • Documentation: Explain what the command does
  • Examples: Show typical usage scenarios
  • Cross-platform: Work on common environments
  • Idempotent: Safe to run multiple times

✗ Avoid

  • Hardcoded paths: Use variables or parameters
  • Silent failures: Always provide feedback
  • Destructive defaults: Require explicit confirmation
  • No comments: Explain complex logic
  • Single-use scripts: Make them reusable
  • Security risks: No exposed credentials or unsafe operations
  • Untested code: Verify it works as described
Example: High-Quality Command Structure
#!/bin/bash
# Docker cleanup script - Remove unused containers, images, and volumes
# Usage: ./docker-cleanup.sh [--dry-run] [--force]

set -euo pipefail # Exit on errors, undefined variables, pipe failures

# Configuration
DRY_RUN=false
FORCE=false

# Parse arguments
while [[ $# -gt 0 ]]; do
 case $1 in
 --dry-run)
 DRY_RUN=true
 shift
 ;;
 --force)
 FORCE=true
 shift
 ;;
 *)
 echo "Unknown option $1"
 exit 1
 ;;
 esac
done

# Check if Docker is running
if ! docker info >/dev/null 2>&1; then
 echo "Error: Docker is not running"
 exit 1
fi

# Show what will be cleaned
echo "Docker cleanup will remove:"
echo "- Stopped containers: $(docker ps -aq --filter status=exited | wc -l)"
echo "- Unused images: $(docker images -f dangling=true -q | wc -l)"
echo "- Unused volumes: $(docker volume ls -qf dangling=true | wc -l)"

if [[ "$FORCE" == "false" ]] && [[ "$DRY_RUN" == "false" ]]; then
 read -p "Continue? (y/N) " -n 1 -r
 echo
 if [[ ! $REPLY =~ ^[Yy]$ ]]; then
 echo "Cancelled"
 exit 0
 fi
fi

# Perform cleanup
if [[ "$DRY_RUN" == "true" ]]; then
 echo "DRY RUN - no changes made"
else
 echo "Cleaning up Docker resources..."
 docker system prune -f
 echo "Cleanup complete!"
fi

AI Prompts Excellence

✓ Must Have

  • Clear objective: Specific goal or output format
  • Context setting: Provide necessary background
  • Constraints: Define limitations and requirements
  • Examples: Show input/output samples
  • Role definition: Specify AI's expertise area
  • Output format: Structure the desired response
  • Tested results: Verify with multiple AI models

✗ Avoid

  • Vague requests: Be specific about what you want
  • No constraints: AI needs boundaries to be useful
  • Single-purpose: Make prompts adaptable
  • No examples: Show the AI what success looks like
  • Overly complex: Break down complex tasks
  • Harmful content: No malicious or unethical requests
  • Model-specific: Work across different AI platforms
Example: High-Quality Prompt Structure
You are an expert code reviewer with 10+ years of experience in software development. 

Your task is to review the provided code and give constructive feedback focused on:
1. Code quality and best practices
2. Security vulnerabilities
3. Performance optimizations
4. Maintainability improvements

**Input format:** Code snippet in any programming language
**Output format:** 
- Overall assessment (1-10 rating)
- Specific issues found (if any)
- Recommended improvements
- Security concerns (if any)
- Positive aspects worth highlighting

**Constraints:**
- Focus on actionable feedback
- Explain the "why" behind suggestions
- Prioritize critical issues first
- Keep suggestions practical and implementable

**Example:**
Input: [Python function with potential issues]
Output: 
Rating: 7/10
Issues found:
1. Missing input validation (line 5)
2. Potential SQL injection vulnerability (line 12)
...

Now review this code: {CODE_TO_REVIEW}

Pricing Your Content

Free Content Strategy

Great for building reputation and community engagement:

  • Simple, commonly-used commands
  • Educational examples and tutorials
  • Basic productivity shortcuts
  • Portfolio showcases
  • Community contributions

Premium Content Strategy

Specialized knowledge that saves significant time:

  • Complex automation workflows
  • Enterprise-grade solutions
  • Time-saving specialized tools
  • Industry-specific expertise
  • Advanced AI prompt engineering

Pricing Recommendations

$1-3

Simple utilities, quick fixes, basic prompts

$5-15

Comprehensive workflows, specialized tools

$20+

Enterprise solutions, complex automations

Making Your Content Discoverable

Titles & Descriptions

  • Descriptive titles: "Deploy React App to AWS S3" vs "Deploy Script"
  • Problem-focused: What specific issue does this solve?
  • Include tools: Mention Docker, Kubernetes, Python, etc.
  • Use keywords: Terms developers actually search for
  • Benefit-driven: Highlight time saved or value provided

Tags & Categories

  • Primary category: Choose the most relevant category
  • Technology tags: docker, kubernetes, python, react, etc.
  • Use case tags: deployment, backup, monitoring, testing
  • Platform tags: aws, gcp, azure, linux, macos
  • Difficulty tags: beginner, intermediate, advanced

Good vs Poor Examples

✓ Good Example

Title: "Backup MySQL Database with Compression and S3 Upload"

Description: "Automated script that creates compressed MySQL backups, validates integrity, and uploads to AWS S3 with retention policy. Includes error handling and email notifications."

Tags: mysql, backup, aws, s3, compression, automation

✗ Poor Example

Title: "Database Script"

Description: "Backs up database"

Tags: script, database

Gallery & Visual Content

Visual content dramatically increases engagement and helps users understand your commands before using them.

Screenshots & Images

  • Before/after states: Show the problem and solution
  • Terminal output: Actual command execution results
  • UI changes: If your command affects interfaces
  • File structures: Directory layouts and organization
  • Configuration examples: Settings and parameters

Animated GIFs

  • Step-by-step demos: Complete workflow execution
  • Interactive processes: Commands with user input
  • Real-time effects: Monitoring and live updates
  • Error handling: How failures are handled
  • Keep them short: 10-30 seconds max

Technical Requirements

  • • Supported formats: PNG, JPG, GIF, WebP
  • • Maximum file size: 5MB per image
  • • Recommended dimensions: 1200x800px or 16:9 ratio
  • • Use high contrast for code screenshots
  • • Include captions explaining what's shown

Building Your Creator Profile

Profile Optimization

  • Professional bio: Highlight your expertise areas
  • Contact information: Make it easy to reach you
  • Portfolio links: GitHub, LinkedIn, personal site
  • Specializations: What technologies you focus on
  • Regular updates: Keep publishing new content

Community Engagement

  • Respond to feedback: Engage with users who copy your commands
  • Iterate and improve: Update based on user suggestions
  • Help others: Comment on and improve other creators' work
  • Share knowledge: Participate in community discussions
  • Be consistent: Regular publishing builds audience

Pre-Publication Checklist

Technical Testing

Content Review

Creator Success Tips

High-Performing Content

  • • Solves real, frequent problems
  • • Has clear, demonstrable value
  • • Includes comprehensive documentation
  • • Regular updates and improvements

Building Audience

  • • Consistent publishing schedule
  • • Engage with user feedback
  • • Share on social media and blogs
  • • Collaborate with other creators

Creator Support & Resources

We're here to help you succeed as a creator. Get support, share ideas, and learn from other creators.

Join Creator Community Technical Documentation Start Creating