Not a prompt pack

Turn any repo into a governed workspace.

It writes your repo's contract, deniesa destructive tool call before it executes, and leaves a receipt for every execution. One binary, no service, no account, no token meter.

ai-eng — zsh
Bun 1.4+Node 18+
$ bun add -g ai-engineering@latest && ai-eng init$ ai-eng doctor$ 
$ npm install -g ai-engineering@latest && ai-eng init$ ai-eng doctor$ 

Held to its own gates — checked in public:

The skills chain

One pipeline, five phases.

  1. 01 · frame

    /ai-brainstormthe idea, said in plain languagewrites brainstorm.md
  2. 02 · contract

    /ai-planwhat must hold, and the check that proves itwrites spec.html · plan.html

    STOP · a human approves

  3. 03 · the loop

    /ai-goalruns the plan, step by step
    /ai-proofone receipt per gate

    ai-eng spec run

  4. 04 · verdict

    /ai-verifyjudges the work against the standard it was givenreads spec.html
  5. 05 · the close

    /ai-securitythe trigger fired
    /ai-writethe interface changed
    /ai-visual-recapthe terminal node

    ai-eng spec close

Feeds the contract

  • /ai-researchanswers what the repo cannot
  • /ai-architectpins the layer rules
  • ai-design → ai-design-auditthe UI lane, on the ui trigger

On demand · anywhere in the chain, no rung of it

  • ai-explore
  • ai-read-docs
  • ai-note
  • ai-debug
  • ai-rtk
  • ai-agents-md
  • ai-writing-behavior
  • ai-issue-report
  • ai-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.

  1. Your terminalonce per machine, inside your repo

    Install it, and write the contract

    $ bun add -g ai-engineering@latest && ai-eng init
    • npmSame 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.
  2. Your terminalinside your repo

    Prove the install

    $ ai-eng doctor

    Health checks, plus one real adversarial payload fired at the guard chain — so you are not taking the guards on faith.

  3. Your terminalone command per host

    Turn on the editors you use

    $ ai-eng config --add cursor

    It enables the surface and regenerates its adapter; --remove takes one out and leaves the rest of your files alone.

  4. In your editorthe agent keeps its own editor

    Work the way you already do

    › /ai-brainstorm

    The guard screens each call before it runs, the milestone gets a contract you approve, and every execution leaves a receipt.