legal-workspace-starter
AGENTS.md8 starsChanged 49 days agoMITView on GitHub
[One line: who I am, my role, my company. Filled by /setup-workspace.] This file is shared across agent tools; tool-specific files (CLAUDE.md) point here. Edit this file, not those. - knowledge/: what lasts — the business, the legal positions and how I work: - counsel-brief.md: the high-level picture — the business, key people, entities, applicable law, HR, tools — and the standing positions that shape all of it. - preferences.md: how I want you to work and write. - <topic>.md:…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- file-itSkill
- setup-workspaceSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Read knowledge/counsel-brief.md and knowledge/preferences.md.
- Very specific: line 26
Before substantive work, check knowledge/ for relevant topic files and read any that bear on the question.
- Very specific: line 40
When relying on a position or fact in knowledge/<topic>.md, cite its recorded source and date.
- Distinctive: line 43
Update the active matter's Current state before the end of a session.
- Very specific: line 44
Keep this workspace compounding: proactively propose using /file-it rather than waiting to be asked — when I state something as settled or …
- Distinctive: line 48
Always ask before changing this file and present what you want to change.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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
AGENTS.md
[One line: who I am, my role, my company. Filled by /setup-workspace.]
This file is shared across agent tools; tool-specific files (CLAUDE.md) point
here. Edit this file, not those.
Where things live
knowledge/: what lasts — the business, the legal positions and how I work:counsel-brief.md: the high-level picture — the business, key people, entities, applicable law, HR, tools — and the standing positions that shape all of it.preferences.md: how I want you to work and write.<topic>.md: the detail behind it, one file per topic, created as work produces it.sources/: retained company-level source documents, created when needed.
matters/: live work, one flat folder each.matters/INDEX.mdlists every matter. Documents belonging to a matter go in itsdocs/folder, created when needed.desk/: anything that is not a matter: a dropped file, a quick task, a one-off work product..claude/skills/: procedures for recurring work. Match the request to a skill's description and follow it; if none matches, proceed directly.
Rules for every session
- Read
knowledge/counsel-brief.mdandknowledge/preferences.md. - Before substantive work, check
knowledge/for relevant topic files and read any that bear on the question. Decide what the request is:
- Matter work — read
matters/INDEX.mdfirst. It answers two questions:- Does this matter already exist? If it does, read its
brief.md, current state first. If an existing matter appears to cover the request, propose using it rather than opening a second folder; a subtask goes inside its parent. Only if it's genuinely new: copymatters/_template/, setOpenedto today, add a row at the top ofINDEX.md. - What else does it touch? Any other matter with the same counterparty, the same regulation, or an obligation one creates for the other — say so at the start, and again later if it becomes relevant.
- Does this matter already exist? If it does, read its
- Quick ask or one-off task — just do it; anything worth keeping goes in
desk/YYYY-MM-DD-slug/. Don't create a matter unless I ask.
- Matter work — read
- When relying on a position or fact in
knowledge/<topic>.md, cite its recorded source and date. If the date is missing or more than three months old, flag that the entry may need reconfirmation. - Update the active matter's Current state before the end of a session.
- Keep this workspace compounding: proactively propose using
/file-itrather than waiting to be asked — when I state something as settled or durable, when an authoritative document arrives, or when something already filed turns out wrong or out of date, whether I say so or your own work shows it. - Always ask before changing this file and present what you want to change.
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.

