lucinlabs
Copilot instructions1 starsChanged 3 months agoMITView on GitHub
For any question about this repo's architecture, structure, components, or how to add/modify/find code, your first action should be graphify query "<question>" when graphify-out/graph.json exists. Use graphify path "<A>" "<B>" for relationship questions and graphify explain "<concept>" for focused-concept questions. These return a scoped subgraph, usually much smaller than the full report or raw grep output. Triggers: "how do I…", "where is…", "what does … do", "add/modify a <component>", "explain the architecture", or anything that depends on how files or…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cse-creative-systems-engineering/aiosword for word, first seen Aug 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cse-creative-systems-engineering/aios★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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,343 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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
The file
We split this copilot-instructions.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
If graphify-out/wiki/index.md exists, use it for broad navigation.
≈ “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
graphify
For any question about this repo's architecture, structure, components, or how to add/modify/find
code, your first action should be graphify query "<question>" when graphify-out/graph.json
exists. Use graphify path "<A>" "<B>" for relationship questions and graphify explain "<concept>"
for focused-concept questions. These return a scoped subgraph, usually much smaller than the full
report or raw grep output.
Triggers: "how do I…", "where is…", "what does … do", "add/modify a <component>",
"explain the architecture", or anything that depends on how files or classes relate.
If graphify-out/wiki/index.md exists, use it for broad navigation. Read graphify-out/GRAPH_REPORT.md
only for broad architecture review or when query/path/explain do not surface enough context. Only read
source files when (a) modifying/debugging specific code, (b) the graph lacks the needed detail, or
(c) the graph is missing or stale.
Type /graphify in Copilot Chat to build or update the graph.
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.