agentleFS
phazurlabsphazurlabs/sumi/skills/shadow-elevation-density/SKILL.md

shadow-elevation-density

Skill58 starsChanged 23 days agoApache-2.0View on GitHub

Elevation, shadow, depth, and density systems: shadow scales, elevation hierarchy, glassmorphism, blur effects, border-radius systems, and compact, comfortable, and spacious density modes with production CSS. Use when surfaces look flat or float wrongly, or when tuning information density.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every reference file in this skill writes against these tokens.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shadow, Elevation and Density

Mental model

Elevation is a lie the interface tells consistently. It works only when every element agrees on where the light is and how far off the surface it sits.

Three rules carry most of the weight:

  • One light source. Top-center, slightly left in LTR. Every element at the same elevation casts the same direction of shadow. Two light sources destroy spatial coherence faster than any other single mistake.
  • Layer, don't darken. A realistic shadow is two or three stacked shadows — a tight dark one for contact, a wide soft one for ambience. A single large blurred shadow reads as a sticker, not a raised surface.
  • Never pure black. oklch(0 0 0 / a) at low alpha, or better, a shadow tinted toward the surface's own hue. Pure black at high alpha is the single most common reason a UI looks cheap.

Density is the same discipline applied to space rather than depth: pick one of three modes and hold it, because a screen that mixes compact and comfortable reads as unfinished rather than flexible.

Shadow anatomy, for reading the values below: x-offset y-offset blur spread color. Y-offset places it, blur softens it, spread tightens or expands it. Higher elevation means larger y-offset, larger blur, lower alpha.

Constants

Every reference file in this skill writes against these tokens. They must be in context for the recipes to be usable.

:root {
  --shadow-0: none;
  --shadow-1: 0 1px 2px oklch(0 0 0 / 0.06), 0 1px 3px oklch(0 0 0 / 0.10);
  --shadow-2: 0 2px 4px oklch(0 0 0 / 0.04), 0 4px 8px oklch(0 0 0 / 0.06), 0 12px 24px oklch(0 0 0 / 0.06);
  --shadow-3: 0 4px 8px oklch(0 0 0 / 0.04), 0 8px 16px oklch(0 0 0 / 0.06), 0 20px 40px oklch(0 0 0 / 0.10);
  --shadow-4: 0 8px 16px oklch(0 0 0 / 0.06), 0 16px 32px oklch(0 0 0 / 0.08), 0 32px 64px oklch(0 0 0 / 0.12);

  --z-base:           0;
  --z-raised:         1;
  --z-dropdown:       100;
  --z-sticky:         200;
  --z-fixed:          300;
  --z-drawer:         400;
  --z-modal-backdrop: 500;
  --z-modal:          510;
  --z-popover:        600;
  --z-toast:          700;
  --z-tooltip:        800;
  --z-drag:           900;
  --z-max:            9999;
}

The z-index scale uses 100-step intervals so sub-layers fit between named levels without renumbering. --z-max is for debug overlays only; reaching for it in product code means a stacking context is wrong somewhere above.

Index

ConcernLevel / modeReference
Resting surface, card at rest--shadow-1shadow-system-recipes.md
Raised card, hover state--shadow-2shadow-system-recipes.md
Dropdown, popover, sticky header--shadow-3shadow-system-recipes.md
Modal, drawer, command palette--shadow-4shadow-system-recipes.md
Minimal system (Linear, Vercel)—shadow-system-recipes.md
Layered system (Stripe)—shadow-system-recipes.md
Material system (Google)—shadow-system-recipes.md
Brand-tinted / colored shadows—shadow-system-recipes.md
Dark-mode ambient glow—shadow-system-recipes.md
Neumorphic—shadow-system-recipes.md
Z-index conflicts, stacking contexts—elevation-hierarchy.md
Surface layer architecture—elevation-hierarchy.md
Compact / comfortable / spacious—density-modes.md
Component-specific density rules—density-modes.md
Radius scale, nested radius rule—border-radius-systems.md
Sharp / rounded / pill systems—border-radius-systems.md
Frosted glass, acrylic, blur—glassmorphism-effects.md
Animating elevation on hover—shadow-animation.md
Depth without shadow; materials—depth-and-materials.md

Reference architecture

FileCoversLines
references/shadow-system-recipes.md11 complete shadow systems1016
references/glassmorphism-effects.md10 glass and blur recipes1101
references/border-radius-systems.mdradius scale, nested rule, 5 systems934
references/density-modes.mdfull token specs for 3 modes923
references/elevation-hierarchy.mdz-index, stacking, surfaces608
references/depth-and-materials.mddepth cues, surface materials145
references/shadow-animation.mdtransitioning elevation86

What every reference file contains

  1. The philosophy — what the treatment is for and when it is wrong
  2. Complete CSS custom properties, ready to paste
  3. Named variants with the condition that selects each
  4. Light and dark values, not light only
  5. Component-specific application notes
  6. Performance cost, where the technique has one
  7. Anti-patterns specific to that treatment

Routing

For a shadow system — minimal (Linear/Vercel), layered (Stripe), Material, colored/brand-tinted, dark-mode ambient glow, and neumorphic, each as complete CSS: read references/shadow-system-recipes.md.

For stacking and z-index — the scale, stacking-context management, surface layer architecture, elevation-to-shadow mapping, and the common z-index bugs: read references/elevation-hierarchy.md.

For density — full token specifications for compact, comfortable and spacious, the side-by-side comparison, implementation strategies and component-specific rules: read references/density-modes.md.

For corner radius — the scale, the nested radius rule, component conventions, and five named systems from sharp/corporate to fully rounded: read references/border-radius-systems.md.

For glass and blur — glassmorphism fundamentals and ten recipes including frosted glass (Apple) and acrylic (Windows): read references/glassmorphism-effects.md.

For animating elevation — what to transition, what it costs, and the compositor-friendly alternatives to animating box-shadow directly: read references/shadow-animation.md.

For depth without shadow — overlap, scale, blur, parallax, borders, and the surface material treatments: read references/depth-and-materials.md.

Performance

box-shadow is painted, not composited. Animating it forces repaint on every frame. Transition opacity on a stacked pseudo-element instead, or accept the cost only on small elements. backdrop-filter is expensive on large surfaces and on low-end Android; always ship a solid-color fallback behind an @supports query.

Cross-References

  • ui-visual-design-system — where elevation sits in the wider visual language
  • platform-visual-standards — iOS and Material 3 have their own elevation models
  • animation-recipe-library — the easing tokens shadow transitions use
  • design-systems-architecture — how these tokens fit the three-tier model
  • figma-design-tool-workflows — setting these up as Figma effect styles

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.