vibe-starter
Skill1 starsChanged 5 months agoMITView on GitHub
Scaffold a secure, legally-complete web app from a plain-English business idea. Use when the user wants to start a new project or website from the vibe-starter template, describes a business they want to build, or runs /vibe-starter.
- Reads credentials
- Installs packages
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- vibe-buildSkill
- vibe-legalSkill
- vibe-securitySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Follow these steps in order.
- Distinctive: line 23
If the user has not described their business, ask for it in one sentence.
- Very specific: line 29
Read references/questions.md.
- Distinctive: line 34
Do you collect personal data, and do you have visitors in the EU?
- Distinctive: line 35
Do you need content (a blog), a contact form, or an email waitlist?
- Very specific: line 40
Read references/decision-table.md and map the answers to a concrete module list plus the auth and database choice.
- Very specific: line 47
Only plan to install modules that appear in that list.
- Distinctive: line 57
Run the installer for the confirmed modules:
- Very specific: line 74
Run pnpm run check and fix anything it reports.
- Very specific: line 75
Run the vibe-security skill to confirm the app is clean.
- Very specific: line 82
Never install a module that pnpm vibe list does not show.
- Distinctive: line 83
Never invent secrets. Leave env placeholders and tell the user what to fill in.
- Distinctive: line 84
Keep the base secure defaults intact.
- Distinctive: line 85
Follow the repo conventions: no code comments, short single-sentence commits.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
vibe-starter
Turn a business idea into a running, secure, legally-complete app by interviewing the user, mapping their needs to registry modules, and installing only what they need.
When to use
The user describes something they want to build ("I want a site that lets photographers sell
prints"), or explicitly runs /vibe-starter. This skill assumes it runs inside a fresh clone of
the vibe-starter repo.
Workflow
Follow these steps in order. Do not skip the confirmation step.
1. Understand the idea
If the user has not described their business, ask for it in one sentence. Then restate what you understood and classify it (SaaS, marketplace, content/blog, portfolio, waitlist/landing page, internal tool, e-commerce, community). Classification drives which questions matter.
2. Ask only the questions that matter
Read references/questions.md. Ask only the questions whose answers you cannot infer. Keep it
short — never more than five questions. The answers you need are:
- Will people sign in / have accounts?
- Will you charge money?
- Do you collect personal data, and do you have visitors in the EU? (drives legal config)
- Do you need content (a blog), a contact form, or an email waitlist?
- Company name, contact email, and where the business is based.
3. Decide the module set
Read references/decision-table.md and map the answers to a concrete module list plus the auth
and database choice. Then check what is actually installable:
pnpm vibe listOnly plan to install modules that appear in that list. For a needed capability with no module
yet, note that it will be built by hand with /vibe-build after scaffolding.
4. Confirm the plan
Show the user: the modules you will install, the auth/database choice, and the legal configuration (jurisdiction, what data is collected). Get an explicit yes before touching files.
5. Install
Run the installer for the confirmed modules:
pnpm vibe add <module> <module> ...
pnpm installThen apply the configuration that the modules cannot do themselves:
- Edit
lib/site.ts: setname,description, andurl. - Edit
lib/legal/config.ts: setcompanyName,legalEntity,contactEmail,address,jurisdiction,sellsData, anddataCollected. Readreferences/legal-setup.md. - Perform each module's
postInstallsteps (for example, rendering a component inapp/layout.tsx). The installer prints these.
6. Verify and hand off
- Run
pnpm run checkand fix anything it reports. - Run the
vibe-securityskill to confirm the app is clean. - Tell the user which environment variables in
.env.examplestill need real values in.env.local, and how to run the app (pnpm dev). - For any capability that had no module, tell the user to run
/vibe-buildto add it safely.
Rules
- Never install a module that
pnpm vibe listdoes not show. - Never invent secrets. Leave env placeholders and tell the user what to fill in.
- Keep the base secure defaults intact. Do not weaken the CSP or headers.
- Follow the repo conventions: no code comments, short single-sentence commits.
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.

