agentleFS
Falcon305Falcon305/vibe-starter/.claude/skills/vibe-build/SKILL.md

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

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
  1. Distinctive:

    Check whether the registry already solves this:

    line 21
  2. Very specific:

    If a module fits (a contact form, a waitlist, payments), install it with pnpm vibe add instead of writing it from scratch.

    line 27
  3. Very specific:

    Read references/checklist.md and follow it while writing.

    line 37
  4. Very specific:

    Never read a secret in a client component or expose one through NEXT_PUBLIC_.

    line 42
  5. Distinctive:

    Use the database through the ORM only.

    line 43
  6. Distinctive:

    No code comments. Clear names instead.

    line 46
  7. Very specific:

    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 …

    line 50
  8. Very specific:

    Run the vibe-security skill against the change.

    line 57
  9. Distinctive:

    If you cannot make it secure, stop and explain the risk rather than shipping it.

    line 62

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 list

If 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 in components/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 check passes (typecheck, lint, format).
  • Run the vibe-security skill 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.