jamiemill/layers-skills
9 skills14.2k installs2.5k starsGitHub
Install
npx skills add https://github.com/jamiemill/layers-skillsSkills in this repo
1Layers Conceptual Modellayers-conceptual-model is a Claude Code skill from jamiemill/layers-skills that applies techniques for defining a product's conceptual model—the objects it recognizes, how they relate, what states they occupy, and the controlled vocabulary naming them. It assumes layers-intro has been loaded and operates as a technique library rather than a rigid script, deliberately separating domain modeling from user mental models or interface layout. Developers reach for layers-conceptual-model when starting a new product area, refactoring confusing terminology, or aligning engineering and design on canonical entity definitions before writing schemas, APIs, or UI components. The conceptual model is described as the most neglected load-bearing layer in the Layers framework.1.6kinstalls2Layers Introlayers-intro in jamiemill/layers-skills is the required entry skill for the Layers of Product Design framework used by all other /layers-* skills. The framework organizes design work into seven layers across three zones with logical dependency: weak lower layers create UX debt that propagates upward. The Reality zone captures complex, contradictory, evolving inputs; the Problem space gathers observed behavior and related knowledge; upper layers build on those foundations toward solution decisions. Developers and designers load layers-intro at the start of any design session so agents understand layer ordering, dependency rules, and vocabulary before applying specialized layer skills. The skill prevents agents from jumping to UI polish before behavioral and problem foundations are established. Triggers include starting a design session, loading layers framework context, and onboarding agents to the seven-layer product design model.1.6kinstalls3Layers Surfacelayers-surface is a technique library from the Layers skills framework for auditing and deciding the surface layer against decisions made below it. The skill assumes layers-intro has been loaded first and is not a script—it guides agents through reviewing vocabulary, object consistency, completeness, feedback, hierarchy, and accessibility across screens, voice, physical devices, and services. Developers reach for layers-surface when a product’s UI copy, visual language, or interaction feedback feels misaligned with the underlying domain model or earlier architecture choices. It complements deeper Layers skills by focusing on what people actually encounter at the medium-specific surface.1.6kinstalls4Layers Product Strategylayers-product-strategy is the first layer skill in jamiemill/layers-skills, treating strategy as the conversion point from problem-space understanding into deliberate scope and direction choices. It is a library of techniques—not a fixed script—for deciding which user needs to serve, which business outcomes to target, and how to test the riskiest assumptions cheaply before build. Developers reach for layers-product-strategy when feature ideas exist but outcome alignment, opportunity prioritization, or assumption risk is unclear. The skill assumes layers-intro is loaded and complements layers-orient, which identifies which layer needs attention. It produces explicit decisions about business outcomes, user opportunities, and solution bets rather than jumping to implementation.1.6kinstalls5Layers Orientlayers-orient is the entry diagnostic in the Layers decision framework from jamiemill/layers-skills. It assumes layers-intro context is loaded, then rapidly maps the current state of decisions across all seven layers, finds the lowest layer still carrying unresolved or risky decisions, and recommends the next focus area without doing a deep dive. Developers reach for layers-orient when multiple parallel concerns exist and it is unclear whether strategy, architecture, or delivery deserves attention first. The skill answers which layer deserves attention most urgently and hands off to layer-specific skills for depth. It is intentionally a front-door audit, not a replacement for individual layer workflows.1.6kinstalls6Layers Interaction Flowlayers-interaction-flow is a jamiemill/layers-skills technique library that sits between the conceptual model layer (what exists) and the surface layer (how it looks). After loading layers-intro, developers use it to define places users navigate, available affordances, presented content, and transitions between states—including edge cases and failure paths. Breadboard-style outputs keep structure explicit without committing to pixels or components. Reach for layers-interaction-flow when wireframes or code are premature but you need agreement on navigation, empty states, errors, and multi-step flows.1.6kinstalls7Layers Domainlayers-domain is part of jamiemill/layers-skills and assumes layers-intro has been loaded first. The skill is a technique library—not a fixed script—for observing what exists in the real world independently of any product: concepts, language, processes, relationships, and user mental models. It helps decide key domain concepts, how they relate, and where terminology conflicts or bounded contexts appear. Developers reach for layers-domain when starting a new product area, entering an unfamiliar industry, or before committing to data models, APIs, or UX flows that encode the wrong abstractions.1.6kinstalls8Layers User Needslayers-user-needs is a jamiemill/layers-skills library for eliciting and prioritizing user needs, pains, and desires that feed product strategy. The skill assumes layers-intro is loaded and operates as techniques rather than a rigid script, sitting between messy behavioral observation and deliberate solution decisions. Outputs are opportunities: needs users want to achieve, pains blocking them, and desires shaping motivation, expressed as prioritized job stories surfacing real bets before feature commitment. Developers and PMs invoke layers-user-needs during discovery workshops, interview synthesis, or roadmap framing when assumptions need structure without jumping straight to implementation tickets.1.6kinstalls9Layers Observed Behaviourlayers-observed-behaviour is a Layers skill from jamiemill/layers-skills that provides techniques for planning user research and synthesizing material into grounded, confidence-rated findings about actual user behavior. It assumes /layers-intro has been loaded and operates as a technique library rather than a rigid script. The observed behaviour layer represents what users actually do, distinct from assumptions or desired behavior. The skill detects two situations: Plan when no research exists yet and a study must be designed, and Synthesise when research material already exists and needs structured findings. Developers reach for layers-observed-behaviour when product decisions need evidence-backed behavioral insights instead of stakeholder opinions alone.1.6kinstalls