vibe-techdesign
Skill1 starsChanged 8 months agoMITView on GitHub
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".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- KhazP/vibe-coding-prompt-templatetheir own version, first seen Sep 10, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- KhazP/vibe-coding-prompt-template★ 3.1ksame 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-researchSkill
- vibe-workflowSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Keep planning in one ongoing conversation when possible.
- Distinctive: line 18
If context is too large, summarize/compact instead of creating an empty replacement chat.
- Distinctive: line 19
If restarting, ask for a continuity handoff before continuing.
- Distinctive: line 23
Prefer model family names in guidance unless the user explicitly requests pinned versions.
- Very specific: line 27
Look for docs/PRD-*.md in the project - this is REQUIRED
- Very specific: line 29
If no PRD exists, suggest running /vibe-prd first
- Distinctive: line 33
Read the PRD and extract:
- Distinctive: line 105
After confirmation, generate a document tailored to their level.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Look for
docs/PRD-*.mdin the project - this is REQUIRED - Optionally check for
docs/research-*.txtfor additional context - If no PRD exists, suggest running
/vibe-prdfirst
Step 1: Load Context
Read the PRD and extract:
- Product name and core purpose
- Must-have features
- Target users and their tech level
- UI/UX requirements
- Budget and timeline constraints
Step 2: Determine Technical Level
Ask:
What's your technical background?
- A) Vibe-coder — Limited coding, using AI to build everything
- B) Developer — Experienced programmer
- C) Somewhere in between — Some basics, still learning
Step 3: Level-Specific Questions
Level A (Vibe-coder):
- "Based on your PRD, where should people use it? Web, Mobile app, Desktop, or Not sure?"
- "What's your coding situation? No-code only, AI writes all code, Learning basics, or Want to understand what's built?"
- "Budget for tools? Free only, up to $50/month, up to $200/month, or Flexible?"
- "How quickly to launch? ASAP (1-2 weeks), 1 month, 2-3 months, or No rush?"
- "What worries you most? Getting stuck, costs, security, wrong choices, or breaking things?"
- "Have you tried any tools yet? Name any and what you liked/disliked"
- "For your main feature, what's most important? Simple to build, works perfectly, looks amazing, or scales well?"
- "Do you want AI-powered features (chat, summarization)? If yes, list them and privacy constraints"
Level B (Developer):
- "Platform strategy and why?"
- "Preferred tech stack? Frontend, Backend, Database, Infrastructure, AI Integration"
- "Architecture pattern? Monolithic, Microservices, Serverless, Jamstack, or Full-stack framework"
- "Service choices? Auth, File storage, Payments, Email, Analytics"
- "AI coding tool preference? Claude Code, Gemini CLI, Cursor, VS Code + Copilot, Antigravity/equivalent agent-first IDE, or Mix?"
- "Development workflow? Git strategy, CI/CD, Testing priority, Environments"
- "Performance/scaling? Expected load, data volume, geographic distribution, real-time needs"
- "Security/compliance? Data sensitivity, compliance needs, auth method, API security"
- "AI/LLM features? Use cases, latency/cost constraints, data sensitivity"
Level C (In-Between):
- "Where should your app run? Web (easiest), Mobile, Both, or Help me decide?"
- "Your technical comfort: Languages you know, frameworks tried, want to learn?"
- "Building approach? No-code (fastest), Low-code with AI, Learn by doing, or Hire out?"
- "Feature complexity? Simple CRUD, real-time, file uploads, integrations, complex logic?"
- "Budget: Development tools, hosting, services - can you spend $X total?"
- "AI assistance preference? AI does everything, AI explains, AI helps when stuck, or Mix?"
- "Timeline reality: Hours/week available, launch date, beta test size?"
- "AI-powered features? List them and privacy constraints if yes"
Step 4: Verification Echo
After ALL questions:
Let me confirm your technical requirements:
Project: [App Name] from your PRD Platform: [Web/Mobile/Desktop] Tech Approach: [No-code/Low-code/Full-code] Key Decisions:
- Frontend: [Choice]
- Backend: [Choice]
- Database: [Choice] Budget: [$/month] Timeline: [Weeks/Months] Main Concern: [Their biggest worry]
Is this correct? Any adjustments before I create the Technical Design?
Step 5: Generate Technical Design
After confirmation, generate a document tailored to their level.
Tech Design Structure:
- Recommended Approach - Best option with justification
- Alternative Options - Comparison table with pros/cons
- Project Setup - Step-by-step checklist
- Feature Implementation - How to build each PRD feature
- Design Implementation - Templates, design system, responsiveness
- Database & Storage - Schema, setup, hosting
- AI Assistance Strategy - Which tool for what task
- Deployment Plan - Platform, steps, backup options
- Cost Breakdown - Development and production phases
- Scaling Path - What to do at 100, 1000, 10000 users
- Limitations - What this approach can't do
Write to docs/TechDesign-[AppName]-MVP.md.
After Completion
Tell the user:
Your Technical Design is saved to
docs/TechDesign-[AppName]-MVP.md.Sanity Check:
- Does the tech stack match your budget?
- Is the timeline realistic for the complexity?
- Are there security concerns addressed?
Next Step: Run
/vibe-agentsto generate your AGENTS.md and AI configuration files.
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.

