Design
Plugin
layers-skills
A set of AI skills that guide product designers through the Layers of Product Design framework — a structured way to think about design work across seven layers, from observed user behaviour through to surface decisions.
Plugin Signal56/100Fair
maintained65
capable48
documented55
adopted52
Install
$ npx -y skills add jamiemill/layers-skills --agent claude-code
Stats
291
Stars
24
Forks
Maintained
Maintenance
MIT
License
2mo ago
Last commit
3mo ago
Created
Repo: jamiemill/layers-skills
What's inside
Skill(9 skills)
/layers-conceptual-modelTechniques for defining the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer/layers-domainTechniques for mapping a domain's concepts, terminology conflicts, and bounded contexts — the raw material the conceptual model is built from/layers-interaction-flowTechniques for mapping interaction structure and flow — places, affordances, edge cases, and failure paths — without committing to visual form/layers-introFramework orientation for Layers of Product Design — load this first; provides the context all other skills depend on/layers-observed-behaviourTechniques for planning user research and synthesising it into grounded, confidence-rated findings about what users actually do/layers-orientDiagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus
README
Layers of Product Design — Skills Toolkit
A set of AI skills that guide product designers through the Layers of Product Design framework — a structured way to think about design work across seven layers, from observed user behaviour through to surface decisions.
Each skill facilitates work at one layer: explaining the layer's nature, naming the decisions that need to be made, and optionally running a structured working session using proven methods.
How it works
Load /layers-intro at the start of any session. It provides the framework context all other skills depend on. Then either run /layers-orient to find out where to focus, or jump directly to the layer you're working at.
Start here
| Skill | What it does |
|---|---|
/layers-intro | Framework orientation — load this first |
/layers-orient | Diagnostic audit across all seven layers; identifies where to focus |
Problem space
Work in the problem space builds understanding of users and their context, independently of any solution.
| Layer | Skill | What it produces |
|---|---|---|
| 1 · Observed behaviour | /layers-observed-behaviour | Candidate job stories with confidence ratings |
| 2 · The domain | /layers-domain | Concept map, terminology conflicts, noun harvest |
| 3 · User needs | /layers-user-needs | Prioritised job stories (needs, pains, desires) |
Solution space
Work in the solution space converts problem space understanding into deliberate decisions about what to build and how.
| Layer | Skill | What it produces |
|---|---|---|
| 4 · Product & service strategy | /layers-product-strategy | Opportunity Solution Tree with prioritised bets |
| 5 · Conceptual model | /layers-conceptual-model | Object map, state diagrams, ubiquitous language |
| 6 · Interaction structure and flow | /layers-interaction-flow | Breadboard with edge cases and open decisions |
| 7 · Surface | /layers-surface | Audit findings and surface decision inventory |
The framework in brief
Layers have logical dependency — lower layers are foundations for upper ones. Weak lower layers create UX debt that propagates upward. This is not a linear process: you can enter at any layer, but it's always worth checking whether the foundations below are sound.
Reality → Problem space (observed behaviour → domain → user needs) → Solution space (strategy → conceptual model → interaction structure → surface) → Reality
The most neglected layer is almost always the conceptual model: the objects, relationships, states, and vocabulary the product works with. If you're unsure where to start, run /layers-orient.
License
MIT — see LICENSE. Fork it, adapt it, ship it. Attribution is appreciated but not required.
File tree
jamiemill/layers-skillsView on GitHub
LICENSE
README.md
skills/
layers-conceptual-model/
SKILL.md
layers-domain/
SKILL.md
layers-interaction-flow/
SKILL.md
layers-intro/
SKILL.md
layers-observed-behaviour/
SKILL.md
layers-orient/
SKILL.md
layers-product-strategy/
SKILL.md
layers-surface/
SKILL.md
layers-user-needs/
SKILL.mdFAQ
layers-skills is a Claude Code plugin with 9 hand-picked skills for design work, indexed on Flowy. Install it with the command on its page. It includes layers-conceptual-model, layers-domain, layers-interaction-flow. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
- What is layers-skills?
- A set of AI skills that guide product designers through the Layers of Product Design framework — a structured way to think about design work across seven layers, from observed user behaviour through to surface decisions.
- How do I install layers-skills?
- Run these in Claude Code: npx -y skills add jamiemill/layers-skills --agent claude-code. Then prompt normally.
- Does layers-skills auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
- Is layers-skills free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.