Jamie Mill
a201dc8c20
- intro: new principle 10 — probe a higher layer to discover what a lower one needs, then come back down (probing to learn != committing to build) - conceptual-model: distinguish can-be-an-object from should-be-first- class; mark bet-dependent objects provisional; "sketch the flow first" technique; don't treat strategy vocabulary as objects Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.