dark-mode-design

Translates light-mode color roles into dark appearances while preserving hierarchy and semantics.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill dark-mode-design-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dark-mode-design
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/dark-mode-design
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill dark-mode-design-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing a dark mode by inverting a light palette breaks semantic status colors, surface hierarchy, images, and browser chrome. This Skill provides a structured workflow to transform a product's appearance role-by-role so information hierarchy, interaction meaning, and brand identity survive across light and dark modes. ## Core Features & Use Cases - Role-preserving transformation: Maps base/raised surfaces, content hierarchy, interaction states, and semantic status colors to dark-specific values instead of inverting hex values. - Cross-mode verification checklist: Compares rendered light and dark artifacts across forms, overlays, focus states, charts, code surfaces, and platform-provided controls. - Asset and preference handling: Covers logos, SVGs, illustrations, system vs. app appearance overrides, and coordination with browser chrome via color-scheme. - Use Case: When adding a dark theme to a web product, use this Skill to audit every surface, state, and asset so the dark UI keeps the same hierarchy and meaning as the light UI rather than looking like a recolored copy. ## Quick Start Use the dark-mode-design skill to review my product's screens and produce a dark appearance that preserves the existing color roles and surface hierarchy.

Frequently Asked Questions about dark-mode-design

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

FAQPage Schema
How do I design a dark mode without inverting my light theme?

Map each semantic role (base surface, foreground hierarchy, interactive, destructive, brand) to dark-specific values instead of mathematically inverting hex colors. Then verify the same tasks in both appearances to confirm hierarchy and meaning are preserved.

Should dark mode backgrounds be pure black?

Not necessarily. Many systems express depth in dark themes with lighter layered surfaces, as in Carbon's dark theme. Choose pure black, near-black, or dark gray based on content type, platform, display, brand, and viewing context.

Does dark mode replace accessibility or high contrast support?

No. Dark appearance and increased/high contrast are separate axes. A dark UI alone does not satisfy high-contrast requirements; platforms with Increase Contrast or forced colors need separate verification, and broad audits belong to an accessibility review.

How should images and logos be handled in dark mode?

Treat assets as part of the theme: check logos with baked backgrounds, SVGs with hard-coded fills, illustrations, charts, and code syntax colors. Create appearance-specific variants when needed, but never mechanically darken photographs or user content.

How do I respect system dark mode preference while offering an app override?

Use the system-wide preference as the initial state, keep system/light/dark meanings distinct, and never silently overwrite user choice. Ensure pages, modals, and embedded regions do not split into mixed appearances when switching.