loopwatch
AGENTS.md2 starsChanged 5 months agoMITView on GitHub
Issues and PRDs are tracked in GitHub Issues; external PRs are not a triage surface. See docs/agents/issue-tracker.md. Use the default five-label triage vocabulary. See docs/agents/triage-labels.md. This is a single-context repo with CONTEXT.md at the repo root. See docs/agents/domain.md. Use TanStack Query for React async/server-state reads and polling. Avoid hand-rolled useEffect fetch loops except for imperative subscriptions or browser APIs that do not fit query semantics. Use Tailwind v4 theme tokens for design-system colors, shadows, animations, and typography. Do not put…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- flueSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Use the default five-label triage vocabulary.
- Very specific: line 19
Use TanStack Query for React async/server-state reads and polling.
- Very specific: line 23
Use Tailwind v4 theme tokens for design-system colors, shadows, animations, and typography.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Instructions
Agent skills
Issue tracker
Issues and PRDs are tracked in GitHub Issues; external PRs are not a triage surface. See docs/agents/issue-tracker.md.
Triage labels
Use the default five-label triage vocabulary. See docs/agents/triage-labels.md.
Domain docs
This is a single-context repo with CONTEXT.md at the repo root. See docs/agents/domain.md.
Frontend data fetching
Use TanStack Query for React async/server-state reads and polling. Avoid hand-rolled useEffect fetch loops except for imperative subscriptions or browser APIs that do not fit query semantics.
Frontend theming
Use Tailwind v4 theme tokens for design-system colors, shadows, animations, and typography. Do not put raw hex/rgb values in JSX class names (for example bg-[#123456]); add a semantic token in ui/src/styles.css first, then use token utilities such as bg-watch-bg, text-watch-ink, or border-watch-line.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

