layers-intro

Organize product design work into layered decision areas and identify foundational gaps.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/harshilLakhani22/monali-ai-property --skill layers-intro-harshillakhani22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: layers-intro
Source: https://github.com/harshilLakhani22/monali-ai-property/tree/main/.agents/skills/layers-intro
Command: npx skills add https://github.com/harshilLakhani22/monali-ai-property --skill layers-intro-harshillakhani22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives you a shared framework for understanding product design work across layers, helping you avoid jumping too early to visuals or features before the underlying problem is clear.

Core Features & Use Cases

  • Layered orientation: Understand how reality, problem space, and solution space relate across seven layers.
  • Decision-making support: Surface missing, risky, or conflicting design decisions before they become UX debt.
  • Conceptual clarity: Use the framework to check foundations such as user needs, conceptual model, interaction flow, and surface.
  • Example use case: When starting a new product or redesign session, use this Skill to choose the right layer to investigate first and identify what should be decided next.

Quick Start

Use the layers-intro skill to help me orient a design session, identify the right layer to focus on, and capture the key decisions that need to be made.

Frequently Asked Questions about layers-intro

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

FAQPage Schema
What is a layered framework for product design and how does it work?

A layered product design framework organizes work across seven distinct decision areas, mapping how reality, problem space, and solution space relate. It works by separating foundational decisions from surface-level features to ensure structural alignment.

How do I orient a UX design session to avoid jumping to visuals too early?

To orient a UX design session, use a seven-layer conceptual model to identify the correct investigative starting point. This ensures user needs and problem framing are validated before committing to interaction flows and surface-level visual decisions.

When do I need a conceptual model for product discovery and critique?

You need a conceptual model during product discovery and critique sessions when problem framing and solution structure require alignment. It surfaces missing or conflicting design decisions, preventing foundational gaps from becoming UX debt.

Can I use this layered design approach for dependency checking between UX layers?

Yes, you can use the layered design approach for dependency checking between UX layers. The framework supports decision auditing across reality, problem space, and solution space to identify risky dependencies before they impact the interaction design.

What is the best way to identify foundational gaps in an interaction design strategy?

The best way to identify foundational gaps in an interaction design strategy is to audit decisions across seven distinct layers. This checks foundational elements like user needs and conceptual models against interaction flows to surface missing requirements.

Why does my product redesign strategy have conflicting design decisions across layers?

Conflicting design decisions across layers occur when problem framing and solution structures are misaligned. Applying a seven-layer orientation framework audits these dependencies, identifying where foundational user needs conflict with surface-level design choices.