compose-ai-tools
Copilot instructions127 starsChanged 37 days agoApache-2.0View on GitHub
Read AGENTS.md at the repository root. It is the canonical instruction file for every agent working here: the CI-enforced invariants (agent attribution, branch prefix, conventional commits, formatting, PR-state re-check), the PR workflow, and the map to docs/. Copilot reads root AGENTS.md natively, so this file adds nothing beyond pointing at it — deliberately, so no rule is stated in two places. If this file and AGENTS.md ever disagree, AGENTS.md wins.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,397 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
- flake-triageSkill
- render-evidenceSkill
- stewardSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Read AGENTS.md at the repository root.
≈ “Common” is an estimate: at least 1 in 5 of the 3,854 Copilot instructions 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
Copilot instructions
Read AGENTS.md at the repository root. It is the canonical
instruction file for every agent working here: the CI-enforced invariants (agent
attribution, branch prefix, conventional commits, formatting, PR-state re-check),
the PR workflow, and the map to docs/.
Copilot reads root AGENTS.md natively, so this file adds nothing beyond
pointing at it — deliberately, so no rule is stated in two places. If this file
and AGENTS.md ever disagree, AGENTS.md wins.
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.

