vibe-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".
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. Keep planning in one ongoing conversation when possible. 2. If context is too large, summariz
What does the vibe-techdesign skill do?
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".
How do I install it?
Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From KhazP/vibe-coding-prompt-template, a repository with 2,806 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.