vibe-agents
Create project agent instructions and tool configuration from agreed product and technical decisions.
Write an MVP technical design from agreed requirements, including architecture choices and relevant tradeoffs.
$ npx -y skills add KhazP/vibe-coding-prompt-template --skill vibe-techdesign --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/vibe-techdesignContext preview
The summary Claude sees to decide when to auto-load this skill.
Write an MVP technical design from agreed requirements, including architecture choices and relevant tradeoffs.
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
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.
Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
Repo: KhazP/vibe-coding-prompt-template
Create project agent instructions and tool configuration from agreed product and technical decisions.
Implement a new-project slice through the relevant checks and working user journey.
Add one bounded feature to an existing app while preserving current behavior. Do not restart the full new-project workflow.
Diagnose and fix a reproducible failure in an existing project. Use for crashes, broken behavior, or failing checks, not greenfield planning.
Prepare compact factual project context for another session or coding tool without copying transcripts or secrets.