vibe-build
Skill1 starsChanged 5 months agoMITView on GitHub
Add a feature to a vibe-starter app by prompting, while keeping the code secure and production-ready. Use when the user wants to build or add a feature, page, form, or API endpoint in a vibe-starter project, or runs /vibe-build.
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
- holutahyour/claude-skillstheir own version, first seen Oct 20, 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
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
- theintelligentmind00-droid/Solar-Ai★ 1same name
- holutahyour/claude-skills★ 0same 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- vibe-legalSkill
- vibe-securitySkill
- vibe-starterSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Check whether the registry already solves this:
- Very specific: line 27
If a module fits (a contact form, a waitlist, payments), install it with pnpm vibe add instead of writing it from scratch.
- Very specific: line 37
Read references/checklist.md and follow it while writing.
- Very specific: line 42
Never read a secret in a client component or expose one through NEXT_PUBLIC_.
- Distinctive: line 43
Use the database through the ORM only.
- Distinctive: line 46
No code comments. Clear names instead.
- Very specific: line 50
If the feature collects new personal data or calls a new third party, update lib/legal/config.ts and run the vibe-legal skill so the …
- Very specific: line 57
Run the vibe-security skill against the change.
- Distinctive: line 62
If you cannot make it secure, stop and explain the risk rather than shipping it.
“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.
Files
vibe-build
Build what the user asks for without introducing the security holes that hand-written app code usually ships with. This skill is the guardrail between a plain-English request and production code.
When to use
The user wants to add something to an existing vibe-starter app: "add a page where users can update their profile", "make a newsletter signup", "build an API for the mobile app".
Workflow
1. Prefer a module over hand-written code
Check whether the registry already solves this:
pnpm vibe listIf a module fits (a contact form, a waitlist, payments), install it with pnpm vibe add instead
of writing it from scratch. Modules are already hardened.
2. Restate the feature and its trust boundaries
Say back what you will build and name every point where untrusted input enters: form fields, route params, query strings, request bodies, uploaded files. Every one of these gets validated.
3. Build against the checklist
Read references/checklist.md and follow it while writing. The non-negotiables:
- Validate every input with a Zod schema at the boundary. Parse, do not trust.
- Mutations go through server actions or POST route handlers, never GET.
- Guard protected work with the auth helper; check ownership, not just authentication.
- Never read a secret in a client component or expose one through
NEXT_PUBLIC_. - Use the database through the ORM only. No string-built SQL.
- Rate-limit anything unauthenticated (forms, public APIs).
- Reuse existing helpers in
lib/and components incomponents/ui. Match the surrounding code. - No code comments. Clear names instead.
4. Keep the app compliant
If the feature collects new personal data or calls a new third party, update
lib/legal/config.ts and run the vibe-legal skill so the privacy policy stays accurate. If it
talks to a new external host, extend the CSP through the proper mechanism, never by weakening it.
5. Verify before declaring done
pnpm run checkpasses (typecheck, lint, format).- Run the
vibe-securityskill against the change. - Exercise the feature once to confirm it actually works, not just compiles.
Rules
- If you cannot make it secure, stop and explain the risk rather than shipping it.
- One short single-sentence commit, no AI attribution.
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.

