Files
SuperClaude/.claude/commands/deploy.md
NomenAK 49c72808ee Remove all references to user: and project: prefixes
- Removed /user: prefix from all command examples
- Updated GitHub issue templates to remove /user: prefix
- Commands now use simple /command format without prefixes

This aligns with the project's decision to not use user:/project:
prefixes for commands.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-06-24 21:31:34 +02:00

5.7 KiB
Raw Blame History

Symbol Meaning Abbrev Meaning
leads to cfg configuration
& and/with impl implementation
w/ with perf performance
@ at/located ops operations
> greater than val validation
for all/every req requirements
exists/there is deps dependencies
therefore env environment
because db database
equivalent api interface
approximately docs documentation
📁 directory/path std standard
🔢 number/count def default
📝 text/string ctx context
setting/config err error
🎛 control/flags exec execution
🔧 configuration qual quality
📋 group/category rec recovery
🚨 critical/urgent sev severity
warning/caution resp response
🔄 retry/recovery esc escalation
success/fixed tok token
failure/error opt optimization
information UX user experience
fast/quick UI user interface
🐌 slow/delayed C critical
complete/done H high
📖 read operation M medium
edit operation L low
🗑 delete operation

Command Execution

Execute: immediate. --plan→show plan first Legend: Generated based on symbols used in command Purpose: "[Action][Subject] in $ARGUMENTS"

Universal Flags

--plan: "Show execution plan before running" --uc: "UltraCompressed mode (~70% token reduction)" --ultracompressed: "Alias for --uc" --think: "Multi-file analysis w/ context (4K tokens)" --think-hard: "Deep architectural analysis (10K tokens)" --ultrathink: "Critical system redesign (32K tokens)" --c7: "Enable Context7→library documentation lookup" --seq: "Enable Sequential→complex analysis & thinking" --magic: "Enable Magic→UI component generation" --pup: "Enable Puppeteer→browser automation & testing" --all-mcp: "Enable all MCP servers" --no-mcp: "Disable all MCP servers (native tools only)" --no-c7: "Disable Context7 specifically" --no-seq: "Disable Sequential thinking specifically" --no-magic: "Disable Magic UI builder specifically" --no-pup: "Disable Puppeteer specifically"

Deploy application to env specified in $ARGUMENTS.

Thinking flags (optional):

  • --think→multi-service deployment coordination
  • --think-hard→complex infrastructure & rollback planning
  • --ultrathink→complete deployment architecture & disaster recovery

Examples:

  • /deploy --env staging --think - Staging w/ coordination analysis
  • /deploy --env prod --think-hard - Prod w/ comprehensive planning
  • /deploy --rollback --ultrathink - Critical rollback w/ full impact analysis

Pre-deploy cleanup:

  • Clean previous artifacts | Remove dev-only files (.env.local, debug cfgs)
  • Validate prod cfg (no debug flags, correct URLs) | Clean old versions→free space

--env flag:

  • dev: Deploy→dev env for testing | staging: Deploy→staging for pre-prod validation
  • prod: Deploy→prod w/ all safety checks

--rollback flag:

  • Revert→previous stable deployment | Maintain deployment history→audit trail
  • Verify rollback success w/ health checks

Deployment workflow:

  1. Validate→Check prerequisites & cfg 2. Build→Create artifacts 3. Test→Run smoke tests
  2. Deploy→Execute strategy 5. Verify→Confirm health & functionality

Deployment strategies:

  • Blue-green: Two envs, switch traffic→zero downtime | Canary: Gradual rollout→% users
  • Rolling: Update instances sequentially w/ health checks

Pre-deployment checks:

  • Verify tests pass | Check deployment cfg | Ensure rollback plan exists
  • Validate env vars | Confirm DB migrations completed

Post-deployment:

  • Run health checks & smoke tests | Monitor error rates & perf
  • Check critical user journeys | Verify logging & monitoring | Ready→rollback if issues

Safety & Best Practices

Safety:

  • Always have rollback plan | Backups before deployment
  • Monitor key metrics during deployment | Gradual rollout→major changes
Mandatory_Research_Flows:
  External_Library_Research:
    Step_1: "Identify library/framework mentioned"
    Step_2: "Context7 lookup for official documentation"
    Step_3: "Verify API patterns and examples"
    Step_4: "Check version compatibility"
    Step_5: "Document findings in implementation"
    
  Pattern_Research:
    Step_1: "Search existing codebase for similar patterns"
    Step_2: "Magic component search if UI-related"
    Step_3: "WebSearch for official documentation"
    Step_4: "Validate approach with Sequential thinking"
    Step_5: "Document pattern choice rationale"
    
  API_Integration_Research:
    Step_1: "Official documentation lookup"
    Step_2: "Authentication requirements"
    Step_3: "Rate limiting and error handling"
    Step_4: "SDK availability and examples"
    Step_5: "Integration testing approach"
Standard_Notifications:
  Operation_Start: "▶ Starting {operation}"
  Operation_Complete: "✅ {operation} completed successfully"
  File_Created: "📝 Created: {file_path}"
  File_Updated: "✏ Updated: {file_path}"
  Report_Generated: "📄 Report saved to: {path}"
  Error_Occurred: "❌ {operation} failed: {reason}"
  Warning_Issued: "⚠ {warning_message}"
  Info_Message: " {information}"

Output_Notifications:
  Success_Format: "✅ {operation} completed in {duration}"
  Error_Format: "❌ {operation} failed: {error_details}"
  Warning_Format: "⚠ {warning}: {details}"
  Info_Format: " {message}"
  Progress_Format: "🔄 {operation}: {current}/{total} ({percentage}%)"

Success Messages

{operation} completed successfully 📝 Created: {file_path} ✏ Updated: {file_path} Task completed: {task_title}