agentleFS
Sign inStart free
bo-516bo-516/NiceDesign/skills/web/web-color-depth/SKILL.md

web-color-depth

Skill1 starsChanged 23 days agoMITView on GitHub

Use when choosing palettes, CSS color tokens, dark mode, elevation, or box-shadows for web UI. Covers color system + shadow/depth rules distilled from frontend-design, ui-craft, taste-skill, better-colors, DESIGN.md, smooth-shadows.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Prefer OKLCH for scales; hold hue, vary L/C.

    line 15
  2. Distinctive:

    Never default: purple→cyan gradients, neon glow, Inter+slate-900 purple SaaS look, cream+brass+espresso “premium” default.

    line 20
  3. Distinctive:

    Prefer APCA / WCAG AA min (text 4.5:1, UI 3:1).

    line 23
  4. Distinctive:

    Never grey text on saturated fills — use darker shade of the fill or alpha of on-color.

    line 26
  5. Distinctive:

    Prefer layered shadows (ambient + direct), soft blur, real offset — not zero-offset glow halos.

    line 38
  6. Distinctive:

    Cards only when elevation = hierarchy: Prefer spacing / hairline / surface tint first.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Web Color & Depth

Rules only. No process narration.

Color system

  • Prefer OKLCH for scales; hold hue, vary L/C.
  • Product UI: ≥90% neutrals + 1 accent. Semantic only: success / warning / error / info.
  • Marketing may commit harder; still one primary accent unless brief says otherwise.
  • Tint neutrals (warm ~60° or cool ~250°); avoid pure #000 / #fff on large surfaces.
  • One accent lock: same accent across the whole page/app surface.
  • Never default: purple→cyan gradients, neon glow, Inter+slate-900 purple SaaS look, cream+brass+espresso “premium” default.
  • Max accent saturation usually < 80% unless brand demands it.
  • Interactive states increase contrast vs rest (hover/active/focus).
  • Prefer APCA / WCAG AA min (text 4.5:1, UI 3:1). Mid-lightness surfaces (L≈0.4–0.7) are contrast traps.
  • Dark mode: color-scheme; elevate with white alpha overlays (≈6/8/12%) not inventing random lighter greys; reduce shadow intensity.
  • P3: ship sRGB-safe default, richer chroma under @media (color-gamut: p3).
  • Never grey text on saturated fills — use darker shade of the fill or alpha of on-color.
  • Tokens: primitives → semantic (--surface-*, --text-*, --status-*, --interactive-*). No raw hex in components.

Shadow / elevation

--shadow-sm: 0 1px 2px rgb(0 0 0 / 0.05);
--shadow-md: 0 4px 6px rgb(0 0 0 / 0.07), 0 1px 3px rgb(0 0 0 / 0.06);
--shadow-lg: 0 10px 15px rgb(0 0 0 / 0.1), 0 4px 6px rgb(0 0 0 / 0.05);
--shadow-xl: 0 20px 25px rgb(0 0 0 / 0.1), 0 8px 10px rgb(0 0 0 / 0.04);
  • Prefer layered shadows (ambient + direct), soft blur, real offset — not zero-offset glow halos.
  • Tint shadow toward surface hue when possible; avoid dirty pure-black on warm UIs.
  • Cards only when elevation = hierarchy. Prefer spacing / hairline / surface tint first.
  • Dark mode: shadow often fails → use 0 0 0 1px rgb(255 255 255 / 0.08) ring / inset highlight.
  • One elevation language per project: border or shadow for resting cards (no ghost-card both).
  • Ban: hard comic 4px 4px 0 (unless brutalist brief), neon outer glow as primary affordance, decorative blur orbs.
  • Image edge: inset outline rgb(0 0 0 / 0.1) light / rgb(255 255 255 / 0.1) dark — not tinted palette greys.
  • Optional craft: multi-layer stacks (3–6 layers) for soft depth; one strength per component state.

Do / Don't

DoDon't
CSS variables for all colors/shadowsMagic hex / one-off shadow in components
Accent 3–5 placements above the foldRainbow accents competing
Soft layered elevationSoft grey rgba(0,0,0,.1) under every identical card

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.

Check your setup, free