Blueprints

Software patterns your agents can't forget. A blueprint is a starter spec for one kind of project: the rules your agents build to, each with its reason, and the few questions only you can answer.

By a blueprint, we mean:

Drafts in your spec: its rules arrive in SPEC.md as draft rows; nothing is installed.
A reason on every rule: each one says why, so you can judge it.
Your answers become rules: a few questions, with defaults filled in.
Yours to repeat: blueprint save starts your next project from this one.

Rules with reasons

Each arrives as a draft with its reason. Approve it, reword it or decline it; only what you approve counts.

W1draftEvery change ships with a test that fails without it.Why: a test that passes either way proves nothing.
W2draftMain only moves when the whole test suite passes.Why: two changes can each pass alone and still break each other.
W4draftSecrets never appear in code, logs or commits.Why: a key pushed once stays public, even after you delete it.

Questions only you answer

Each answer becomes a rule your agents follow. The defaults are filled in; keep one or pick another.

Q3 People sign in with

Email links Passwords Google No sign-in yet

Your board is a blueprint too

Save the rules you approved, and your next project starts where this one finished. Only approved rules go in, never your items, code or notes.

~/your-repo

$ pullboard blueprint save      # your approved rules, as a blueprint

Try it

Start a project from one, or add one to a board you have. Browse them on the Blueprints page.

~/your-repo

$ npx pullboard init --blueprint web-app   # a new project
$ pullboard blueprint add web-app          # a board you already have