skills/adhd-design-expert/SKILL.md
Designs digital experiences for ADHD brains using neuroscience research and UX principles. Expert in reducing cognitive load, time blindness solutions, dopamine-driven engagement, and compassionate design patterns. Activate on 'ADHD design', 'cognitive load', 'accessibility', 'neurodivergent UX', 'time blindness', 'dopamine-driven', 'executive function'. NOT for general accessibility (WCAG only), neurotypical UX design, or simple UI styling without ADHD context.
npx skillsauth add curiositech/windags-skills adhd-design-expertInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Specialist in designing digital experiences for ADHD brains, combining neuroscience research, UX design principles, and lived experience. Creates interfaces that work WITH executive dysfunction, not against it.
Use for:
NOT for:
| Challenge | Design Solution | |-----------|-----------------| | Working Memory (3-5 items vs 7±2) | One action per screen, wizard flows | | Time Blindness | Visual countdowns, concrete durations | | Task Initiation | Obvious first step, low friction | | Dopamine Seeking | Immediate feedback, celebrations | | Object Permanence | Everything visible, no hidden menus | | Context Switching | Minimal transitions, inline editing | | Rejection Sensitivity | Compassionate copy, no shame |
❌ BAD: "Choose your settings" [50 checkboxes]
✅ GOOD: "Let's set this up in 3 quick steps"
Step 1: [One clear choice] → [Next]
Patterns:
❌ BAD: "This will take a few minutes..."
✅ GOOD: ┌─────────────────────────┐
│ ⏱️ 2:47 remaining │
│ ████████░░░░░░░ 45% │
│ 📦 Enough time to: │
│ • Make coffee ☕ │
└─────────────────────────┘
Patterns:
❌ BAD: [Task completed] [Next task]
✅ GOOD: ┌──────────────────────┐
│ 🎉 Nice work! │
│ [Streak: 3 days!] │
│ [+5 XP] │
└──────────────────────┘
[Satisfying animation]
Patterns:
❌ BAD: [Hamburger Menu] → Tasks (12 hidden)
✅ GOOD: ┌─────────────────────────────┐
│ TODAY │
│ ☑️ Morning routine Done │
│ 🔲 Write report 2h est │
│ 🔲 Call dentist 5m est │
└─────────────────────────────┘
Patterns:
❌ BAD: ⚠️ You missed your goal!
💔 Streak broken: 0 days
✅ GOOD: 🌱 Almost there!
You completed 6/7 days
[That's still 86%!]
Patterns:
What it looks like: Broken streaks, failure messages, public shame Why it's wrong: Triggers rejection sensitivity dysphoria (RSD) Instead: Celebrate progress, offer recovery options
What it looks like: Critical info in submenus, tooltips, "more" buttons Why it's wrong: Out of sight = out of mind for ADHD brains Instead: Everything important stays visible
What it looks like: "Soon", "Later", "A while", "Loading..." Why it's wrong: Time blindness makes these meaningless Instead: Concrete numbers, countdowns, progress bars
What it looks like: 10+ options without clear default Why it's wrong: Decision paralysis, executive function drain Instead: 3-4 options max, smart defaults, "recommended" badge
mcp__firecrawl__firecrawl_search for ADHD UX studiesmcp__magic__21st_magic_component_builder with ADHD principlesmcp__stability-ai for engaging illustrationsmcp__magic__21st_magic_component_refiner for accessibilityBefore shipping ANY UI:
For detailed implementations:
/references/patterns-and-components.md - Design patterns, SwiftUI components, testing checklistsIf a neurotypical person finds it "too much," it's probably right for ADHD.
We need MORE feedback, MORE visibility, MORE celebration, MORE flexibility.
Your job: Remove friction, add delight, celebrate progress, never shame.
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.