How jamiemill/layers-skills works
This repository is a toolkit of AI skills for guiding product-design work through the seven Layers of Product Design. A designer starts with framework orientation, then either runs a diagnostic across the layers or opens a specific layer skill; those skills guide work and describe its outputs. The README documents the skill relationships and layer sequence, but no source excerpts were provided, so the graph does not infer implementation details beyond those documented capabilities.
Main entry points: layers-intro/SKILL.md Framework Intro · layers-orient/SKILL.md Layer Diagnostic · layers-domain/SKILL.md Domain · layers-user-needs/SKILL.md User Needs
Components 10
Orientation
- Framework Intro
skills/layers-intro/SKILL.md - Layer Diagnostic
skills/layers-orient/SKILL.md
Problem Space
- Observed Behaviour
skills/layers-observed-behaviour/SKILL.md - Domain
skills/layers-domain/SKILL.md - User Needs
skills/layers-user-needs/SKILL.md
Solution Space
- Product Strategy
skills/layers-product-strategy/SKILL.md - Conceptual Model
skills/layers-conceptual-model/SKILL.md - Interaction Flow
skills/layers-interaction-flow/SKILL.md - Surface
skills/layers-surface/SKILL.md
Other components
- Designer
Connections 30
- Designer → Framework Intro: starts with
README.md - Designer → Layer Diagnostic: runs diagnostic
README.md - Designer → Observed Behaviour: opens directly
README.md - Designer → Domain: opens directly
README.md - Designer → User Needs: opens directly
README.md - Designer → Product Strategy: opens directly
README.md - Designer → Conceptual Model: opens directly
README.md - Designer → Interaction Flow: opens directly
README.md - Designer → Surface: opens directly
README.md - Framework Intro → Layer Diagnostic: provides context
README.md - Framework Intro → Observed Behaviour: provides context
README.md - Framework Intro → Domain: provides context
README.md - Framework Intro → User Needs: provides context
README.md - Framework Intro → Product Strategy: provides context
README.md - Framework Intro → Conceptual Model: provides context
README.md - Framework Intro → Interaction Flow: provides context
README.md - Framework Intro → Surface: provides context
README.md - Layer Diagnostic → Observed Behaviour: audits layer
README.md - Layer Diagnostic → Domain: audits layer
README.md - Layer Diagnostic → User Needs: audits layer
README.md - Layer Diagnostic → Product Strategy: audits layer
README.md - Layer Diagnostic → Conceptual Model: audits layer
README.md - Layer Diagnostic → Interaction Flow: audits layer
README.md - Layer Diagnostic → Surface: audits layer
README.md - Observed Behaviour → Domain: logically precedes
README.md - Domain → User Needs: logically precedes
README.md - User Needs → Product Strategy: logically precedes
README.md - Product Strategy → Conceptual Model: logically precedes
README.md - Conceptual Model → Interaction Flow: logically precedes
README.md - Interaction Flow → Surface: logically precedes
README.md