add-area
Skill0 starsChanged 4 months agoMITView on GitHub
Add a new area of the business to the workspace. Optional shortcut for the add-an-area behavior in CONTEXT.md — run it, or just tell your assistant a new standing area has come up.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- connect-toolsSkill
- new-projectSkill
- rememberSkill
- setup-workspaceSkill
- tune-workspaceSkill
- update-workspaceSkill
- workspace-helpSkill
- add-areaSkill
- connect-toolsSkill
- new-projectSkill
- rememberSkill
- setup-workspaceSkill
- tune-workspaceSkill
- update-workspaceSkill
- workspace-helpSkill
The file
We split this skill 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 22
Read Adding an area in CONTEXT.md and follow it exactly: confirm it's really new, name it with the owner, copy the template, fill the …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
add-area
The workspace grows itself: when the business takes on a new standing domain of
work, it gets its own area, same structure as every other one. This behavior is
written down in one place — the Adding an area section of CONTEXT.md. You
don't need this command; just say a new kind of work has started and the assistant
runs the same thing. The command is the shortcut.
When to use
A kind of work has appeared that doesn't fit any existing area, and it's a standing
domain (sales, delivery, marketing, finance, support…), not a one-off project.
One-off work is a project — use new-project for that.
How to run it
Read Adding an area in CONTEXT.md and follow it exactly: confirm it's really
new, name it with the owner, copy the template, fill the contract — including the
Task | Load these | Skip these routing table and the source of truth — one question
at a time, register it in workspaces/REGISTRY.md, then show the result. The two
things that never bend: ask the owner before creating the folder (it changes the
workspace's shape), and one domain per area — never a catch-all "misc."
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.

