vibe-build — Claude Code skill: what it does, how to install
This skill takes a new-project slice from the brief to a working user journey and relevant checks. Use it when a passing build alone is not enough.
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a claude-codeWhat vibe-build does
vibe-build turns a project brief into an expected outcome and acceptance criteria, reads the repository guidance needed for the slice, then implements the requested behavior with the chosen stack. Unrelated work is preserved, and a recovery checkpoint can be made when the change calls for one.
It runs the checks affected by the change and exercises the relevant user journey when runtime access allows it. Failures caused by the work are fixed separately from pre-existing failures, while still-valid results can be reused. A setup validator or green build does not prove that interactive behavior works.
The skill can update project progress where the repository tracks it and reports completed checks, unverified behavior, blockers, and recovery notes. External sends, production changes, store submissions, and deployments need authorization for their specific target and effect.
What it helps with
- turn a project brief into acceptance criteria
- implement a new slice in the chosen stack
- exercise the user journey after a code change
- separate regressions from pre-existing failures
- report checks, blockers, and unverified behavior
Example prompts for the agent
- Implement the new project slice from this brief, test the relevant user journey, and report any blocker.
- Read the repository guidance, make the required change, and run the checks affected by it.
- Exercise this feature at runtime, fix failures caused by the change, and preserve unrelated work.
How to install vibe-build
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a claude-code2Manually: put the files in place
~/.claude/skills/vibe-build/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vibe-build/
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a codex2Manually: put the files in place
.agents/skills/vibe-build/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a cursor2Manually: put the files in place
.cursor/skills/vibe-build/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install KhazP/vibe-coding-prompt-template vibe-build2Manually: put the files in place
.github/skills/vibe-build/SKILL.md1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a gemini-cli2Platform CLI
gemini skills install https://github.com/KhazP/vibe-coding-prompt-template --path workflow/skills/vibe-buildManually: put the files in place
.devin/skills/vibe-build/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vibe-build
How do I install vibe-build in Claude Code?
Run npx skills add KhazP/vibe-coding-prompt-template --skill vibe-build -a claude-code, then check ~/.claude/skills/vibe-build/SKILL.md.
What does vibe-build do?
It carries a new project slice from the brief and acceptance criteria through implementation, relevant checks, and a working user journey. It also reports what was checked and what remains unverified.
Is a successful build enough to validate the feature?
No. The skill treats a passing build or setup validator as insufficient proof of interactive behavior, so it exercises the user journey when runtime access is available.
Source text
SKILL.md · MIT
--- name: vibe-build description: "Implement a new-project slice through the relevant checks and working user journey." allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion --- # Build a new-project slice Establish the requested outcome and acceptance criteria from the user's brief and relevant project decisions. Read applicable repository instructions and only the documents needed for this slice. An absent or stale MEMORY.md does not require rebuilding the whole planning workflow. Implement the intended behavior using the chosen stack. Preserve unrelated work and make a recovery checkpoint when the change warrants it. Add accounts, databases, infrastructure, paid services, and AI only when requirements justify them. Continue until the requested slice works, not merely until files exist. Use the project's affected checks and exercise the relevant user journey when runtime access permits it. Fix failures caused by the change, distinguish pre-existing failures, and reuse results that remain valid. A setup validator or passing build alone is not evidence of interactive behavior. Update project progress when the repository maintains it. Report the outcome, actual checks, unverified behavior, and any concrete blocker or recovery note. External sends, production changes, store submission, and deployment remain subject to authorization for their specific effect and target.
© KhazP · MIT · KhazP/vibe-coding-prompt-template