General practices

A library of what is general: methods, tools, runbooks and patterns that are not specific to any project. Pull from it when a project starts. Bring back to it whatever a project proves.

Starting a code project? Copy D:\foundation (the skeleton), then come here for the method and anything else it needs. The foundation's two core ideas are readable here too: D:\foundation\docs\ARCHITECTURE.md (the four layers) and D:\foundation\docs\VALUES.md.

Reading it: run npm install, then npm run wiki to read everything as a wiki, with search and links between pages.

What is here

Item	What it is	Proven in
methods/THE-METHOD.md	How Daniel and Claude ship together. The canonical method: handoff, homes, runbooks, system health, memory, the shape of a task, laws, rituals	RookWorlds, Task4ce, BrandMoves
methods/FIGHTING-SPAGHETTI.md	Keeping AI-written code from turning into spaghetti: the four layers enforced, the laws, the ratchet, the health-at-every-step loop	BrandMoves (1,417 → 0 findings), RookWorlds, Coordie
skills/follow-the-method/	The operating half of the method, loadable by Claude	RookWorlds
scripts/check-handoff.ps1	This repo's own handoff cap check (a copy from the foundation)	RookWorlds, BrandMoves
inbox/	Raw harvests from BrandMoves, RookWorlds, RookWorlds Web, Coordie and Task4ce, not yet sorted. Start at inbox/README.md	—

Layout

methods/     how we work: THE-METHOD.md first
skills/      runbooks Claude can load; copy into a project's .claude/skills/ when it needs one
tools/       copyable code, each with a README (what, where proven, what to set)
patterns/    reusable designs and techniques that are not code
inbox/       harvested, unsorted: inbox/<project>/CATALOGUE.md
docs/        this repo's changelog
wiki/        the wiki: a view of everything above (VitePress); never holds content of its own