$npx -y skills add kornpng/web-mvp-blueprint-kit --skill mvp-tech-designCreate 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.
| 1 | # MVP Technical Design |
| 2 | |
| 3 | Create `docs/TechBlueprint-[AppName].md`. |
| 4 | |
| 5 | ## Inputs |
| 6 | |
| 7 | Read `docs/BuildablePRD-*.md`. |
| 8 | |
| 9 | Ask only for missing technical level, desired maintenance responsibility, monthly budget, launch deadline, data sensitivity, and required integrations. |
| 10 | |
| 11 | ## Default Routes |
| 12 | |
| 13 | Evaluate: |
| 14 | |
| 15 | - No-code route |
| 16 | - AI-code route, usually a Web stack like Next.js + managed backend |
| 17 | - Developer route |
| 18 | |
| 19 | Choose the simplest route that satisfies the P0 features. |
| 20 | |
| 21 | ## Output |
| 22 | |
| 23 | Include: |
| 24 | |
| 25 | - Recommendation and route comparison |
| 26 | - Selected stack by layer |
| 27 | - Mermaid architecture |
| 28 | - Implementation notes by PRD feature |
| 29 | - Setup commands |
| 30 | - Security/privacy baseline |
| 31 | - Testing plan |
| 32 | - Cost and maintenance notes |
| 33 | |
| 34 | ## Rules |
| 35 | |
| 36 | - Prefer maintainable defaults over novelty. |
| 37 | - Verify current pricing or mark costs as "verify current vendor page". |
| 38 | - Do not recommend complex infrastructure unless the PRD requires it. |