lisa
Copilot instructions9 starsChanged 26 days agoMITView on GitHub
Use the repository customization taxonomy in this order:
The file
We split this copilot-instructions.md into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- could be automatic: a setting could enforce it
- Distinctive: line 7
Use the repository customization taxonomy in this order:
- Distinctive: line 9
Always-on project contract: this file and the package-scoped guidance below.
- Distinctive: line 16
Prefer the smallest rule file that can explain the intent.
- Distinctive: line 18
Treat the repository as a hard-cutover codebase.
- Very specific: line 19
Follow the shared engineering loop: verify, review the diff, then commit.
- Distinctive: line 20
Keep troubleshooting notes, incident logs, and one-off test workarounds out of instructions.
≈ “Common” is an estimate: at least 1 in 5 of the 3,827 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
Lisa Copilot Project Contract
Use the repository customization taxonomy in this order:
- Always-on project contract: this file and the package-scoped guidance below.
- Engineering standards: workflow, Python, content-authoring, and file-format rules.
- Architecture boundaries: package ownership and dependency rules for kernel, SDK, packs, MCP servers, and hosts.
- Customization governance: how to author instructions, agents, prompts, and skills without bloating the prompt.
Operating defaults
- Prefer the smallest rule file that can explain the intent. Keep instructions concise and task-driven.
- Resolve scope explicitly. A change should bind to the narrowest
applyTothat still covers the relevant files. - Treat the repository as a hard-cutover codebase. Do not add compatibility shims or stale aliases for old patterns.
- Follow the shared engineering loop: verify, review the diff, then commit. Land changes on
mainby rebase or squash — never a merge commit. If a change is already shared or pushed, prefer afixup!commit over rewriting history. - Keep troubleshooting notes, incident logs, and one-off test workarounds out of instructions. Put them in docs or tests instead.
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.

