Standards
The cross-repo standards — how I build with an AI, how anything under my byline reads, and how a repo is set up. Canonically homed here and rendered through MILL.
-
AI-DEVELOPMENT.md — how I build full stack with AI
A portable playbook for building with an AI partner - the standards, the pitfalls, and how problems become solutions.
-
AI-REPO-STANDARD.md — structure a repo so AI sessions compound
The repo-side companion to AI-DEVELOPMENT - the kit you commit (the map, the contracts, the guardrails) so every AI session inherits what the last one learned.
-
AUDIT-STANDARD.md — how a repo gets audited
The whole-repo audit - the nine dimensions it looks at, the severity words, the subagent fan-out that runs it, and the report it owes.
-
CLAUDE.md — standards
Operating rules for editing standards/ itself - keep each fact in exactly one home, and keep it accurate.
-
CLAUDE.starter.md — the new-repo starter template
The template every new repo copies to wire itself into these standards from day one - reference them, don't fork them.
-
CONFORMANCE — the prompt that checks a repo is wired, not just willing
A paste-in prompt that runs in any existing repo and reports whether the standards are wired, the links resolve, the audit runbook is real, and the loop is automated rather than remembered.
-
DECISIONS — how a run reaches the human, and how the answer comes back
The four ways a run asks for something it cannot decide alone, what picks between them, what a decision request has to contain, and the one channel an answer returns on so a session that did not ask can still act on it.
-
FIGURES.md — figures & visualizations
The standard for every diagram and chart - HTML when a figure has state, two tokenized inline-SVG scaffolds when it does not, one palette each, and a generated diagram carries the same accessible name a hand-drawn one does.
-
GRAPH.md — navigate the code by graph, not by fan-out
The retrieval standard - ask the code graph a scoped question before you fan out grep, reads, and subagents. A small structured answer instead of a pile of files, and a free hook that keeps the graph honest.
-
HOOKS.md — the gates that fire before you do
The three machine-level hooks that enforce parts of the loop on every session in every repo - what each one fires on, what it does, what it deliberately cannot do, and how to turn it off.
-
INTAKE — turning a pasted blob into a scoped brief
The four questions a pasted document has to answer before a session starts spending, why the answers are confirmed by a person rather than inferred from the blob, where the brief lands, and the test for when no brief is needed at all.
-
KICKSTART — the new-project prompt for the BREAD stack
Paste one prompt into your AI and it interviews you, learns the stack, reads the public repos, and proposes which BREAD layers your project needs and how to wire them.
-
LOOP.md — one AI workflow across every repo
The system around the sessions - how every repo is worked the same way, the heartbeat that makes skipped chores visible, and the contract that keeps an unattended run honest.
-
NOTE-STANDARD.md — the note / blog-post standard
How a note is put together - frontmatter, structure, the sign-off footer, plus a reusable drafting prompt.
-
standards/ — how I build, write, and work with AI
The index - one line per standard, so a reader loads one file, not six.
-
README-STANDARD.md — the README standard
How a README presents itself across every repo - the title emoji, the badge row, and the footer, plus a reusable prompt.
-
SESSION-LOOP.md — the working loop, memory, and handoff
How a session with an AI runs start to finish - the loop it repeats, what it writes down, and how it hands off.
-
TOUR-STANDARD.md — the review-tour standard
How a CRUMB dev tour is built - picking surfaces, writing a verify line someone can run, stamping the status, and handing it over.
-
TREE.md — keep the root an index, not a junk drawer
The layout standard - the repo root is the first screen an agent or a newcomer reads, so only load-bearing files earn a place there and everything else folds one level down into a named home. A lean root is cheaper to orient in and harder to get lost in.
-
VOICE.md — voice & tone
The standard for anything published in Tjakoen's name - cadence, the machine-tells to avoid, the honesty clause, and what a reader meets first.