vibe-deploylisted

Prepares a vibe-* project for deployment to 7 platforms: Railway, Render, Fly.io, Heroku, Vercel, Netlify, GitHub Pages. Detects stack automatically (FastAPI, Express, Next.js, Django, React, Vue, static). Patches source files (port binding to $PORT, adds /health endpoint, production CORS). Generates platform config files scoped per service — backend, web, worker. Inlines non-secret env vars directly in config files per service. Links database connections using platform-native syntax. Generates ENV_SETUP.md with per-service CLI commands for secrets only. Handles background workers and cron services if the project requires them. Optionally generates GitHub Actions CI/CD workflow. Produces DEPLOY.md step-by-step checklist. Triggers: deploy: railway, deploy: render, deploy: fly, deploy: heroku, deploy: vercel, deploy: netlify, deploy: github-pages.
aakashdhar/vibe-skill · ★ 7 · API & Backend · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Deploy Skill Prepares your project for deployment — config files, source patches, env vars, database provisioning, worker services, and a human checklist. Deployment itself is manual. Everything before that is automated. --- ## Supported platforms | Trigger | Platform | Best for | Database | |---|---|---|---| | `deploy: railway` | Railway | Full-stack, multi-service, APIs | PostgreSQL plugin | | `deploy: render` | Render | Full-stack, background workers | PostgreSQL service | | `deploy: fly` | Fly.io | Containers, globally distributed | Fly Postgres | | `deploy: heroku` | Heroku | Full-stack, legacy projects | Heroku Postgres add-on | | `deploy: vercel` | Vercel | Next.js, frontend, serverless | External only | | `deploy: netlify` | Netlify | Static, JAMstack, serverless functions | External only | | `deploy: github-pages` | GitHub Pages | Static sites only | None | --- ## Step 0 — Detect stack and services Read the project to understand what is being deployed: ```bash # Detect package managers and frameworks cat package.json 2>/dev/null cat requirements.txt 2>/dev/null cat pyproject.toml 2>/dev/null cat Dockerfile 2>/dev/null # Detect framework-specific files ls next.config.js next.config.ts 2>/dev/null ls manage.py 2>/dev/null ls main.py app.py 2>/dev/null ls vite.config.js vite.config.ts 2>/dev/null # Detect service directories ls -la 2>/dev/null # Read vibe context if available cat vibe/ARCHITECTURE.md 2>/dev/null cat CLAUDE.md 2>/dev/null # Check for e