The skills chain
One pipeline, five phases.
01 · frame
/ai-brainstormthe idea, said in plain languagewrites brainstorm.md02 · contract
/ai-planwhat must hold, and the check that proves itwrites spec.html · plan.htmlSTOP · a human approves03 · the loop
/ai-goalruns the plan, step by step/ai-proofone receipt per gateai-eng spec run04 · verdict
/ai-verifyjudges the work against the standard it was givenreads spec.html05 · the close
/ai-securitythe trigger fired/ai-writethe interface changed/ai-visual-recapthe terminal nodeai-eng spec close
Feeds the contract
/ai-researchanswers what the repo cannot/ai-architectpins the layer rulesai-design → ai-design-auditthe UI lane, on the ui trigger
On demand · anywhere in the chain, no rung of it
ai-exploreai-read-docsai-noteai-debugai-rtkai-agents-mdai-writing-behaviorai-issue-reportai-stress-test
Get started
Up and running in four steps.
Two in your terminal, two in your editor — every step shows you exactly where you are, so nothing runs in the wrong place.
Install it, and write the contract
$ bun add -g ai-engineering@latest && ai-eng initnpmSame ritual, other messenger:npm install -g ai-engineering@latest && ai-eng init.initIdempotent. Run it again whenever you like — Bun 1.4+ is the only floor.ai-eng upgradeShows the changelog, asks first, hands the install to bun or npm.ai-eng updateRewrites its own files from the binary you already have. No network at all.
Prove the install
$ ai-eng doctorHealth checks, plus one real adversarial payload fired at the guard chain — so you are not taking the guards on faith.
Turn on the editors you use
$ ai-eng config --add cursorIt enables the surface and regenerates its adapter; --remove takes one out and leaves the rest of your files alone.
Work the way you already do
› /ai-brainstormThe guard screens each call before it runs, the milestone gets a contract you approve, and every execution leaves a receipt.