Back to Skills

layers-intro

Framework orientation for Layers of Product Design — load this first; provides the context all other skills depend on

284stars24forksUpdated 8/6/2026

Security Assessment

Safe(98/100)
Security Score98/100

About layers-intro

This skill is the orientation and entry point for the "Layers of Product Design" framework, meant to be loaded at the start of any design session because every other `/layers-*` skill depends on the context it establishes. It presents design as decision-making: organising work into seven layers across three zones (reality, problem space, and solution space), where lower layers are foundations for upper ones and weak foundations propagate UX debt upward. The seven layers run from observed behaviour and the domain and user needs, up through product strategy, conceptual model, interaction structure, and finally surface.

The skill's substance is a set of operating principles and a usage model. It defines four kinds of design progress — making decisions, uncovering unmade decisions, evaluating existing decisions, and prioritising them — and stresses that uncovering and evaluating are often more valuable than resolving. It instructs the practitioner to treat each layer skill as a technique library rather than a script: find the live decisions, offer a fitting technique, and capture only the residue instead of generating heavy artefacts. Ten cross-session principles reinforce this, including working one layer at a time, checking foundations before building upward, flagging bad decisions rather than only missing ones, and the "push forward, pull back" idea of probing an upper layer to learn what a lower one actually needs. A dedicated section draws attention to frequently overlooked temporal decisions at the conceptual-model and interaction layers.

The target users are product designers, UX practitioners, and teams adopting this framework. It is a conceptual guide and methodology primer with no code, tools, or side effects — useful whenever someone wants a shared vocabulary and disciplined approach for structuring product-design work.

FAQ

When should this skill be loaded?

At the start of any design session. It provides the framework context that all other `/layers-*` skills depend on, so it is intended to be loaded first.

What are the seven layers?

Observed behaviour, the domain, and user needs (problem space), then product and service strategy, conceptual model, interaction structure and flow, and surface (solution space), all grounded in reality.

Is the framework a linear process?

No. The layers have logical dependency but you can enter anywhere; the guidance is to always check whether the foundations below are sound before building upward.

What does 'capture decisions, not transcripts' mean?

It advises defaulting to lightweight output — the decisions made, decisions surfaced, and open questions — rather than long documents, since the conversation itself is already a record and a diagram earns its place only when it encodes a decision.

Does the skill make design decisions for you?

No. Its stated job is to help the designer make better decisions, not to make decisions for them, and to steer rather than jump to surface-level output before foundations are set.

Install layers-intro

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill