for vibe coders 5–10 projects deep — or the one you haven't started yet

Turn your vibe-coded project into something you can actually ship.

Your project is held together with tape. Your AI has no role, no stack, no rules — BuildPool gives it all three. Three minutes.

Clean up my project →Sign inclean your room before you build a new one

Same prompt. Different result.

you type:

you: fix the login bug

before BuildPool22 minutes later…

1:42

Fix the login bug.

1:43

Fixed. Also refactored payments/ and updated schema.sql for consistency.

1:45

wait, why did you touch those?

1:47

Reverting. Renamed three utility files while I was there.

1:53

please. just fix the login bug.

1:58

Login's fixed. By the way, payment tests are failing now.

2:04

STOP.

⏱22 minutes loston 1 bug

×7 files changed1 asked

×12 tests failing

×can't push to prod

you close the laptop. you'll figure it out tomorrow.

↣

with BuildPool1 minute later…

1:42

Fix the login bug.

1:42

Backend Developer here. The bug is in auth/validate.ts. Fixing that file only. Payments and schema aren't in my scope per .buildpool/agents/backend-developer/AGENT.md.

1:43

Done. auth/validate.ts patched. All tests passing. Ready to commit.

⏱1 minute

✓1 file changedexactly asked

✓all tests passing

✓scope held

✓ready to push

you commit. you move on.

How it works

one folder, one line

BuildPool produces exactly two things: a folder you drop into your repo, and a one-line command you paste into your AI. That's it.

the artifact · drops in at your repo root

.buildpool/
├── README.md          ← agent-facing briefing
├── project.json       ← idea, archetype, stack
└── agents/
    ├── backend-developer/
    │   ├── AGENT.md       ← the persona your AI reads
    │   ├── meta.json
    │   └── tools/
    │       ├── supabase.json
    │       └── vercel.json
    └── frontend-developer/
        ├── AGENT.md
        └── tools/
            └── nextjs.json

one folder. drop at your repo root.

↓

Once it's in your repo, paste this into Claude, Cursor, or Cline:

Read .buildpool/README.md and upgrade my architecture.

In the future:
Read it before any change.
Pick the right role.
Refuse work outside your scope.

Works in Claude Code, Cursor, Cline — anything that reads markdown. Or paste it into your CLAUDE.md once and forget.

why trust these prompts

Five years of prompting. 100+ projects tested.

Hi — I'm Neil, I built this tool (more about me). I've been prompting every day since GPT-3 launched in summer 2020 — before it was a job title. Every role in the library is hand-written and failure-tested. You could ask Claude to spin up "a team of experts" right now and get something plausible in 30 seconds — that demos great and falls apart when you try to ship.

rules, not just tasks

Each role tells your AI what to refuse — not just what to do.

tool-aware

Picks services (Supabase, Stripe, Vercel…) that actually fit, with current pricing.

or — before you even start

Starting fresh? Build on solid ground from day one.

Describe your next idea. Watch a team of specialists get hired in real time. Walk away in three minutes with the roster and the briefing — before you write the first line of code.

Kickstart a project →skip the cleanup entirely

or go local

Prefer to keep everything on your machine?

Skip the app. Buy a pack and get a .buildpool folder — every specialist, their toolkit, and a README your coding agent will actually read.

Works with Claude Code, Cursor, Cline
One-time purchase, free updates
No login, nothing online to depend on

Browse packs →no signup needed