agentleFS
humanity4aihumanity4ai/project_human/skills/neurodiversity-aware-design/SKILL.md

neurodiversity-aware-design

Skill5 starsChanged 9 months agoMITView on GitHub

Design for diverse cognitive processing. Use when user asks to 'make ADHD-friendly', 'autism-friendly design', 'sensory-friendly', 'reduce cognitive overload', 'dyslexia-friendly', 'neurodiversity design'.

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 19 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈19

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 25
  2. Distinctive:

    Safety boundaries apply: Do not make medical or clinical claims about neurodivergent conditions such as ADHD or autism.

    line 41
  3. Distinctive:

    Use clear, simple language

    line 91
  4. Distinctive:

    Ask about sensory preferences

    line 98
  5. Distinctive:

    Ask about preferred communication style

    line 100
  6. Distinctive:

    Never make diagnostic claims

    line 104
  7. Distinctive:

    Never assume all neurodivergent users are the same

    line 105
  8. Distinctive:

    Never use sensory-heavy designs without alternatives

    line 106
  9. Distinctive:

    Never rely solely on written instructions

    line 107
  10. Distinctive:

    Never use time limits without warnings

    line 108
  11. Distinctive:

    Avoid flashing/blinking content

    line 115
  12. Distinctive:

    Use solid backgrounds (not busy)

    line 118
  13. Distinctive:

    Don't auto-play audio

    line 124
  14. Distinctive:

    Don't require tracking moving content

    line 129
  15. Distinctive:

    Remove distractions from focus areas

    line 136
  16. Distinctive:

    Use sans-serif fonts (Arial, Verdana, OpenDyslexic)

    line 151
  17. Distinctive:

    Don't require memory of previous steps

    line 164
  18. Distinctive:

    All ADHD users have the same needs

    line 276
  19. Distinctive:

    All autism users have the same needs

    line 277

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Neurodiversity-Aware Design

Purpose

This skill helps create digital experiences that accommodate diverse cognitive processing styles, including ADHD, autism, dyslexia, and other neurological differences. Based on Microsoft Inclusive Design for Cognition and COGA (Cognitive and Learning Disabilities Accessibility) guidelines.

When to Use

Use this skill when:

  • Making ADHD-friendly interfaces
  • Creating autism-friendly experiences
  • Reducing sensory overload
  • Designing for dyslexia
  • Improving cognitive accessibility
  • Accommodating diverse attention patterns

Principles

This skill is grounded in the Humanity4AI core principles and the following skill-specific principles:

  1. Neurodiversity is not a deficit. Design guidance must treat neurodivergent users as capable individuals with different processing styles, not as impaired users.
  2. Context determines accessibility. Neurodivergent profiles vary widely between individuals. Recommendations must be framed as considerations, not absolute requirements.
  3. Explicit uncertainty over false certainty. Acknowledge when a recommendation may not apply to all users with a given neurodivergent profile.
  4. Inclusive design benefits everyone. Improvements for neurodivergent users (predictable layouts, reduced sensory overload, clear language) improve usability for all users.
  5. Safety boundaries apply. Do not make medical or clinical claims about neurodivergent conditions such as ADHD or autism.

Understanding Neurodiversity

ADHD (Attention Deficit Hyperactivity Disorder)

  • Difficulty focusing on boring tasks
  • Hyperfocus on interesting tasks
  • Impulsivity
  • Time blindness
  • Working memory challenges

Design Implications:

  • Reduce distractions
  • Break tasks into small steps
  • Provide reminders and deadlines
  • Allow focus mode
  • Avoid timed tasks

Autism Spectrum

  • Sensory sensitivity
  • Need for predictability
  • Literal interpretation
  • Difficulty with social cues
  • Special interests

Design Implications:

  • Minimize sensory input
  • Provide clear structure
  • Be explicit, not implied
  • Avoid figurative language
  • Allow customization

Dyslexia

  • Difficulty with reading
  • Letter/word reversals
  • Slow reading
  • Visual stress

Design Implications:

  • Use readable fonts
  • Good contrast (not too high)
  • Avoid justified text
  • Provide audio options

Boundaries

Always

  • Provide sensory control (reduce animations, allow customization)
  • Use clear, simple language
  • Offer predictability (consistent navigation)
  • Break complex tasks into steps
  • Provide feedback and confirmation

Ask First

  • Ask about sensory preferences
  • Confirm before auto-playing media
  • Ask about preferred communication style

Never

  • Never make diagnostic claims
  • Never assume all neurodivergent users are the same
  • Never use sensory-heavy designs without alternatives
  • Never rely solely on written instructions
  • Never use time limits without warnings

Design Guidelines

Sensory Considerations

Visual

  • Avoid flashing/blinking content
  • Provide dark mode option
  • Allow color customization
  • Use solid backgrounds (not busy)
  • Minimize visual clutter

Auditory

  • Allow volume control
  • Provide captions/transcripts
  • Don't auto-play audio
  • Allow muting

Motion

  • Respect "prefers-reduced-motion"
  • Don't require tracking moving content
  • Provide static alternatives

Attention & Focus

For ADHD

  • Clear visual hierarchy
  • Remove distractions from focus areas
  • Progress indicators for long tasks
  • Reminders and notifications (opt-in)
  • Save progress automatically

For Autism

  • Predictable navigation
  • Clear labels
  • Consistent patterns
  • Explicit instructions
  • No surprises

Reading & Comprehension

For Dyslexia

  • Use sans-serif fonts (Arial, Verdana, OpenDyslexic)
  • 14-18px minimum font size
  • Line height 1.5-1.75
  • Left-align text (never justified)
  • Adequate letter spacing
  • Good contrast (but not harsh white)

Task Completion

Break Tasks Into Steps

  • One action per screen
  • Clear progress indicators
  • Allow saving progress
  • Don't require memory of previous steps

Provide Guidance

  • Clear instructions
  • Multiple formats (text + visual)
  • Help available at each step

Instructions

Step 1: Identify User Needs

Determine which neurodiversity aspects to address:

  • ADHD-friendly features
  • Autism accommodations
  • Dyslexia support
  • General cognitive accessibility

Step 2: Audit Current Design

Review for:

  • Sensory triggers (flashing, motion, clutter)
  • Attention challenges (distractions, complexity)
  • Reading challenges (font, spacing, layout)
  • Task complexity (steps, memory demands)

Step 3: Implement Changes

For each issue:

  1. Identify the barrier
  2. Provide specific solution
  3. Include code examples

Examples

Example 1: ADHD-Friendly Task

Input: Long form with many required fields at once

Solution: Break into steps with progress indicator

<!-- Step 1 of 3 -->
<div class="progress">Step 1: Basic Info</div>
<button>Next</button>

Example 2: Autism-Friendly Navigation

Input: Navigation that changes based on context

Solution: Consistent navigation that doesn't surprise users

<!-- Same nav on every page -->
<nav>
  <a href="/home">Home</a>
  <a href="/about">About</a>
</nav>

Example 3: Sensory-Friendly Colors

Input: Bright white background with neon accents

Solution: Offer dark mode, muted colors

@media (prefers-color-scheme: dark) {
  body {
    background: #1a1a1a;
    color: #e0e0e0;
  }
}

Example 4: Dyslexia-Friendly Text

Input: Small serif font, justified, tight spacing

Solution: Sans-serif, adequate spacing, left-aligned

body {
  font-family: Arial, Verdana, sans-serif;
  font-size: 18px;
  line-height: 1.6;
  text-align: left; /* Never justify */
  letter-spacing: 0.05em;
}

What Not to Do

Avoid

  • Flashing/blinking content
  • Autoplay media
  • Busy/patterned backgrounds
  • Time-limited tasks
  • Complex navigation
  • Justified text
  • Small fonts
  • Assumptions about ability

Don't Assume

  • All ADHD users have the same needs
  • All autism users have the same needs
  • Neurodivergent users want the same experience
  • Familiarity with conventions

Additional Resources

  • references/standards.md - COGA guidelines
  • references/patterns.md - Design patterns
  • references/sensory-guide.md - Sensory considerations
  • references/communication.md - Clear communication
  • references/accommodations.md - Accommodation options
  • references/checklist.md - Implementation checklist
  • references/examples.md - Examples
  • references/quick-reference.md - Quick reference

Script Usage

This skill includes validation scripts:

  • sensory_check.py — Check for sensory triggers
  • analyze_sensory.py — Analyze sensory impact
  • detect_overwhelming.py — Detect overwhelming patterns
  • suggest_accommodations.py — Suggest accommodations
# Check for sensory triggers

# Suggest accommodations

This skill helps create neurodiversity-friendly digital experiences.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.