vibe-techdesign — Claude Code skill: what it does, how to install
Generates an MVP technical design document from agreed requirements, outlining architecture, tradeoffs, and handoff context without excess infra.
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a claude-codeWhat vibe-techdesign does
The skill evaluates requirements and reuses Handoff Context. Before suggesting replacements, it checks the existing repository stack using codebase search tools. It prompts you only for unresolved decisions rather than repeating established choices.
The architectural scope covers the primary user journey: component boundaries, data ownership, integration contracts, deployment target, and failure handling. Paid services, storage, authentication, and external APIs are included only when justified. Credentials and secrets stay out of the generated files.
The output writes to docs/TechDesign-[AppName]-MVP.md or a manifest-defined path. It ends with a structured Handoff Context containing constraints, choices, budget, and open questions for the next workflow stage.
What it helps with
- write an MVP technical architecture document for core user journeys
- define service boundaries and integration contracts
- document meaningful technical tradeoffs and recovery constraints
- pass architectural decisions and open questions to the next agent
Example prompts for the agent
- Write an MVP technical design from our agreed requirements
- Create docs/TechDesign-[AppName]-MVP.md in quick mode using the current stack
- Draft the architecture plan and document core integration contracts
How to install vibe-techdesign
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a claude-code2Manually: put the files in place
~/.claude/skills/vibe-techdesign/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vibe-techdesign/
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a codex2Manually: put the files in place
.agents/skills/vibe-techdesign/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a cursor2Manually: put the files in place
.cursor/skills/vibe-techdesign/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install KhazP/vibe-coding-prompt-template vibe-techdesign2Manually: put the files in place
.github/skills/vibe-techdesign/SKILL.md1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a gemini-cli2Platform CLI
gemini skills install https://github.com/KhazP/vibe-coding-prompt-template --path workflow/skills/vibe-techdesignManually: put the files in place
.devin/skills/vibe-techdesign/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vibe-techdesign
How to install vibe-techdesign in Claude Code?
Run npx skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign -a claude-code. The skill file will be placed at ~/.claude/skills/vibe-techdesign/SKILL.md.
Where does vibe-techdesign save the design document?
By default, it writes to docs/TechDesign-[AppName]-MVP.md or the path specified in your manifest configuration.
What tools does vibe-techdesign use?
It uses Read, Write, Glob, Grep, WebSearch, and AskUserQuestion to inspect the project and clarify key choices.
Source text
SKILL.md · MIT
--- name: vibe-techdesign description: "Write an MVP technical design from agreed requirements, including architecture choices and relevant tradeoffs." allowed-tools: Read, Write, Glob, Grep, WebSearch, AskUserQuestion --- # MVP technical design Read the agreed requirements and reuse Handoff Context. Inspect an existing project's stack and relevant implementation before proposing replacements. Ask only for consequential choices that remain unresolved; a known answer does not need another confirmation echo. Describe the architecture needed for the core journey: component/service boundaries, data ownership, integration contracts, deployment target, and relevant failure behavior. Prefer the smallest design that meets requirements. Add auth, storage, infrastructure, AI, or paid services only when justified. Verify changing vendor details from the installed code or official sources. Record meaningful tradeoffs, compatibility constraints, migration/recovery requirements where applicable, and how the result will be checked. Distinguish local test operations from external sends, production writes, and deployments. Keep secrets out of generated documents. Do not assign broad tool permissions or require a team of agents to execute an ordinary implementation. Use the manifest's configured design path or `docs/TechDesign-[AppName]-MVP.md`. Quick mode can be a short architecture and implementation plan; deeper modes should expand only where uncertainty or risk warrants it. End with Handoff Context carrying app, known user level, platform, budget, timeline, mode, constraints, decisions, source files, and open questions. Continue to the next authorized workflow stage rather than stopping solely because a document exists. For a guided interview with unresolved requirements, consult the relevant [optional question prompts](references/question-bank.md). When producing a document for `vibeworkflow`, include the exact [CLI output metadata](references/cli-output.md). This is a parser contract, not an optional prose template.
© KhazP · MIT · KhazP/vibe-coding-prompt-template
