new-domain
Skill253 starsChanged 11 months agoMITView on GitHub
Create a new .context domain folder with overview and patterns files following the Substrate methodology. Use when adding a new documentation domain to the project.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- cacardinal/lailatheir own version, first seen Jul 31, 2026
- cogotemartinez/ai-second-brain-templatetheir own version, first seen Feb 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- cogotemartinez/ai-second-brain-template★ 9same name
- cacardinal/laila★ 1same name
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.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-adrSkill
- generate-tool-configSkill
- validate-contextSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create a new .context/ domain folder for $ARGUMENTS.
- Very specific: line 12
Create the directory .context/$ARGUMENTS/
- Very specific: line 13
Create overview.md with this structure:
- Very specific: line 32
Create patterns.md if the domain has code patterns to document
- Very specific: line 33
Update .context/substrate.md to add the new domain under "Core Domains"
- Distinctive: line 34
Add the domain to CLAUDE.md under "Task-Specific Context" if it needs task-specific file pointers
- Distinctive: line 35
Update AGENTS.md to add the domain under "Context Files by Task"
- Very specific: line 38
Follow existing domain structure (see .context/auth/ or .context/api/ as examples)
- Distinctive: line 39
Use project-specific content, not generic best practices
- Distinctive: line 41
Keep files under 200 lines each
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Create a new .context/ domain folder for $ARGUMENTS.
Steps
- Create the directory
.context/$ARGUMENTS/ - Create
overview.mdwith this structure:
# Domain: [Name]
Brief description of what this domain covers.
## Overview
High-level description with context.
## Implementation Patterns
Code examples and standard approaches.
## Decision History & Trade-offs
Why choices were made, alternatives considered.
## Integration Points
How this domain connects to others.- Create
patterns.mdif the domain has code patterns to document - Update
.context/substrate.mdto add the new domain under "Core Domains" - Add the domain to
CLAUDE.mdunder "Task-Specific Context" if it needs task-specific file pointers - Update
AGENTS.mdto add the domain under "Context Files by Task"
Rules
- Follow existing domain structure (see
.context/auth/or.context/api/as examples) - Use project-specific content, not generic best practices
- Include decision rationale in every section
- Keep files under 200 lines each
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.

