layers-orient

Diagnose unresolved design layers and recommend the next skill.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/codesour-design/gravity --skill layers-orient
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: layers-orient
Source: https://github.com/codesour-design/gravity/tree/main/.agents/skills/layers-orient
Command: npx skills add https://github.com/codesour-design/gravity --skill layers-orient

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps designers and product teams identify the most critical unresolved design decisions by diagnosing which foundational layer is creating risk.

Core Features & Use Cases

  • Seven-Layer Audit: Evaluates observed behaviour, domain understanding, user needs, strategy, conceptual model, interaction structure, and surface design.
  • Bottleneck Identification: Distinguishes weak decisions and hidden assumptions to recommend the layer that needs attention next.
  • Use Case: A product team preparing a new feature can use this Skill to determine whether they should focus on user research, strategy, modelling, or interaction design before moving forward.

Quick Start

Describe your product design challenge and ask the layers-orient skill to identify the bottleneck layer and recommend the next step.

Frequently Asked Questions about layers-orient

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify which product design layer to prioritize for a new feature?

To identify which product design layer to prioritize, you can use a structured diagnostic audit that evaluates observed behavior, user needs, strategy, conceptual models, and interaction flows to pinpoint the bottleneck causing development risk.

What is a design audit for bottleneck analysis in UX strategy?

A design audit for bottleneck analysis is a diagnostic process that evaluates seven foundational design layers, from observed behavior to surface design, distinguishing validated decisions from hidden assumptions to reveal unresolved risks.

When do I need a conceptual model evaluation before building interaction flows?

You need a conceptual model evaluation before building interaction flows when foundational strategy and user needs are unresolved, as hidden assumptions in these layers create downstream product development risk and require a prioritized diagnostic audit.

How do I distinguish validated user research decisions from weak assumptions in product design?

You distinguish validated user research decisions from weak assumptions by applying a structured seven-layer diagnostic audit that evaluates decision quality across domain understanding, user needs, strategy, and conceptual modeling to expose hidden risks.

Can I use a design audit to prioritize between user research and interaction design tasks?

Yes, you can use a design audit to prioritize between user research and interaction design by evaluating layer decision quality across the product structure, identifying the most critical unresolved layer, and recommending the appropriate next step.