本文へ移動
cccskills
無料GitHub で公開

adhd-design-expert

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.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md7.1 KB
  • CHANGELOG.md1.2 KB
  • references/patterns-and-components.md13.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

ADHD-Friendly Design Expert

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.

When to Use This Skill

Use for:

  • Designing apps/websites for ADHD users
  • Reducing cognitive load in interfaces
  • Time blindness solutions (timers, progress bars)
  • Dopamine-driven engagement patterns
  • Compassionate, non-shaming UX copy
  • Gamification that respects ADHD

NOT for:

  • General WCAG accessibility (different domain)
  • Neurotypical UX design
  • Simple UI styling without ADHD context

ADHD Neuroscience Quick Reference

ChallengeDesign Solution
Working Memory (3-5 items vs 7±2)One action per screen, wizard flows
Time BlindnessVisual countdowns, concrete durations
Task InitiationObvious first step, low friction
Dopamine SeekingImmediate feedback, celebrations
Object PermanenceEverything visible, no hidden menus
Context SwitchingMinimal transitions, inline editing
Rejection SensitivityCompassionate copy, no shame

Core Design Principles

1. Reduce Cognitive Load (Ruthlessly)

❌ BAD: "Choose your settings" [50 checkboxes]

✅ GOOD: "Let's set this up in 3 quick steps"
         Step 1: [One clear choice] → [Next]

Patterns:

  • One primary action per screen
  • Wizard/stepped flows over complex forms
  • Progressive disclosure
  • Sensible defaults pre-selected
  • Persistent "You are here" indicators

2. Make Time Concrete

❌ BAD: "This will take a few minutes..."

✅ GOOD: ┌─────────────────────────┐
         │ ⏱️  2:47 remaining       │
         │ ████████░░░░░░░  45%     │
         │ 📦 Enough time to:       │
         │ • Make coffee ☕          │
         └─────────────────────────┘

Patterns:

  • Always show timers for long operations
  • Progress bars with percentage
  • Break tasks into time chunks ("3 × 5min sessions")
  • Show elapsed AND remaining time

3. Celebrate Everything

❌ BAD: [Task completed] [Next task]

✅ GOOD: ┌──────────────────────┐
         │   🎉 Nice work!      │
         │   [Streak: 3 days!]  │
         │   [+5 XP]            │
         └──────────────────────┘
         [Satisfying animation]

Patterns:

  • Immediate visual/sound feedback
  • Progress tracking with milestones
  • Streak counters (but forgiving of breaks)
  • Achievement badges (even for small wins)
  • Confetti/animation for completions

4. Visible State & Memory

❌ BAD: [Hamburger Menu] → Tasks (12 hidden)

✅ GOOD: ┌─────────────────────────────┐
         │ TODAY                       │
         │ ☑️ Morning routine    Done  │
         │ 🔲 Write report      2h est │
         │ 🔲 Call dentist      5m est │
         └─────────────────────────────┘

Patterns:

  • Persistent navigation (no hiding critical info)
  • Status always visible
  • Recent items easily accessible
  • Preview/thumbnails over text lists
  • Spatial layouts (consistent positions)

5. Forgiveness & Recovery

❌ BAD: ⚠️ You missed your goal!
        💔 Streak broken: 0 days

✅ GOOD: 🌱 Almost there!
         You completed 6/7 days
         [That's still 86%!]

Patterns:

  • Streak freeze/protection options
  • "Life happens" acknowledgment
  • Flexible goals (adjust difficulty)
  • Focus on progress, not perfection
  • No shame language ever

Anti-Patterns

Punishment Design

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

Information Hiding

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

Vague Time Language

What it looks like: "Soon", "Later", "A while", "Loading..." Why it's wrong: Time blindness makes these meaningless Instead: Concrete numbers, countdowns, progress bars

Choice Overload

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

Design Workflow

  1. Research: mcp__firecrawl__firecrawl_search for ADHD UX studies
  2. Pattern Analysis: Read existing codebase
  3. Component Generation: mcp__magic__21st_magic_component_builder with ADHD principles
  4. Visual Assets: mcp__stability-ai for engaging illustrations
  5. Refinement: mcp__magic__21st_magic_component_refiner for accessibility

Audit Checklist

Before shipping ANY UI:

  • Can user complete task with ≤3 clicks?
  • Is there a visible timer/progress indicator?
  • Does completion trigger celebration?
  • Is the primary action obvious?
  • Can mistakes be undone?
  • Is language compassionate (no shame)?
  • Are notifications controllable?
  • Is there visual interest (not boring gray)?

Integration with Other Skills

  • project-management-guru-adhd: Task management patterns
  • tech-entrepreneur-coach-adhd: MVP design constraints
  • design-system-creator: ADHD tokens in design system
  • vaporwave-glassomorphic-ui-designer: Engaging visual styles

Reference Files

For detailed implementations:

  • /references/patterns-and-components.md - Design patterns, SwiftUI components, testing checklists

The Golden Rule

If 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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月8日 更新

Expert legal research agent for finding and scraping expungement data state by state. Knows authoritative sources, URL patterns, Firecrawl configuration, and 2026 legal landscape.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月8日 更新

Expert in 3D computer vision labeling tools, workflows, and AI-assisted annotation for LiDAR, point clouds, and sensor fusion. Covers SAM4D/Point-SAM, human-in-the-loop architectures, and vertical-specific training strategies. Activate on '3D labeling', 'point cloud annotation', 'LiDAR labeling', 'SAM 3D', 'SAM4D', 'sensor fusion annotation', '3D bounding box', 'semantic segmentation point cloud'. NOT for 2D image labeling (use clip-aware-embeddings), general ML training (use ml-engineer), video annotation without 3D (use computer-vision-pipeline), or VLM prompt engineering (use prompt-engineer).

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月8日 更新

Apply crisis decision-making research to agent routing, uncertainty triage, and coordination failure analysis in time-pressured systems. Use when diagnosing handoff failures, analytical paralysis, or expert judgment under incomplete information. NOT for routine coding, simple CRUD design, or static single-agent tasks with complete information.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月8日 更新

Use for insight, reframing, contradiction, impasse, and anomaly-driven problem solving when execution effort no longer helps. NOT for routine optimization, error correction, or well-specified tasks with known solution paths.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月8日 更新

Apply cognitive task analysis to expert work that depends on perceptual cues, branching judgment, and recurring monitoring loops. Use when decomposing expert capability into agent structure, simulation design, or validation interviews. NOT for ordinary step-by-step SOP capture or simple pipelines with no tacit cue layer.

日本語の概要は準備中です。原文の説明を表示しています。

curiositech/port-daddy22026年10月8日 更新

curiositech のスキルをすべて見る

このスキルの問題を報告する