
Layers Domain
This is a structured approach to mapping a problem domain before you design anything. It's all about capturing how people think and talk about their work now, not how your product will work later. The discipline is resisting the urge to resolve conflicts: if two groups call the same thing by different names, or use the same word to mean different things, that's data about where your conceptual model will need to make choices. You get a toolkit of techniques like concept mapping, terminology audits, and noun harvests that feed directly into building your conceptual model. Most useful when you're entering a complex domain you don't fully understand yet.
- skills.sh installs
- 2K
- GitHub stars
- 314
- last updated
- Aug 21, 2026
Install
$ npx -y skills add jamiemill/layers-skills --skill layers-domain --agent claude-codeInstalls into .claude/skills of the current project.
Files
/layers-domain
Assumes /layers-intro has been loaded. This skill is a library of techniques, not a script — see "How to use these skills" there.
The domain layer maps what exists in the real world independently of any product: the concepts, terminology, processes, relationships, and mental models users bring with them. This is observation, not design.
The decisions this layer makes
- What the key concepts in this domain are, and how they relate
- What language people use — and where it conflicts or diverges
- Where the natural seams are: communities that use the same words differently
- What events and processes structure the domain's activity over time
If the domain is already well understood and uncontested, you may not need this layer — go straight to the conceptual model.
Disciplines — what keeps domain work honest
Sponsors
Details
- Repository
- github.com/jamiemill/layers-skills
- First seen
- Jun 3, 2026