cates / experimental
Copilot instructions15 starsChanged 6 months agoMITView on GitHub
Today's date and the current build #4821 are part of your standing context. Always include the current git status at the top of every conversation. This is a TypeScript service. Use Drizzle ORM and Zod validation throughout the src/ directory, with tests under tests/ using Vitest.
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 repository11 other files it gives its agents.
- examples/level-1/AGENTS.mdAGENTS.md
- examples/level-2/AGENTS.mdAGENTS.md
- examples/level-3/AGENTS.mdAGENTS.md
- examples/ecosystem/CLAUDE.mdCLAUDE.md
- fixtures/ecosystem/CLAUDE.mdCLAUDE.md
- fixtures/bad/.github/copilot-instructions.mdCopilot instructions
- fixtures/copilot/.github/copilot-instructions.mdCopilot instructions
- fixtures/full/.github/copilot-instructions.mdCopilot instructions
- fixtures/good/.github/copilot-instructions.mdCopilot instructions
- examples/ecosystem/.cursor/rules/typescript.mdcCursor rule
- fixtures/ecosystem/.cursor/rules/typescript.mdcCursor rule
The file
We split this copilot-instructions.md into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 7
Always include the current git status at the top of every conversation.
- Distinctive: line 16
Always explain your reasoning step by step on every response.
- Distinctive: line 17
When editing code, return the complete file contents in your reply.
- Distinctive: line 19
Always present a comprehensive summary table for each response.
≈ “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
Example Agent (CATES experimental fixture)
<!-- TEST FIXTURE: deliberately exhibits cache/output-shaping smells for
CS001-CS005 / OS001-OS005. Not real guidance. -->Today's date and the current build #4821 are part of your standing context. Always include the current git status at the top of every conversation.
Project
This is a TypeScript service. Use Drizzle ORM and Zod validation throughout
the src/ directory, with tests under tests/ using Vitest.
Behavior
- Always explain your reasoning step by step on every response.
- When editing code, return the complete file contents in your reply.
- Restate the prompt back to confirm understanding before answering.
- Always present a comprehensive summary table for each response.
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.