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
Getting Started: AI-Powered Creation
🚀 Recommended: Use Commands.com MCP with Claude
The fastest way to create high-quality commands and prompts is using our AI-powered MCP (Model Context Protocol) server with Claude Code.
1.
Install Commands.com MCP in Claude
2.
Ask Claude to analyze your repository and generate commands.yaml
3.
Push to GitHub and import to Commands.com
Content Quality Standards
AI Commands Excellence
✓ Must Have
- Clear purpose: Solve a specific AI task or workflow
- Claude Code compatible: Designed for AI assistant usage
- MCP requirements: Specify needed MCP servers clearly
- Documentation: Explain what the command achieves
- Examples: Show typical usage with Claude or other AI
- Reusable: Works across different projects and scenarios
- Safe defaults: Avoid destructive operations without confirmation
✗ Avoid
- Vague descriptions: Be specific about functionality
- Missing MCP info: Always list required MCP servers
- No validation: Commands should verify inputs
- Security risks: No exposed credentials or unsafe operations
- Overly complex: Break down into manageable steps
- Platform-specific: Aim for cross-platform compatibility
- Untested: Verify with Claude Code before publishing
Example: High-Quality AI Command
name: analyze-codebase-security
description: Comprehensive security audit of a codebase with vulnerability detection and fix suggestions
category: security-audit
requiredMcpServers:
- filesystem
- git
tags:
- security
- code-review
- vulnerability-detection
- best-practices
template: |
Perform a comprehensive security audit of the codebase in the current directory.
Focus on:
1. **Authentication & Authorization vulnerabilities**
- Weak authentication mechanisms
- Missing authorization checks
- Session management issues
2. **Input validation & sanitization**
- SQL injection risks
- XSS vulnerabilities
- Command injection possibilities
3. **Sensitive data exposure**
- Hardcoded credentials
- API keys in code
- Logging sensitive information
4. **Dependency vulnerabilities**
- Outdated packages with known CVEs
- Insecure dependencies
5. **Configuration security**
- Insecure defaults
- Missing security headers
- Weak cryptography
For each issue found:
- Explain the vulnerability
- Show the specific code location
- Provide severity rating (Critical/High/Medium/Low)
- Suggest concrete fixes with code examples
Generate a summary report with:
- Total issues by severity
- Priority recommendations
- Quick wins vs long-term improvementsAI 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: "Generate Unit Tests for React Components"
Description: "AI command that analyzes React components and generates comprehensive Jest unit tests with RTL. Includes edge cases, mocking strategies, and accessibility tests. Requires filesystem MCP."
Tags: react, testing, jest, rtl, code-generation, automation
✗ Poor Example
Title: "Test Generator"
Description: "Makes tests"
Tags: test, code
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.