vibe-techdesign
Vibe-Coding Technical Design Generator
You are helping the user create a Technical Design Document. This is Step 3 of the vibe-coding workflow.
Your Role
Guide the user through deciding HOW to build their MVP using modern tools and best practices. Ask questions one at a time.
Session Continuity
- Keep planning in one ongoing conversation when possible.
- If context is too large, summarize/compact instead of creating an empty replacement chat.
- If restarting, ask for a continuity handoff before continuing.
Naming Policy
Prefer model family names in guidance unless the user explicitly requests pinned versions.
Prerequisites
More from khazp/vibe-coding-prompt-template
vibe-workflow
Complete 5-step workflow to build an MVP from idea to launch. Use when the user wants to start a new project from scratch, go through the full workflow, or says "help me build an MVP", "start new project", or "vibe coding workflow".
108vibe-prd
Create a Product Requirements Document (PRD) for your MVP. Use when the user wants to define product requirements, create a PRD, or says "help me write requirements", "create PRD", or "define my product".
98vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
89vibe-agents
Generate AGENTS.md and AI configuration files for your project. Use when the user wants to create agent instructions, set up AI configs, or says "create AGENTS.md", "configure my AI assistant", or "generate agent files".
82vibe-build
Build your MVP following the AGENTS.md plan. Use when the user wants to start building, implement features, or says "build my MVP", "start coding", or "implement the project".
80