Initial commit: SuperClaude v4.0.0 configuration framework

- Core configuration files (CLAUDE.md, RULES.md, PERSONAS.md, MCP.md)
- 17 slash commands for specialized workflows
- 25 shared YAML resources for advanced configurations
- Installation script for global deployment
- 9 cognitive personas for specialized thinking modes
- MCP integration patterns for intelligent tool usage
- Token economy and ultracompressed mode support

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

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/commands/deploy.md

@@ -0,0 +1,68 @@
+## Legend
+| Symbol | Meaning | | Abbrev | Meaning |
+|--------|---------|---|--------|---------|
+| → | leads to | | env | environment |
+| & | and/with | | prod | production |
+| w/ | with | | perf | performance |
+
+Execute immediately. Add --plan flag if user wants to see plan first.
+
+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:
+- `/user:deploy --env staging --think` - Staging w/ coordination analysis
+- `/user:deploy --env prod --think-hard` - Prod w/ comprehensive planning
+- `/user: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
+4. 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
+
+Research requirements:
+- Infrastructure patterns→WebSearch cloud provider practices & docs
+- CI/CD patterns→verify w/ platform-specific guides | Monitoring→research observability patterns
+- Security hardening→check security guides & compliance | Never deploy on assumptions
+- All cfg cite sources: // Source: [deployment guide ref]
+
+Report Output:
+- Deployment logs: `.claudedocs/reports/deployment-<env>-<timestamp>.md`
+- Health checks: `.claudedocs/metrics/health-check-<timestamp>.md`
+- Ensure dirs: `mkdir -p .claudedocs/reports/ .claudedocs/metrics/`
+- Include location: "📄 Deployment report saved to: [path]"
+
+Deliverables: Deployment log w/ timestamps, health check results, perf metrics comparison, rollback instructions & verification report.