| Skill | Description | Stages | Status |
|---|---|---|---|
🚀 vibe-coding-prod |
Full pre-build pipeline: PRD → TRD → App Flow → UI/UX → Schema → Impl. Plan | 6 | ✅ Stable |
"Vibe coding is fast. Production is forever. The 6-stage pipeline is the bridge."
The only skill you need to go from "I have an app idea" to a fully architected, production-ready build plan — without cutting corners.
┌─────────┐ ┌─────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ Stage 1 │───▶│ Stage 2 │───▶│ Stage 3 │───▶│ Stage 4 │───▶│ Stage 5 │───▶│ Stage 6 │
│ PRD │ │ TRD │ │ App Flow │ │ UI/UX │ │ Schema │ │ Impl. │
│ │ │ │ │ │ │ Brief │ │ │ │ Plan │
└─────────┘ └─────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
📋 Stage 1 — PRD (Product Requirements Document)
- User personas with pain points & goals
- MVP feature table with acceptance criteria
- Out-of-scope definition (prevents scope creep)
- Success metrics (measurable, not aspirational)
- Risk register with mitigations
⚙️ Stage 2 — TRD (Technical Requirements Document)
- Architecture pattern decision (Monolith / Microservices / Serverless)
- Full tech stack table with justifications
- API design spec (REST/GraphQL, auth, rate limits, error format)
- Non-functional requirements (p95 latency, uptime SLA, security)
- Infrastructure & environment matrix
🗺️ Stage 3 — App Flow
- Every user journey mapped (happy path + error paths)
- Complete screen/page inventory with routes & auth requirements
- State management scope map
- Edge cases: offline, session expired, rate limited, empty states
- Navigation structure (desktop + mobile)
🎨 Stage 4 — UI/UX Brief
- Complete design token system (colors, typography, spacing, shadows, radii)
- Component library spec with all interactive states
- Screen-by-screen wireframe briefs
- Motion & animation guidelines
- WCAG 2.1 AA accessibility requirements
- Dark mode strategy
🗄️ Stage 5 — Backend Schema
- Full table definitions (columns, types, constraints, indexes)
- Entity relationship overview
- Row-level security policies
- Caching strategy (Redis TTLs, invalidation rules)
- Migration strategy & naming conventions
- GDPR/data privacy & retention policies
📅 Stage 6 — Implementation Plan
- 3-phase roadmap: Foundation → MVP Core → Polish & Launch
- Per-feature task templates (backend + frontend + tests)
- Phase exit criteria (no fuzzy milestones)
- Launch gate checklist (security, performance, observability)
- Definition of Done applied to every task
- Post-launch monitoring cadence
Trigger the full pipeline:
"Vibe code me an app that does X"
"Build a production app for Y"
"I have an app idea: Z"
Trigger individual stages:
"Write me a PRD for..." → Stage 1
"Create a tech spec for..." → Stage 2
"Map out the app flow for..." → Stage 3
"Design the UI/UX brief for..." → Stage 4
"Create the backend schema for..." → Stage 5
"Write the implementation plan for..." → Stage 6
Every stage is validated against:
- ✅ Auth & authorization strategy
- ✅ Error states (not just happy paths)
- ✅ Mobile-first responsive layout
- ✅ API versioning
- ✅ Rate limiting & abuse prevention
- ✅ Data validation at every layer
- ✅ Observability: logging, monitoring, alerting
- ✅ CI/CD pipeline
- ✅ OWASP Top 10 mitigations
- ✅ GDPR / data privacy compliance
vibe-coding-prod/
├── SKILL.md ← Main orchestrator & stage router
└── references/
├── prd-trd.md ← Stages 1 & 2 templates + rules
├── app-flow.md ← Stage 3 templates + rules
├── uiux-brief.md ← Stage 4 templates + rules
├── backend-schema.md ← Stage 5 templates + rules
└── implementation-plan.md ← Stage 6 templates + rules
Have a skill to add? PRs are welcome.
- Fork the repo
- Create your skill folder:
your-skill-name/SKILL.md - Follow the skill structure above
- Submit a PR with a clear description
MIT © Dev Warriors
Built with ❤️ using Claude AI
Star ⭐ this repo if it helped you ship faster