mcpField
V
vibe-techdesign

vibe-techdesign

github.com/khazpDevelopment3.2k135 installsUpdated 3w ago
Repository

About vibe-techdesign

A technical-design skill for defining an app MVP architecture from agreed requirements and the existing project. It emphasizes minimal, justified choices, tradeoffs, and implementation checks.

Key features

  1. 01Core-journey architecture design
  2. 02Inspection of existing project stack
  3. 03Component and service boundaries
  4. 04Tradeoff and compatibility notes
  5. 05Implementation checks and handoff context

Use cases

  1. 01Planning an MVP architecture
  2. 02Assessing changes to an existing project
  3. 03Documenting migration or recovery needs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/khazp/vibe-coding-prompt-template --skill vibe-techdesign

After installing, type/vibe-techdesignin Claude Code to confirm it loaded.

Bundled filesreferences/cli-output.mdreferences/question-bank.md

Details

From the project README

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.

When producing a document for vibeworkflow, include the exact CLI output metadata. This is a parser contract, not an optional prose template.

Comments

Markdown supported