Deploy
Auto-detects your deployment target from config files and deploys to any of 15 supported platforms. For advanced infrastructure needs, defers to DevOps.
What This Skill Does
Deploy reads your project config files (vercel.json, netlify.toml, fly.toml, etc.) to determine the target platform, validates prerequisites, and executes the deployment. No manual platform configuration needed for standard projects.
When to Use
- First deployment of a new project
- Deploying feature branches for preview
- Switching hosting providers
- Setting up production deployments with CI/CD
Supported Platforms
| Platform | Config File Detected |
|---|---|
| Vercel | vercel.json |
| Netlify | netlify.toml |
| Cloudflare Pages/Workers | wrangler.toml |
| Railway | railway.json |
| Fly.io | fly.toml |
| Render | render.yaml |
| Heroku | Procfile |
| GitHub Pages | gh-pages branch / Actions workflow |
| AWS | serverless.yml, cdk.json, amplify.yml |
| GCP | app.yaml, cloudbuild.yaml |
| DigitalOcean | .do/app.yaml |
| Vultr | Detected via CLI |
| Coolify | docker-compose.yml + Coolify reference |
| Dokploy | dokploy.yml |
| TOSE | tose.yaml |
Example Usage
/ck:deploy
/ck:deploy vercel
/ck:deploy fly
Workflow
- Auto-detect platform — scan config files in project root
- Validate prerequisites — check CLI installed, auth configured
- Pre-deploy checks — run build, verify env vars present
- Execute deployment — run platform-specific deploy command
- Report result — URL, deployment ID, and logs summary
Cost-Optimized Recommendations
When no platform config is detected, Deploy recommends the most cost-effective option based on your stack:
- Static sites: Cloudflare Pages (free, fast edge network)
- Node.js apps: Railway or Render (generous free tiers)
- Full-stack: Vercel (best Next.js integration)
- Containers: Fly.io (per-second billing)
For Kubernetes, Terraform, or complex multi-region setups, use DevOps instead.