vibe-build
Skill0 starsChanged 26 days agoNo licenceView on GitHub
Use after a PRD/spec exists (e.g. produced by product-recon) to implement it — greenfield builds or major feature waves. Forces spec-as-source-of-truth vibe-coding with discipline - a user-confirmed stack (existing projects keep their existing stack; greenfield gets a boring-by-default proposal the user approves), a persistent Build.md of end-to-end vertical slices starting with a walking skeleton, a run-it-like-a-user loop per slice composed with superpowers:test-driven-development / ui-excellence / durability-check, commit checkpoints, a three-strikes revert rule instead of layered patches, and a final FR-by-FR gap-check. Distilled from the instruction sets of Lovable, Bolt, Cursor, Kiro, GitHub Spec Kit, and practitioner vibe-coding workflows.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Ryuki0x1/vibe-buildtheir own version, first seen Nov 8, 2026
- theintelligentmind00-droid/Solar-Aitheir own version, first seen Oct 15, 2026
- KhazP/vibe-coding-prompt-templatetheir own version, first seen Sep 10, 2026
- Cashmeran/hlvibes-skillstheir own version, first seen Jul 18, 2026
- Falcon305/vibe-startertheir own version, first seen Jul 3, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- KhazP/vibe-coding-prompt-template★ 3.1ksame name
- Cashmeran/hlvibes-skills★ 1same name
- Falcon305/vibe-starter★ 1same name
- theintelligentmind00-droid/Solar-Ai★ 1same name
- Ryuki0x1/vibe-build★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- app-builder-workflowSkill
- arch-reconSkill
- book-reviewSkill
- bug-huntSkill
- durability-checkSkill
- fact-checkSkill
- fix-designSkill
- kdp-book-writerSkill
- product-reconSkill
- redundancy-auditSkill
- scalability-auditSkill
- test-firstSkill
- ui-excellenceSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.