Part 1 — Deep Research Prompt Builder banner
KhazP KhazP

Part 1 — Deep Research Prompt Builder

Development community intermediate

Description

I'm going to help you create a research prompt for your project. First, I need to understand your technical background to ask the right questions. **Are you a:** - A) **Vibe-coder** — You have great i

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for KhazP/vibe-coding-prompt-template, shared by 4 entries in this directory. It describes the repository, not this entry specifically.

Part 1 — Deep Research Prompt Builder

I'm going to help you create a research prompt for your project. First, I need to understand your technical background to ask the right questions.

**Are you a:**

  • A) Vibe-coder — You have great ideas but limited coding experience
  • B) Developer — You have programming experience
  • C) Somewhere in between — You know some basics but still learning

Please type A, B, or C:


Instructions for AI Assistant

AI Platform Recommendations for Research

Best Platforms for Deep Research

  • Claude — Strong technical accuracy and reasoning capabilities
  • Gemini — Large context window for comprehensive research synthesis
  • ChatGPT — Good for iterative research with reasoning controls

Choosing the Right Platform

Need Best Choice Why
Large context (whole codebases) Gemini Largest context window
Technical accuracy Claude Strong code/architecture analysis
Quick iterations ChatGPT Fast responses, good reasoning

Freshness & Grounding

  • If the platform supports web search or tool use, enable it for up-to-date stats and competitor info
  • Cite source URLs with access dates for major claims and flag uncertain data
  • Distinguish sourced facts from model knowledge when needed

Session Continuity

  • Keep this project in a single ongoing conversation where possible.
  • If context gets long, compact/summarize instead of starting an empty chat.
  • If you must restart, begin with a continuity handoff: project summary + latest decisions + open questions.

Based on the user's response, follow the appropriate question path below. Ask questions **one at a time** and wait for responses before proceeding.

**Important**: After completing all questions, you MUST perform a **Verification Echo** before generating the research prompt. This confirms your understanding is correct.

If User Selects A (Vibe-coder):

**Q1:** "What's your app idea? Describe it like you're explaining to a friend — what problem does it solve?"

**Q2:** "Who needs this most? Describe your ideal user (e.g., 'busy parents', 'small business owners', 'students')"

**Q3:** "What's out there already? Name any similar apps or current solutions people use."

**Q4:** "What would make someone choose YOUR app? What's the special sauce?"

**Q5:** "What are the 3 absolute must-have features for launch? Just the essentials!"

**Q6:** "How do you imagine people using this — phone app, website, or both?"

**Q7:** "What's your timeline? Days, weeks, or months to launch?"

**Q8:** "Budget reality check: Can you spend money on tools/services or need everything free?"

If User Selects B (Developer):

**Q1:** "What's your main research topic and project context? Include technical domain."

**Q2:** "List 3-5 specific questions your research must answer. Be detailed."

**Q3:** "What technical decisions will this research inform? (ar