d24503ca02
- Migrate all command files to use @include reference system - Consolidate shared patterns into new yml structure - Create central superclaude shared configuration files - Remove deprecated markdown files (MCP.md, PERSONAS.md, RULES.md) - Add new documentation structure in docs/ - Update installation script for new architecture - Add ROADMAP.md and VERSION files This completes the major architectural refactor to improve maintainability and reduce duplication across the SuperClaude command system. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2.1 KiB
Purpose: Safe application deployment with rollback
@include shared/universal-constants.yml#Universal_Legend
Command Execution
Execute: immediate. --plan→show plan first Legend: Generated based on symbols used in command Purpose: "[Action][Subject] in $ARGUMENTS"
Deploy application to env specified in $ARGUMENTS.
@include shared/flag-inheritance.yml#Universal_Always
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
Deployment modes:
--env: Specify target environment
- dev: Deploy→dev env for testing
- staging: Deploy→staging for pre-prod validation
- prod: Deploy→prod w/ all safety checks
--rollback: Revert→previous stable deployment | Maintain deployment history→audit trail | Verify rollback success w/ health checks
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
Deployment workflow:
- Validate→Check prerequisites & cfg 2. Build→Create artifacts 3. Test→Run smoke tests
- 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
@include shared/research-patterns.yml#Mandatory_Research_Flows
@include shared/docs-patterns.yml#Standard_Notifications
@include shared/universal-constants.yml#Standard_Messages_Templates