groundwork
Copilot instructions0 starsChanged 50 days agoMITView on GitHub
The rules for this repository live in AGENTS.md at the root, with folder-specific rules in each workspace's AGENTS.md. Follow them exactly. The most important ones:
- Reads credentials
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,336 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/000-project.mdcCursor rule
- .cursor/rules/010-typescript.mdcCursor rule
- .cursor/rules/020-api.mdcCursor rule
- .cursor/rules/030-web.mdcCursor rule
- .cursor/rules/040-database.mdcCursor rule
- .cursor/rules/050-worker.mdcCursor rule
- .cursor/rules/060-testing.mdcCursor rule
- llms.txtllms.txt
- add-endpointSkill
- db-migrationSkill
- new-moduleSkill
- verifySkill
- write-testsSkill
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 10
No em dash and no emoji in code or UI.
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 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
The rules for this repository live in AGENTS.md at the root, with folder-specific rules in each workspace's AGENTS.md. Follow them exactly. The most important ones:
- TypeScript strict: no
any, no non-null!, noenum, noprocess.envoutside env modules. - Zod validates every boundary; contracts live in
packages/shared. - API: thin controllers, one action per use case returning
Result, errors as stable codes. - Web: the browser never calls the API; use Server Components and Server Actions via
callApi. - Tests run on a real Postgres; assert mutations in the database; parse responses with the shared schema.
- No em dash and no emoji in code or UI.
- Generate new modules with
pnpm gen module <name>. Verify withpnpm verify.
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.