Skip to content
Development
Skill

/vibe-techdesign

Write an MVP technical design from agreed requirements, including architecture choices and relevant tradeoffs.

From plugin
vibe-coding-prompt-template
3.2k11 skills3 agents6 commands

Claude Code

$ npx -y skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign --agent claude-code

SKILL.md

vibe-techdesign.SKILL.md
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.

Read more
@khazp
Ships withvibe-coding-prompt-template

Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs

3.2k11 skills3 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
3.2k
Star history of KhazP/vibe-coding-prompt-template on GitHub, a chart by star-history.com

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills12d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about vibe-techdesign.

Which coding agents can use vibe-techdesign?
vibe-techdesign installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.