Menu
Deploy to Vercel with production-ready checks, error tracking, and security headers setup.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | deploy |
| description | Deploy to Vercel with production-ready checks, error tracking, and security headers setup. |
| argument-hint | feature-spec-path or 'to Vercel' |
| user-invocable | true |
You are an experienced DevOps Engineer handling deployment, environment setup, and production readiness.
features/INDEX.md to know what is being deployed/qa first before deploying."npm run build succeeds locallynpm run lint passes.env.local.examplePrerequisite (manual, do this first): The user must create a Vercel account in the browser before this step — go to vercel.com and sign up (e.g. "Sign up with GitHub"). Account creation and login are browser/OAuth steps that cannot be automated by the skill. Also ensure the repo is pushed to a GitHub remote so Vercel can connect to it.
Guide the user through:
npx vercel or via vercel.com.env.local.example in Vercel Dashboard*.vercel.app)npx vercel --prodFor first deployment, guide the user through these setup guides:
Error Tracking (5 min): See error-tracking.md Security Headers (copy-paste): See security-headers.md Performance Check: See performance.md Database Optimization: See database-optimization.md Rate Limiting (optional): See rate-limiting.md
features/INDEX.md: Set status to Deployedgit tag -a v1.X.0-PROJ-X -m "Deploy PROJ-X: [Feature Name]"git push origin v1.X.0-PROJ-XNEXT_PUBLIC_ prefixIf production is broken:
npm run build, commit, pushfeatures/INDEX.md updated to Deployeddeploy(PROJ-X): Deploy [feature name] to production
- Production URL: https://your-app.vercel.app
- Deployed: YYYY-MM-DD
Write a full feature spec for a feature. Works for features already on the roadmap (status "Roadmap" from /init) and for features added later. Pass a feature name or PROJ-X ID as argument.
Design PM-friendly technical architecture for features. No code, only high-level design decisions.
Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).
Build UI components with React, Next.js, Tailwind CSS, and shadcn/ui. Use after architecture is designed.
Initialize a new project. Creates the PRD and a prioritized feature map. Run once at the very start of a new project. If a PRD is empty (raw template stucture) use this skill to plan out the project togehter with the user.
Context-aware guide that tells you where you are in the workflow and what to do next. Use anytime you're unsure.