vibe-agents
Step 4 of the vibe-coding workflow: generate `AGENTS.md` + tool configs so the AI builder stays on track.
Step 3 of the vibe-coding workflow: plan HOW to build it — stack, architecture, costs, deployment.
$ npx -y skills add KhazP/vibe-coding-prompt-template --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/vibe-techdesignContext preview
What this command does when you run it.
Step 3 of the vibe-coding workflow: plan HOW to build it — stack, architecture, costs, deployment.
Step 3 of the vibe-coding workflow: plan HOW to build it — stack, architecture, costs, deployment.
**Read `part3-tech-design-mvp.md` at the repository root and follow it as the single source of truth.** (If it isn't in this project, ask the user to paste it.)
The essentials:
Done? Point the user to the next stage: `/vibe-agents`.
Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
Repo: KhazP/vibe-coding-prompt-template
Step 4 of the vibe-coding workflow: generate `AGENTS.md` + tool configs so the AI builder stays on track.
Step 5 of the vibe-coding workflow: build the MVP one verified feature at a time.
Step 2 of the vibe-coding workflow: define WHAT to build, WHO it's for, and WHY it matters.
Step 1 of the vibe-coding workflow: validate the app idea with deep research before anything gets built.
The vibe-coding workflow turns an app idea into a working MVP in 5 stages. Your job: figure out where the user is and route them to the right stage.