dark-mode
Design and implement dark mode (and theming) that maintains hierarchy, accessibility, and brand quality in low-light interfaces. Use when adding dark theme support, refining theme tokens, or ensuring parity between light and dark experiences.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- dark-mode
- description
- Design and implement dark mode (and theming) that maintains hierarchy, accessibility, and brand quality in low-light interfaces. Use when adding dark theme support, refining theme tokens, or ensuring parity between light and dark experiences.
03 SKILL.md 正文
Dark Mode
Overview
Dark mode is not an inversion of light mode. It requires deliberate elevation, contrast, and color decisions to keep interfaces readable and comfortable.
When to Use
- Adding dark theme support to a product
- Building theme-aware design systems
- Fixing contrast or hierarchy issues in existing dark UI
Core Practices
- Use semantic tokens that map to theme-specific values
- Desaturate and re-tune brand colors for dark surfaces
- Maintain elevation through surface steps, not only shadows
- Check contrast for text, icons, and interactive states
- Respect system preference and offer user override
- Test critical flows in both themes
Principles
- Avoid pure #000 backgrounds in most product UIs
- Don’t rely on opacity tricks that tank contrast
- Images and illustrations may need theme-specific treatment
- Dark mode should feel intentional, not like a filter
Verification
- [ ] Text and controls meet contrast requirements in dark theme
- [ ] Hierarchy remains clear on dark surfaces
- [ ] Theme switching is predictable and persistent
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.