Design Color
Use when creating or repairing a palette, semantic color roles, OKLCH scales, dark mode, contrast pairs, gamut fallbacks, “buat palet”, “warna brand”, “dark theme”, or color that must measurably pass accessibility requirements.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill design-colorgit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/design-color ~/.claude/skills/design-colorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Design Color ## Overview Build color from product meaning and measured pairs. OKLCH is a useful working space, not proof that contrast or gamut requirements pass. ## When to use - Palette, semantic roles, theme derivation, or color migration - OKLCH, Display P3, gamut mapping, or fallback work - Contrast, status colors, charts, or dark-mode complaints ## When to skip - Selecting which existing token preset applies → `tokens` - Accessibility audit without palette changes → `accessibility` - Surface depth without color-system work → `design-surfaces` ## MUST | Rule | Detail | |---|---| | **Preserve source** | Existing brand/project palette wins unless change is requested | | **Semantic roles** | Name by purpose, not raw hue or component instance | | **Measured contrast** | Test rendered foreground/background pairs; lightness heuristics are not proof | | **Gamut safety** | Provide target-browser fallback for colors outside supported gamut | | **Theme derivation** | Rebalance hierarchy and chroma; do not mechanically invert | | **No color-only meaning** | Pair status with text, icon, shape, or pattern | ## Workflow 1. **Inventory** — brand colors, tokens, themes, semantics, targets, and failing pairs. 2. **Model** — choose a working space and build neutral, accent, and semantic roles. 3. **Derive** — create states and themes while preserving meaning and hierarchy. 4. **Measure** — contrast, gamut, forced-colors, and color-vision risks.
Details
- Skill name
design-color- Repository
- sukirman1901/frontend-expert
- Path
skills/design-color/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Design Color skill do?
Use when creating or repairing a palette, semantic color roles, OKLCH scales, dark mode, contrast pairs, gamut fallbacks, “buat palet”, “warna brand”, “dark theme”, or color that must measurably pass accessibility requirements.
How do I install the Design Color skill?
Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Design Color popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/frontend-expert
Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Anti Slop Design
9sukirman1901/frontend-expert
Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.
Design Direction
9sukirman1901/frontend-expert
Senior frontend judgment before building UI — offer 2–3 approaches on distinct design axes (hierarchy, layout, density, interaction, expression) with tradeoffs; max 1–2 clarifying questions; optional inspiration (Linear/Stripe/…). Use at the start of non-trivial UI work and whenever direction is unclear. Skip for obvious bugfixes, single-token tweaks, or “just implement”. Runs before domain skills.
Data Fetching
9sukirman1901/frontend-expert
Async UI for remote data — loading, error, retry, empty, stale, cache boundaries. Use when building lists, detail pages, dashboards fed by API, React Query/SWR, fetch/loaders, or "ambil data", "loading state API", "retry".
Design Foundations
9sukirman1901/frontend-expert
Use when creating or repairing the structural layout of a web screen: grid, spacing rhythm, alignment, hierarchy, density, composition, whitespace, or content grouping. Trigger for blank layouts, inconsistent spacing, weak hierarchy, cluttered screens, "layout terasa berantakan", "struktur layout", or "rapikan struktur". Skip isolated color, typography, component-state, motion, and micro-polish changes.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.