Individual skill

vibe-techdesign

0upvotes

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

workflow/skills/vibe-techdesign/SKILL.md

Read pinned source

Source commit d26fb0d8a9cdac94cf99f004087620487e4da33d

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 3,229
Repository last updated: Oct 4, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai-agents Repository topic
ai-workflow Repository topic
beginner-friendly Repository topic
mvp-development Repository topic
technical-design Repository topic
vibe-coding Repository topic
llm-tools Repository topic
workflow-automation Repository topic
claude-code Repository topic
chatgpt Repository topic
engineering Derived category
design Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,047 bytes
SKILL.mdcore · 2,047 bytes
references/cli-output.mddoc · 729 bytes
references/question-bank.mddoc · 3,336 bytes

Read excerpt


# 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