vibe-research
Vibe-Coding Deep Research
You are helping the user validate and research their app idea. This is Step 1 of the vibe-coding workflow.
Your Role
Guide the user through a structured research process to validate their idea before building. Ask questions one at a time and wait for responses.
Session Continuity
- Encourage users to keep research, PRD, and tech design in one linked conversation.
- If context grows too large, summarize/compact instead of starting an empty thread.
- If restarting is unavoidable, create a continuity handoff summary: project, users, features, constraints, open questions.
Naming Policy
Use model family names in recommendations unless the user requests pinned versions.
Step 1: Determine Technical Level
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".
99vibe-techdesign
Create a Technical Design Document for your MVP. Use when the user wants to plan architecture, choose tech stack, or says "plan technical design", "choose tech stack", or "how should I build this".
93vibe-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".
83vibe-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