ship-itlisted

# ship-it — go from "works on my machine" to "live on the internet" ## When to use this skill Trigger when the user wants deployment work done. Strong signals: - "deploy this", "ship it", "put this live" - "set up Vercel / Railway / Fly / Render" - "dockerize this", "write a Dockerfile" - "set up CI/CD for this repo" - "write the deploy GitHub Action" Do *not* trigger for: infrastructure architecture from scratch (use a real infra discussion first), DB provisioning (use `schema-architect` for schema, then a platform skill for hosting), or for production debugging after a deploy went wrong (read logs, don't redeploy blindly). ## The output contract A deployable artifact that: 1. **Has a single, clear deploy command** — `git push`, `vercel`, `flyctl deploy`, `railway up`, whatever the platform's idiom is. 2. **Boots in production-like config** — secrets via env, no hard-coded localhost, no dev-only middleware in the prod bundle. 3. **Has health checks** — the platform knows when the app is up. 4. **Has logs the team can read** — structured JSON, going somewhere they can find them. 5. **Documents rollback** — one command or one button. ## Workflow ### 1 — Match the app to the platform Ask 4 questions before recommending: 1. **What is it?** Static site, Next.js, API + DB, full-stack monolith, background workers, ML inference? 2. **Where's the data?** Already on managed DB (Supabase, Neon, PlanetScale)? Need one? Local SQLite that needs migrating to managed? 3. **What's