Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jamiemill/layers-skills --skill layers-orient- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads layers-orient automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
/layers-orient
Assumes /layers-intro has been loaded for framework context.
Orient is a rapid diagnostic — the front door for finding the live decisions the other skills then work. It maps the current state of decisions across all seven layers, identifies the bottleneck — the lowest layer with unresolved or risky decisions — and recommends where to focus next.
It is not a deep dive into any layer. That's what the individual layer skills are for. Orient answers the prior question: which layer deserves attention most urgently? Keep it fast and light — the output is a short audit and one recommendation, not a report.
What it assesses:
- Whether key decisions have been made at each layer, and how solidly
- Whether decisions treated as solid are actually assumptions
- Which layer is the most foundational with unresolved work, creating risk for everything above
Quality signals — when orient is done well:
- The bottleneck layer is specifically named, not vaguely gestured at
- Assumed layers are distinguished from Strong ones — they require different responses
- The recommendation connects to a specific skill with a clear reason
Guided session
Describe your design situation and what prompted you to pick it up, or say "let's orient" to start.
(Capture is opt-in and light — see /layers-intro. For orient, the audit table itself is usually all that's worth keeping.)
Then ask:
- What product or feature are you working on?
- What design challenge are you facing right now?
- How far along is this work — early exploration, active design, or fixing something in an existing product?
Listen for clues about which layers have already been worked through and which are thin or missing.
Layer audit
Work through each layer with one or two targeted questions. Rate each as: Strong / Partial / Assumed / Weak / Not started / N/A
Observed behaviour "What user research do you have? Have you spoken to users, observed them, or have analytics? Or is this mostly based on what the team believes users do?"
The domain "How well do you understand the space this product operates in — the real-world concepts, terminology, and how users think before your product enters the picture?"
User needs "Can you articulate what users are trying to achieve — not in features, but the underlying job and why it matters? Do you have job stories or equivalent?"
Product & service strategy "Do you know which specific user need this work targets and what business outcome it's meant to move? Is the connection between opportunity and business goal explicit, or informal?"
Conceptual model "Does the product have a clear model of the objects it works with — the things that exist, how they connect, and what vocabulary you use? Is this shared across the team, or does each person have their own version?"
Interaction structure and flow "Do you have a clear picture of the key user journeys — places, steps, decision points? A breadboard, rough flow, working code, or a description you can narrate?"
Surface "Is there an existing design system, visual language, or component library this needs to fit into?"
Decision landscape
Produce the audit as a table:
Layer | State | Notes
---------------------------|-------------|----------------------------------------
Observed behaviour | |
The domain | |
User needs | |
Product & service strategy | |
Conceptual model | |
Interaction structure | |
Surface | |
Bottleneck analysis
Identify the bottleneck layer: the lowest layer with Weak, Assumed, or Not started state. State it clearly: what decisions are missing, and what risk does that create for the layers above?
Also flag assumed layers — layers treated as decided but not verified. Assumptions that look solid are often where the most dangerous decisions hide.
If the designer has a deadline or constraint that changes the calculus, acknowledge it. Sometimes the right move isn't the most foundational one — name that tradeoff explicitly rather than ignoring it.
Recommendation
Recommend a specific skill to run next and why:
- Conceptual model →
/layers-conceptual-model - Product strategy →
/layers-product-strategy - User needs →
/layers-user-needs - Domain →
/layers-domain - Interaction structure →
/layers-interaction-flow - Observed behaviour →
/layers-observed-behaviour
Close with: "Want to run [skill] now, or is there something in this picture to push back on first?"
FAQ
What does the layers-orient skill do?
Diagnostic audit across all seven layers — identifies the bottleneck layer and recommends where to focus
How do I install layers-orient?
Run npx skills add https://github.com/jamiemill/layers-skills --skill layers-orient in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/layers-orient/ (personal) or .claude/skills/layers-orient/ (project).
Which AI agents can use layers-orient?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is layers-orient safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains layers-orient?
It is published by jamiemill in jamiemill/layers-skills. It has 1,957 recorded installs.
More from jamiemill/layers-skills
layers-conceptual-model
jamiemill/layers-skills
Techniques for defining the product's objects, relationships, states, and vocabulary independently of any interface — the most load-bearing layer
layers-intro
jamiemill/layers-skills
Framework orientation for Layers of Product Design — load this first; provides the context all other skills depend on
layers-interaction-flow
jamiemill/layers-skills
Techniques for mapping interaction structure and flow — places, affordances, edge cases, and failure paths — without committing to visual form
layers-product-strategy
jamiemill/layers-skills
Techniques for connecting user opportunities to business outcomes and solution bets, and testing the riskiest assumptions cheaply
layers-surface
jamiemill/layers-skills
Techniques for auditing and deciding the surface against the layers below — vocabulary, object consistency, completeness, feedback, hierarchy, accessibility
layers-domain
jamiemill/layers-skills
Techniques for mapping a domain's concepts, terminology conflicts, and bounded contexts — the raw material the conceptual model is built from
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.