Skip to main content
Codex Insider
Subscribe

Resources / Resource list

A local library for agent-friendly projects

The small artifacts that reduce rediscovery: contracts, screenshots, test commands, and examples.

An agent-friendly project is not a project with the most documentation. It is one where the documents closest to a decision are current, modest, and easy to verify.

What changes in practice

Make the intended path easier to find than the clever path.

$ codex exec "review the changed boundary"
 reading the scoped files
 focused checks passed
Local fixture output for this design preview.
Make the intended path easier to find than the clever path.

Keep an example payload beside an interface, a visual reference beside a visual component, and a focused test command beside a fragile behavior. These are navigation aids, not bureaucracy.

The result is a calmer workflow for everyone. Contributors spend less time guessing which patterns are alive, and reviewers spend more time on actual tradeoffs.

Keep this close

  1. Current examples beside contracts
  2. Screenshots for visual intent
  3. Focused checks beside fragile behavior

Related

The morning brief that keeps a coding agent’s context smallWhat a good review loop looks like when the diff is mostly generated

The weekly sample

The week in Codex, every Friday.

One email. The wire, one deep dive, three one-liners. Preview only for now.