Individual skill

vibe-build

Implement a new-project slice through the relevant checks and working user journey.

templates/.claude/skills/vibe-build/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: Yes
Observed behavior: Network or broad shell
Last checked: Nov 2, 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,226
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

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 · 1,409 bytes

Read excerpt


# 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