layers-intro
/layers-intro
Load this skill at the start of any design session. It provides the framework context that all other /layers-* skills depend on.
The framework
Layers of Product Design organises design work into seven layers across three zones. Layers have logical dependency: lower layers are foundations for upper ones. Weak lower layers create UX debt that propagates upward.
Reality — complex, contradictory, evolving. Source of all learning.
Problem space — knowledge gathered from reality:
- Observed behaviour — what users actually do
- The domain — concepts, terminology, and mental models that exist independently of any product
- User needs — what we think users are trying to achieve, and why
Solution space — deliberate decisions about what to build: 4. Product & service strategy — which needs to serve, and what business outcomes to target
More from jamiemill/layers-skills
layers-conceptual-model
Defines the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer
171layers-domain
Maps domain concepts, terminology conflicts, and bounded contexts — produces a noun harvest for the conceptual model layer
169layers-orient
Diagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus
168layers-product-strategy
Connects user opportunities to business outcomes and solution bets — produces a strategy tree and prioritised experiments
168layers-interaction-flow
Maps interaction structure and flow — produces breadboard notation with edge cases, failure paths, and open decisions
168layers-surface
Audits existing surface against lower-layer decisions and produces a surface decision inventory — vocabulary, object consistency, completeness, feedback, hierarchy, accessibility
167