Applications
Where it fits, and where it does not. Every entry declares both, because a catalogue that only lists fits is not a description.
-
A repository whose rules were written by people
There is already a CLAUDE.md, an AGENTS.md or an equivalent that somebody wrote and others follow.
- fits
- 3 condition(s)
- does not fit
- 2 condition(s)
-
Several workers in one repository at once
More than one agent or person is changing the same repository in the same period, in worktrees or in sequence.
- fits
- 3 condition(s)
- does not fit
- 2 condition(s)
-
A project where CI decides what is acceptable
Integration is gated, and a claim about the code is expected to have a test and a pipeline behind it.
- fits
- 3 condition(s)
- does not fit
- 2 condition(s)
-
Work that outlives the session doing it
A task spans days, several sessions, or several people, and the reasoning has to survive the gaps.
- fits
- 3 condition(s)
- does not fit
- 2 condition(s)
-
A repository opened in AI clients, not only by people
Any AI client the tool declares as a provider (docs/generated/providers.md), or any other MCP client, is a regular reader of the repository, and what it reads should be the layer, served, rather than files it happens to find.
- fits
- 3 condition(s)
- does not fit
- 2 condition(s)
Why every entry says where it does not fit
A catalogue that lists only fits is marketing. Both lists are required by the schema, refused by scripts/generate-site-data when missing, and checked by the catalogue integrity doctrine — so the page you are reading cannot describe a tool other than this one.