Mvp tech design
Codex-first Web MVP blueprint kit for turning app ideas into PRDs, technical plans, agent context, and build tickets.
npx -y skills add kornpng/web-mvp-blueprint-kit --skill mvp-tech-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Create a practical Technical Blueprint for a Web MVP. Use after a buildable PRD exists when the user needs a stack decision, No-code vs AI-code vs Developer route comparison, architecture, setup commands, security baseline, testing plan, and cost/maintenance notes.
SKILL.md
1.2 KB, as published. Nobody here has run it
MVP Technical Design
Create docs/TechBlueprint-[AppName].md.
Inputs
Read docs/BuildablePRD-*.md.
Ask only for missing technical level, desired maintenance responsibility, monthly budget, launch deadline, data sensitivity, and required integrations.
Default Routes
Evaluate:
- No-code route
- AI-code route, usually a Web stack like Next.js + managed backend
- Developer route
Choose the simplest route that satisfies the P0 features.
Output
Include:
- Recommendation and route comparison
- Selected stack by layer
- Mermaid architecture
- Implementation notes by PRD feature
- Setup commands
- Security/privacy baseline
- Testing plan
- Cost and maintenance notes
Rules
- Prefer maintainable defaults over novelty.
- Verify current pricing or mark costs as "verify current vendor page".
- Do not recommend complex infrastructure unless the PRD requires it.