deploy-pimp

Active router for ALL deployment and infrastructure requests — classifies by platform (Vercel, Cloudflare, Docker, GitHub Actions, Railway, GitHub Platform) and routes to the correct deploy skill. Use when deploying apps, configuring CI/CD, managing containers, or working with GitHub APIs.

Model	Source
sonnet	pack: deploy

Full Reference

If the request involves deployment, infrastructure, CI/CD, containers, cloud platforms, or GitHub APIs in ANY way — you MUST route through this skill FIRST.

This is not optional. This is not negotiable. You cannot skip this.

Deploy Pimp

The orchestration layer for all deployment and infrastructure expertise. Not documentation — an active router. Every deploy request flows through this routing table before any response.

Mandatory Announcement — FIRST OUTPUT before anything else:

┏━ 🚀 deploy-pimp ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ [one-line description of what request/routing] ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

No exceptions. Box frame first, then route.

Quick Context

The deploy pack covers the full deployment spectrum — from zero-config Next.js deploys on Vercel to Cloudflare Workers/D1 edge runtimes, Dockerized services, GitHub Actions CI/CD pipelines, Railway quick-deploys with managed Postgres, and GitHub’s platform APIs for releases, issues, and automation.

Routing Table

Classify the request. Invoke the matching skill. No response before invocation.

Request Pattern	Skill
Vercel deploy, vercel.json, domains, preview URLs, Edge Functions	`vercel`
Cloudflare Pages, Workers, D1, KV, R2, wrangler.toml	`cloudflare-pages-workers`
Docker, Dockerfile, docker-compose, containers, registries	`docker`
GitHub Actions, workflows, CI/CD, .github/workflows/	`github-actions`
Railway deploy, managed Postgres, environment variables, services	`railway`
GitHub API, Issues, Releases, webhooks, GitHub Apps	`github-platform`
”How do I deploy?” / “Which platform should I use?”	Decision matrix → route

Decision Matrix

When the user hasn’t specified a platform, classify their use case:

Signal	Route To
Next.js, React, SSR, ISR, Edge middleware	`vercel`
Workers, D1 database, KV store, edge compute, Cloudflare	`cloudflare-pages-workers`
Containerized app, microservices, self-hosted, Kubernetes	`docker`
Automate tests on push, build pipelines, scheduled jobs	`github-actions`
Quick deploy + managed Postgres, Node/Rails/Bun backend	`railway`
GitHub API automation, releases, issue management, webhooks	`github-platform`
”Which platform should I use?”	Ask one question: stack + budget

Shortcut rules:

Next.js + no infra preference → Vercel, no discussion
Workers/D1/KV → Cloudflare, no discussion
Containers → Docker, no discussion
Automate on git events → GitHub Actions, no discussion
Postgres + fast deploy, no DevOps overhead → Railway, no discussion
GitHub API/webhooks/releases → github-platform, no discussion

State Detection

Before routing, check project context:

stack.json → read deploy field for declared platform
vercel.json present → route to vercel directly
wrangler.toml present → route to cloudflare-pages-workers directly
Dockerfile or docker-compose.yml present → route to docker directly
.github/workflows/ directory present → route to github-actions directly
railway.json or railway.toml present → route to railway directly

State	Action
`stack.json` has `deploy` field	Route to that platform directly
`vercel.json` in root	Route to `vercel` directly
`wrangler.toml` in root	Route to `cloudflare-pages-workers` directly
`Dockerfile` in root	Route to `docker` directly
`.github/workflows/` exists	Route to `github-actions` directly
`railway.json` in root	Route to `railway` directly
Nothing detected	Apply decision matrix

Chaining Patterns

User Says	Chain
”Deploy my Next.js app”	`vercel`
”Set up a Worker with D1 database”	`cloudflare-pages-workers`
”Containerize my Express API”	`docker`
”Run tests on every PR”	`github-actions`
”Deploy a Node API with Postgres, no DevOps”	`railway`
”Create a GitHub release with changelogs”	`github-platform`
”Add CI to my Railway app”	`github-actions` → `railway`
”Deploy Docker container to Cloudflare”	`docker` → `cloudflare-pages-workers`
”Auto-deploy on merge to main”	`github-actions` → target platform skill
”Set up automated releases”	`github-actions` → `github-platform`

Hard Rules

Never respond about deployment/infra before invoking the target skill
No summarizing, planning to invoke, or explaining what you’re about to do
If unclear, ask ONE clarifying question, then route
The skill’s content has the verified facts — always defer to it
“How do I deploy?” is decision matrix territory — NEVER jump to implementation