elevation-and-depth

Establishes elevation and depth systems for interface components using tokens and dark-mode-aware styling.

33|6|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dembrandt/dembrandt-skills --skill elevation-and-depth-dembrandt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elevation-and-depth
Source: https://github.com/dembrandt/dembrandt-skills/tree/main/skills/elevation-and-depth
Command: npx skills add https://github.com/dembrandt/dembrandt-skills --skill elevation-and-depth-dembrandt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents flat, indistinct, or overly heavy interfaces by using consistent shadows, borders, gradients, and border-radius to communicate hierarchy and layering.

Core Features & Use Cases

  • Elevation Systems: Define tokenized shadow levels for cards, dropdowns, popovers, modals, drawers, and overlays.
  • Surface Definition: Pair subtle shadows with borders, consistent radius tokens, and restrained gradients to make surfaces feel clear and tactile.
  • Visual Review: Identify excessive shadows, inconsistent button radii, weak card boundaries, and elevation patterns that fail to communicate role or depth.

Quick Start

Use the elevation-and-depth skill to design a consistent shadow and border-radius system for the cards, dropdowns, and modals in this interface.

Frequently Asked Questions about elevation-and-depth

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

FAQPage Schema
How do I create a consistent elevation and shadow system for UI cards and modals?

Create a consistent elevation system by defining tokenized shadow levels for cards, dropdowns, popovers, and modals. Pair subtle diffuse shadows with defined edges and consistent border-radius values to make interface surfaces feel clear and tactile.

Why does my interface depth hierarchy look flat or overly heavy?

Interface depth hierarchy looks flat or heavy when shadows, borders, and gradients are applied inconsistently. Establish role-based shadow levels and use restrained gradients to communicate layering clearly without making surfaces feel visually heavy.

What's the best way to define depth hierarchy for dark mode components?

The best way to define depth hierarchy for dark mode components is to apply role-based shadow levels with subtle diffuse values and defined edges. This establishes consistent elevation across surfaces while reinforcing visual hierarchy in low-contrast environments.

How do I fix inconsistent button radii and weak card boundaries in my design?

Fix inconsistent button radii and weak card boundaries by standardizing border-radius tokens and pairing subtle shadows with defined borders. This creates clear surface boundaries and ensures tactile consistency across all interface components.

Can I use design tokens to manage elevation for dropdowns, popovers, and drawers?

Yes, you can use design tokens to manage elevation for dropdowns, popovers, and drawers. Tokenized shadow levels ensure consistent depth application across all elevated surfaces and streamline visual review processes for interface hierarchy.

When should I not use heavy shadows for interface layering?

You should avoid heavy shadows for interface layering when subtle diffuse values can communicate depth effectively. Excessive shadows make surfaces feel overly heavy and indistinct, failing to communicate role or hierarchy properly.