Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

curiositech/skills/dark-mode-design-expert

Name: skills/dark-mode-design-expert
Author: curiositech

skills/dark-mode-design-expert/SKILL.md

npx skillsauth add curiositech/windags-skills skills/dark-mode-design-expert

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

Dark Mode Design Expert

Master dark mode UI design with atmospheric theming, WCAG accessibility, and cross-platform best practices. Specializes in weather/sky/ocean-inspired color systems that adapt to time of day and environmental conditions.

Decision Points

When Dark Mode is Right for the User

IF user environment = bright (outdoor/office) AND device ≠ OLED
  → Recommend light mode (better readability)

ELSE IF user environment = low light (evening/bedroom)
  → Activate dark mode (reduce eye strain)

ELSE IF device = OLED AND battery concern = high
  → Suggest dark mode (39-47% power savings at max brightness)

ELSE IF user has astigmatism flags (accessibility preference)
  → Default to light mode (dark text prevents halation)

ELSE
  → Respect system preference (prefers-color-scheme)

Contrast Ratio Decision Tree

FOR text content:
  IF text size ≥ 24px (large text)
    → Target 4.5:1 minimum, 7:1 ideal
  ELSE IF body text
    → Target 7:1+ (AAA compliance)
  ELSE IF disabled/decorative
    → 3:1 acceptable

FOR interactive elements:
  IF primary action button
    → 4.5:1+ against background
  ELSE IF border/icon
    → 3:1+ minimum

Elevation Method Selection

IF theme = light mode
  → Use box-shadow for elevation
  → Shadows = rgba(0,0,0,0.1-0.3)

ELSE IF theme = dark mode
  → Use lighter surface colors
  → Each level = base + 5-11% white overlay
  → NO shadows (invisible on dark)

ELSE IF theme = atmospheric (storm/night)
  → Use colored glow effects
  → box-shadow with theme accent color

Color Adjustment Strategy

IF switching light → dark:
  IF color lightness > 70%
    → Increase saturation 10-20%
    → Reduce lightness to 40-60%
  
  IF color is brand primary
    → Use 400-level instead of 600-level
    → Test against dark background
  
  IF color is gray/neutral
    → Invert but avoid pure white/black
    → Use #f1f5f9 instead of #ffffff

ELSE IF switching dark → light:
  → Reverse above rules
  → Test readability on white background

Failure Modes

1. Pure Black Syndrome

Symptoms: Background is #000000, text is #ffffff, harsh contrast Detection: Check if background HSL lightness = 0% Fix: Replace with near-black (#0c1222, #121212) and off-white (#f1f5f9)

2. Shadow Invisibility

Symptoms: Cards have no elevation in dark mode, UI feels flat Detection: box-shadow values unchanged between themes Fix: Replace shadows with lighter surface colors in dark mode

/* Wrong */
.card { box-shadow: 0 4px 8px rgba(0,0,0,0.1); }

/* Right */
:root.theme-dark .card { 
  background: var(--surface-elevated); 
  box-shadow: none; 
}

3. Color Inversion Laziness

Symptoms: Colors look washed out or invisible in dark mode Detection: Same hex values used in both themes Fix: Manually adjust each color for its new background context

4. Flash of Wrong Theme (FOWT)

Symptoms: Page loads light, then flashes to dark after 100-200ms Detection: Theme change visible during page load Fix: Inline blocking script in <head> before any CSS:

<script>
(function(){
  if(localStorage.theme==='dark')
    document.documentElement.classList.add('theme-dark');
})();
</script>

5. System Preference Ignorance

Symptoms: App forces one theme regardless of user's OS setting Detection: No prefers-color-scheme media queries Fix: Default to system preference, allow manual override

Worked Examples

Example 1: Weather App Dashboard Theming

Scenario: Building a weather app that shows current conditions with background that matches the weather and time of day.

User Context:

Time: 8:30 PM (night)
Weather: Clear skies
Device: iPhone with OLED screen
User preference: System (dark mode enabled)

Decision Process:

Time-based atmosphere: 8:30 PM → Night theme (deep blues, bioluminescent accents)
Weather modifier: Clear skies → No storm effects, use starry gradient
Device optimization: OLED → Prioritize true blacks for battery savings
System preference: Dark mode → Confirm night theme choice

Implementation:

/* Night + Clear Weather */
:root.atmosphere-night-clear {
  --bg-primary: #0c1222;        /* Deep navy, not pure black */
  --bg-elevated: #1a1f3a;       /* Lighter for cards */
  --text-primary: #f1f5f9;      /* Off-white, not pure white */
  --accent: #22d3ee;            /* Cyan for bioluminescent feel */
  
  /* Starry effect */
  background-image: radial-gradient(
    circle at 20% 30%, rgba(34, 211, 238, 0.1) 0%, transparent 50%
  );
}

What novice would miss:

Using pure black (#000) causing OLED smearing
Same accent color as light mode becoming invisible
No elevation strategy for dark cards

Expert catches:

Near-black with blue tint maintains atmosphere
Brighter cyan accent maintains visibility
Lighter surfaces create elevation without shadows

Example 2: Dashboard with Accessibility Conflict

Scenario: Enterprise dashboard needs to support users with astigmatism (prefer light mode) and users with light sensitivity (prefer dark mode).

Conflict: Astigmatism users experience "halation" (text bleeding) in dark mode, while light-sensitive users get eye strain from light mode.

Decision Process:

Detect accessibility preferences: Check for prefers-reduced-contrast and user-set preferences
Compromise solution: Medium contrast theme that works for both groups
Escape hatches: Explicit high-contrast and extra-dark options

Implementation:

/* Medium contrast theme */
:root.theme-accessible {
  --bg-primary: #1e293b;        /* Not too dark */
  --bg-elevated: #334155;       /* Clear hierarchy */
  --text-primary: #e2e8f0;      /* Not pure white */
  --contrast-ratio: 12:1;       /* Between 7:1 and 21:1 */
}

/* High contrast escape hatch */
:root.theme-high-contrast {
  --bg-primary: #000000;
  --text-primary: #ffffff;
  --contrast-ratio: 21:1;
}

Expert considerations:

Provides theme options rather than forcing one choice
Tests contrast ratios programmatically
Offers escape hatches for extreme preferences

Example 3: OLED Battery Optimization Conflict

Scenario: Mobile news app user reports poor battery life, but switching to dark mode makes article text harder to read.

Analysis:

User is outdoors frequently (bright environment)
OLED phone at 80%+ brightness most of the time
Dark mode would save 35% battery but reduces readability

Decision Process:

Environment detection: Use ambient light sensor if available
Adaptive brightness: Auto-adjust contrast based on screen brightness
Smart defaults: Dark mode when brightness >70% AND environment is controlled

Implementation:

/* Brightness-adaptive contrast */
:root.brightness-high {
  /* Higher contrast for outdoor reading */
  --text-primary: #000000;      /* Pure black for maximum contrast */
  --bg-primary: #ffffff;        /* Pure white background */
}

:root.brightness-low {
  /* Lower contrast for indoor comfort */
  --text-primary: #f1f5f9;
  --bg-primary: #0c1222;
}

What novice would miss:

Assuming dark mode is always better for OLED
Not considering reading environment
Fixed contrast ratios regardless of brightness

Expert solution:

Context-aware theming based on device state
Battery vs. readability trade-offs clearly communicated
User education about when each mode works best

Quality Gates

[ ] Primary text contrast ≥7:1 in both themes (AAA compliance)
[ ] Interactive elements contrast ≥4.5:1 (AA compliance)
[ ] Focus indicators clearly visible in both themes
[ ] Elevation hierarchy works without shadows in dark mode
[ ] No pure black (#000000) or pure white (#ffffff) backgrounds
[ ] Color adjustments made for each theme (not simple inversion)
[ ] System preference respected on first load (prefers-color-scheme)
[ ] No flash of wrong theme during page load
[ ] Theme preference persists across sessions
[ ] OLED-optimized colors when device supports it

NOT-FOR Boundaries

This skill handles dark mode implementation. For other needs:

Color palette creation → Use color-theory-palette-harmony-expert instead
Typography in themes → Use typography-expert for font selection and sizing
Component library structure → Use design-system-creator for broader architecture
Specific contrast auditing → Use color-contrast-auditor for testing color pairs
Brand identity decisions → Use web-design-expert for overall visual direction
Animation/interaction → Use frontend-expert for theme transition animations

Delegate when you see:

Requests to create entirely new color palettes from scratch
Questions about font pairing or typography hierarchy
Component architecture decisions beyond theming
Specific WCAG audit requirements for compliance documentation
Brand strategy or identity design questions

curiositech/skills/dark-mode-design-expert

skills/dark-mode-design-expert/SKILL.md

--- license: Apache-2.0 category: Design & Creative tags: - dark-mode - theming - design - accessibility - contrast --- # Dark Mode Design Expert Master dark mode UI design with atmospheric theming, WCAG accessibility, and cross-platform best practices. Specializes in weather/sky/ocean-inspired color systems that adapt to time of day and environmental conditions. ## Decision Points ### When Dark Mode is Right for the User ``` IF user environment = bright (outdoor/office) AND devic

development

Updated Apr 4, 2026

$ install --global

skillsauth

npx skillsauth add curiositech/windags-skills skills/dark-mode-design-expert

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Apr 4, 2026, 2:09 PM18.1s4 files scanned

SKILL.md

license:: Apache-2.0
category:: Design & Creative

Dark Mode Design Expert

Decision Points

When Dark Mode is Right for the User

IF user environment = bright (outdoor/office) AND device ≠ OLED
  → Recommend light mode (better readability)

ELSE IF user environment = low light (evening/bedroom)
  → Activate dark mode (reduce eye strain)

ELSE IF device = OLED AND battery concern = high
  → Suggest dark mode (39-47% power savings at max brightness)

ELSE IF user has astigmatism flags (accessibility preference)
  → Default to light mode (dark text prevents halation)

ELSE
  → Respect system preference (prefers-color-scheme)

Contrast Ratio Decision Tree

FOR text content:
  IF text size ≥ 24px (large text)
    → Target 4.5:1 minimum, 7:1 ideal
  ELSE IF body text
    → Target 7:1+ (AAA compliance)
  ELSE IF disabled/decorative
    → 3:1 acceptable

FOR interactive elements:
  IF primary action button
    → 4.5:1+ against background
  ELSE IF border/icon
    → 3:1+ minimum

Elevation Method Selection

IF theme = light mode
  → Use box-shadow for elevation
  → Shadows = rgba(0,0,0,0.1-0.3)

ELSE IF theme = dark mode
  → Use lighter surface colors
  → Each level = base + 5-11% white overlay
  → NO shadows (invisible on dark)

ELSE IF theme = atmospheric (storm/night)
  → Use colored glow effects
  → box-shadow with theme accent color

Color Adjustment Strategy

IF switching light → dark:
  IF color lightness > 70%
    → Increase saturation 10-20%
    → Reduce lightness to 40-60%
  
  IF color is brand primary
    → Use 400-level instead of 600-level
    → Test against dark background
  
  IF color is gray/neutral
    → Invert but avoid pure white/black
    → Use #f1f5f9 instead of #ffffff

ELSE IF switching dark → light:
  → Reverse above rules
  → Test readability on white background

Failure Modes

1. Pure Black Syndrome

Symptoms: Background is #000000, text is #ffffff, harsh contrast Detection: Check if background HSL lightness = 0% Fix: Replace with near-black (#0c1222, #121212) and off-white (#f1f5f9)

2. Shadow Invisibility

Symptoms: Cards have no elevation in dark mode, UI feels flat Detection: box-shadow values unchanged between themes Fix: Replace shadows with lighter surface colors in dark mode

/* Wrong */
.card { box-shadow: 0 4px 8px rgba(0,0,0,0.1); }

/* Right */
:root.theme-dark .card { 
  background: var(--surface-elevated); 
  box-shadow: none; 
}

3. Color Inversion Laziness

Symptoms: Colors look washed out or invisible in dark mode Detection: Same hex values used in both themes Fix: Manually adjust each color for its new background context

4. Flash of Wrong Theme (FOWT)

Symptoms: Page loads light, then flashes to dark after 100-200ms Detection: Theme change visible during page load Fix: Inline blocking script in <head> before any CSS:

<script>
(function(){
  if(localStorage.theme==='dark')
    document.documentElement.classList.add('theme-dark');
})();
</script>

5. System Preference Ignorance

Symptoms: App forces one theme regardless of user's OS setting Detection: No prefers-color-scheme media queries Fix: Default to system preference, allow manual override

Worked Examples

Example 1: Weather App Dashboard Theming

Scenario: Building a weather app that shows current conditions with background that matches the weather and time of day.

User Context:

Time: 8:30 PM (night)
Weather: Clear skies
Device: iPhone with OLED screen
User preference: System (dark mode enabled)

Decision Process:

Time-based atmosphere: 8:30 PM → Night theme (deep blues, bioluminescent accents)
Weather modifier: Clear skies → No storm effects, use starry gradient
Device optimization: OLED → Prioritize true blacks for battery savings
System preference: Dark mode → Confirm night theme choice

Implementation:

/* Night + Clear Weather */
:root.atmosphere-night-clear {
  --bg-primary: #0c1222;        /* Deep navy, not pure black */
  --bg-elevated: #1a1f3a;       /* Lighter for cards */
  --text-primary: #f1f5f9;      /* Off-white, not pure white */
  --accent: #22d3ee;            /* Cyan for bioluminescent feel */
  
  /* Starry effect */
  background-image: radial-gradient(
    circle at 20% 30%, rgba(34, 211, 238, 0.1) 0%, transparent 50%
  );
}

What novice would miss:

Using pure black (#000) causing OLED smearing
Same accent color as light mode becoming invisible
No elevation strategy for dark cards

Expert catches:

Near-black with blue tint maintains atmosphere
Brighter cyan accent maintains visibility
Lighter surfaces create elevation without shadows

Example 2: Dashboard with Accessibility Conflict

Scenario: Enterprise dashboard needs to support users with astigmatism (prefer light mode) and users with light sensitivity (prefer dark mode).

Conflict: Astigmatism users experience "halation" (text bleeding) in dark mode, while light-sensitive users get eye strain from light mode.

Decision Process:

Detect accessibility preferences: Check for prefers-reduced-contrast and user-set preferences
Compromise solution: Medium contrast theme that works for both groups
Escape hatches: Explicit high-contrast and extra-dark options

Implementation:

/* Medium contrast theme */
:root.theme-accessible {
  --bg-primary: #1e293b;        /* Not too dark */
  --bg-elevated: #334155;       /* Clear hierarchy */
  --text-primary: #e2e8f0;      /* Not pure white */
  --contrast-ratio: 12:1;       /* Between 7:1 and 21:1 */
}

/* High contrast escape hatch */
:root.theme-high-contrast {
  --bg-primary: #000000;
  --text-primary: #ffffff;
  --contrast-ratio: 21:1;
}

Expert considerations:

Provides theme options rather than forcing one choice
Tests contrast ratios programmatically
Offers escape hatches for extreme preferences

Example 3: OLED Battery Optimization Conflict

Scenario: Mobile news app user reports poor battery life, but switching to dark mode makes article text harder to read.

Analysis:

User is outdoors frequently (bright environment)
OLED phone at 80%+ brightness most of the time
Dark mode would save 35% battery but reduces readability

Decision Process:

Environment detection: Use ambient light sensor if available
Adaptive brightness: Auto-adjust contrast based on screen brightness
Smart defaults: Dark mode when brightness >70% AND environment is controlled

Implementation:

/* Brightness-adaptive contrast */
:root.brightness-high {
  /* Higher contrast for outdoor reading */
  --text-primary: #000000;      /* Pure black for maximum contrast */
  --bg-primary: #ffffff;        /* Pure white background */
}

:root.brightness-low {
  /* Lower contrast for indoor comfort */
  --text-primary: #f1f5f9;
  --bg-primary: #0c1222;
}

What novice would miss:

Assuming dark mode is always better for OLED
Not considering reading environment
Fixed contrast ratios regardless of brightness

Expert solution:

Context-aware theming based on device state
Battery vs. readability trade-offs clearly communicated
User education about when each mode works best

Quality Gates

[ ] Primary text contrast ≥7:1 in both themes (AAA compliance)
[ ] Interactive elements contrast ≥4.5:1 (AA compliance)
[ ] Focus indicators clearly visible in both themes
[ ] Elevation hierarchy works without shadows in dark mode
[ ] No pure black (#000000) or pure white (#ffffff) backgrounds
[ ] Color adjustments made for each theme (not simple inversion)
[ ] System preference respected on first load (prefers-color-scheme)
[ ] No flash of wrong theme during page load
[ ] Theme preference persists across sessions
[ ] OLED-optimized colors when device supports it

NOT-FOR Boundaries

This skill handles dark mode implementation. For other needs:

Color palette creation → Use color-theory-palette-harmony-expert instead
Typography in themes → Use typography-expert for font selection and sizing
Component library structure → Use design-system-creator for broader architecture
Specific contrast auditing → Use color-contrast-auditor for testing color pairs
Brand identity decisions → Use web-design-expert for overall visual direction
Animation/interaction → Use frontend-expert for theme transition animations

Delegate when you see:

Requests to create entirely new color palettes from scratch
Questions about font pairing or typography hierarchy
Component architecture decisions beyond theming
Specific WCAG audit requirements for compliance documentation
Brand strategy or identity design questions

Related Skills

curiositech/revisiting-interview-data-analysing-turn

data-ai

VerifiedTrustedCommunity

license: Apache-2.0 NOT for unrelated tasks outside this domain.

8SKILL.mdUpdated Jul 19, 2026

curiositech/revisiting-interview-data-analysing-turn

curiositech/redis-patterns-expert

development

VerifiedTrustedCommunity

Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.

8SKILL.mdUpdated Jul 19, 2026

curiositech/redis-patterns-expert

curiositech/react-server-components-boundary

tools

VerifiedTrustedCommunity

Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.

8SKILL.mdUpdated Jul 19, 2026

curiositech/react-server-components-boundary

curiositech/rate-limiting-strategy

development

VerifiedTrustedCommunity

Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.

8SKILL.mdUpdated Jul 19, 2026

curiositech/rate-limiting-strategy

Download

For Claude Desktop. Download once, then upload the file in the app — no terminal needed.

Need help? View full Cowork setup guide →

Install manually

Choose your platform

# Clone the repo
git clone https://github.com/curiositech/windags-skills.git

# Copy into Claude Code skills folder (global)
cp -r windags-skills/skills/dark-mode-design-expert ~/.claude/skills/

Claude Code Skills — official skills path docs.

Repository

curiositech/windags-skills

Compatible with

Claude Code

OpenAI Codex CLI

ChatGPT