vibe-research
Skill1 starsChanged 8 months agoMITView on GitHub
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".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- KhazP/vibe-coding-prompt-templatetheir own version, first seen Sep 10, 2026
- Zhangyanbo/vibe-research-skilltheir own version, first seen Sep 2, 2026
- OpenOps-Studio/vibe-driven-devtheir own version, first seen Mar 30, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- KhazP/vibe-coding-prompt-template★ 3.1ksame name
- Zhangyanbo/vibe-research-skill★ 27same name
- OpenOps-Studio/vibe-driven-dev★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- vibe-agentsSkill
- vibe-buildSkill
- vibe-prdSkill
- vibe-techdesignSkill
- vibe-workflowSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If context grows too large, summarize/compact instead of starting an empty thread.
- Distinctive: line 19
If restarting is unavoidable, create a continuity handoff summary: project, users, features, constraints, open questions.
- Distinctive: line 23
Use model family names in recommendations unless the user requests pinned versions.
- Distinctive: line 38
Ask these questions ONE AT A TIME:
- Distinctive: line 77
After ALL questions are answered, summarize back to the user:
- Distinctive: line 93
After confirmation, generate a tailored research prompt.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
First, ask the user:
What's your technical background?
- A) Vibe-coder — Great ideas but limited coding experience
- B) Developer — Experienced programmer
- C) Somewhere in between — Know some basics, still learning
Step 2: Ask Questions Based on Level
If Level A (Vibe-coder):
Ask these questions ONE AT A TIME:
- "What's your app idea? Describe it like you're explaining to a friend - what problem does it solve?"
- "Who needs this most? Describe your ideal user (e.g., 'busy parents', 'small business owners')"
- "What's out there already? Name any similar apps or current solutions people use."
- "What would make someone choose YOUR app? What's the special sauce?"
- "What are the 3 absolute must-have features for launch? Just the essentials!"
- "How do you imagine people using this - phone app, website, or both?"
- "What's your timeline? Days, weeks, or months to launch?"
- "Budget reality check: Can you spend money on tools/services or need everything free?"
If Level B (Developer):
Ask these questions ONE AT A TIME:
- "What's your main research topic and project context? Include technical domain."
- "List 3-5 specific questions your research must answer. Be detailed."
- "What technical decisions will this research inform? (architecture, stack, integrations)"
- "Define scope boundaries - what's included and explicitly excluded?"
- "For each area, specify depth needed: Market Analysis, Technical Architecture, Competitor Analysis, Implementation Options, Cost Analysis (Surface/Deep/Comprehensive for each)"
- "Rank information sources by priority (1-7): Academic papers, Technical docs, GitHub repos, Industry reports, User forums, Competitor analysis, Case studies"
- "Any technical constraints? Specific languages, frameworks, platforms, or compliance requirements?"
- "What's the business context? Startup, enterprise, side project, or client work?"
If Level C (In-Between):
Ask these questions ONE AT A TIME:
- "Tell me about your project idea and your current skills. What can you code, and where do you need help?"
- "What problem are you solving? Who has this problem most?"
- "What specific things do you need to research? List both technical and business aspects."
- "What similar solutions exist? What do you like/dislike about them?"
- "Platform preferences: Web app, Mobile app, Desktop app, or Not sure?"
- "Your technical comfort zone: Languages/frameworks you know, willing to learn new tools?"
- "Timeline and success metrics? When do you want to launch and how will you measure success?"
- "Budget for tools and services? Free only, under $50/month, under $200/month, or flexible?"
Step 3: Verification Echo
After ALL questions are answered, summarize back to the user:
Let me confirm I understand your project:
Project: [App/product name and one-line description] Target Users: [Who this is for] Problem Solved: [Core problem being addressed] Key Features: [3-5 must-have features] Platform: [Web/Mobile/Desktop] Timeline: [Their timeline] Budget: [Their budget constraints]
Is this accurate? Should I adjust anything before creating your research prompt?
Step 4: Generate Research Prompt
After confirmation, generate a tailored research prompt. Use WebSearch to gather current information about:
- Competitors and market landscape
- Technical approaches and best practices
- Cost estimates for recommended tools
- Similar successful projects
Then write the research findings to docs/research-[AppName].txt in the project directory.
Output Format
The research document should include:
- Market Analysis - Competitors, market size, opportunity
- Technical Recommendations - Best approaches for their level
- Tool Recommendations - Specific tools with current pricing
- MVP Feature Prioritization - What to build first
- Risk Assessment - Potential challenges and mitigations
- Cost Estimates - Development and running costs
- Next Steps - Clear path forward
After Completion
Tell the user:
Your research is saved to
docs/research-[AppName].txt.Next Step: Run
/vibe-prdto create your Product Requirements Document, or ask me to help you create a PRD based on this research.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

