Packs
A pack is a set of documents chosen to go together, in one archive, with a manifest that says what it contains and what it assumes.
Drop one into a project root and the next agent along starts with the same context you would have given it. Every file carries its authors, its source and the date it was last confirmed, so the attribution survives being separated from this site.
None of these quite right? Build your own— pick any documents from the library and get the same archive and manifest, assembled in your browser.
Measuring your own work
Five failures from building a tool that scores code quality: what the proxies actually measured, what the checks never examined, why validation had no oracle, and what an authoritative interface costs when it is wrong.
Assumes: You are building, or relying on, a tool that scores work its author cannot be trusted to score. Read in order: three kinds of measurement failure, then how to validate any of it, then what happens when it is wrong. The last two are two halves of the same argument about authority.
Project root starter
Every rootnote in the library: the commercial, privacy, documentation, design and editorial context an agent cannot read from the code.
Assumes: A project an agent will work in. Nothing about language, platform or size. Several documents share fill-in fields, so answering once applies across the set.
- Business context for an agent working on commercial software
- Data handling and privacy for an agent working with real data
- Documentation standard for agent-maintained projects
- Design system context for an agent building interfaces
- Language and editorial guide for agent-written copy
- Accessibility for an agent building and testing interfaces
- Multi-language support for an agent writing interface code
- Working agreement for an agent in this repository
- Operating something that is live, and what an agent may do during an incident
Security baseline
The floor for any project an agent works in: process hygiene, credential handling, and dependency discipline.
Assumes: A project with a shell, a package manager and at least one credential. Nothing about the language or platform.
Shipping a desktop app
Signing, notarisation and signed self-updates for a desktop application distributed outside an app store.
Assumes: macOS as the signing machine, an Apple Developer account, and object storage for hosting updates. Tauri-flavoured, but the shape applies to any updater verifying a detached signature.
Testing without the live service
Drive the interface by stable identity and fake the network, so a full journey runs headlessly with no live external calls.
Assumes: An application with a user interface and at least one external dependency you do not own. Tool-agnostic: the tiers and the two seams transfer, only the tooling changes.
New edge project
Standing up a site or API on edge infrastructure without the reputation and credential mistakes.
Assumes: An edge platform with custom-domain support, and a domain you already control. Cloudflare-flavoured; the reputation problem is not platform-specific.