Documentation Index
Fetch the complete documentation index at: https://mintlify.com/vudovn/antigravity-kit/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The deployment-procedures skill teaches deployment principles and decision-making for safe production releases. It covers platform selection, pre-deployment verification, rollback strategies, and zero-downtime deployment patterns.
What This Skill Provides
- Platform Selection: Choosing the right deployment platform
- Pre-Deployment Checklist: Critical verifications before deploying
- 5-Phase Deployment Process: Prepare, Backup, Deploy, Verify, Confirm
- Rollback Strategies: When and how to rollback deployments
- Zero-Downtime Patterns: Rolling, Blue-Green, Canary deployments
- Emergency Procedures: Handling service outages
- Decision-Making Framework: Principles over scripts
Philosophy
Learn to THINK, not memorize scripts. Every deployment is unique. Understand the WHY behind each step and adapt procedures to your platform.
Decision Tree
What are you deploying?
│
├── Static site / JAMstack
│ └── Vercel, Netlify, Cloudflare Pages
│
├── Simple web app
│ ├── Managed → Railway, Render, Fly.io
│ └── Control → VPS + PM2/Docker
│
├── Microservices
│ └── Container orchestration
│
└── Serverless
└── Edge functions, Lambda
| Platform | Deployment Method |
|---|
| Vercel/Netlify | Git push, auto-deploy |
| Railway/Render | Git push or CLI |
| VPS + PM2 | SSH + manual steps |
| Docker | Image push + orchestration |
| Kubernetes | kubectl apply |
Pre-Deployment Principles
The 4 Verification Categories
| Category | What to Check |
|---|
| Code Quality | Tests passing, linting clean, reviewed |
| Build | Production build works, no warnings |
| Environment | Env vars set, secrets current |
| Safety | Backup done, rollback plan ready |
Pre-Deployment Checklist
The 5-Phase Deployment Process
1. PREPARE
└── Verify code, build, env vars
2. BACKUP
└── Save current state before changing
3. DEPLOY
└── Execute with monitoring open
4. VERIFY
└── Health check, logs, key flows
5. CONFIRM or ROLLBACK
└── All good? Confirm. Issues? Rollback.
Phase Principles
| Phase | Principle |
|---|
| Prepare | Never deploy untested code |
| Backup | Can’t rollback without backup |
| Deploy | Watch it happen, don’t walk away |
| Verify | Trust but verify |
| Confirm | Have rollback trigger ready |
Use Cases
When to Use This Skill
- Planning a production deployment
- Setting up deployment pipelines
- Handling deployment failures
- Implementing rollback procedures
- Choosing deployment strategies
Example Scenarios
- First Deploy: “Help me deploy this Next.js app to Vercel”
- Rollback: “The deployment broke production, how do I rollback?”
- Zero-Downtime: “Deploy without taking the site offline”
- Emergency: “Service is down after deployment”
Post-Deployment Verification
What to Verify
| Check | Why |
|---|
| Health endpoint | Service is running |
| Error logs | No new errors |
| Key user flows | Critical features work |
| Performance | Response times acceptable |
Verification Window
- First 5 minutes: Active monitoring
- 15 minutes: Confirm stable
- 1 hour: Final verification
- Next day: Review metrics
Rollback Principles
When to Rollback
| Symptom | Action |
|---|
| Service down | Rollback immediately |
| Critical errors | Rollback |
| Performance >50% degraded | Consider rollback |
| Minor issues | Fix forward if quick |
| Platform | Rollback Method |
|---|
| Vercel/Netlify | Redeploy previous commit |
| Railway/Render | Rollback in dashboard |
| VPS + PM2 | Restore backup, restart |
| Docker | Previous image tag |
| K8s | kubectl rollout undo |
Rollback Principles
- Speed over perfection: Rollback first, debug later
- Don’t compound errors: One rollback, not multiple changes
- Communicate: Tell team what happened
- Post-mortem: Understand why after stable
Zero-Downtime Deployment
Strategies
| Strategy | How It Works |
|---|
| Rolling | Replace instances one by one |
| Blue-Green | Switch traffic between environments |
| Canary | Gradual traffic shift |
Selection Principles
| Scenario | Strategy |
|---|
| Standard release | Rolling |
| High-risk change | Blue-green (easy rollback) |
| Need validation | Canary (test with real traffic) |
Emergency Procedures
Service Down Priority
- Assess: What’s the symptom?
- Quick fix: Restart if unclear
- Rollback: If restart doesn’t help
- Investigate: After stable
Investigation Order
| Check | Common Issues |
|---|
| Logs | Errors, exceptions |
| Resources | Disk full, memory |
| Network | DNS, firewall |
| Dependencies | Database, APIs |
Anti-Patterns to Avoid
| ❌ Don’t | ✅ Do |
|---|
| Deploy on Friday | Deploy early in week |
| Rush deployment | Follow the process |
| Skip staging | Always test first |
| Deploy without backup | Backup before deploy |
| Walk away after deploy | Monitor for 15+ min |
| Multiple changes at once | One change at a time |
Best Practices
- Small, frequent deploys over big releases
- Feature flags for risky changes
- Automate repetitive steps
- Document every deployment
- Review what went wrong after issues
- Test rollback before you need it
- server-management: Server operations and monitoring
- clean-code: Code quality before deployment
- lint-and-validate: Pre-deployment validation
- bash-linux: Server commands and scripts
- powershell-windows: Windows deployment scripts
Which Agents Use This Skill
- devops-engineer: Primary user for all deployment operations
Decision Checklist
Before deploying:
- Read, Glob, Grep: For checking deployment configs
- Bash: For deployment commands
Remember: Every deployment is a risk. Minimize risk through preparation, not speed.