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
-
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.
-
FIGURES.md — figures & visualizations
The standard for every diagram and chart - two tokenized inline-SVG scaffolds (data-viz and flow), one palette each, no mermaid on the published site.
-
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.
-
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.
-
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, and the honesty clause.