agentleFS
KyaniteLabsKyaniteLabs/tastecheck/skills/cognitive-a11y/SKILL.md

cognitive-a11y

Skill12 starsChanged 12 days agoMITView on GitHub

Cognitive accessibility pass for ADHD, autism, dyslexia, and neurodivergent users. Use for readability, plain language, predictability, sensory load, memory burden, time pressure, forms, onboarding, dashboards, docs, and flows.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use references/profiles.md.

    line 28
  2. Very specific:

    Stop / handoff: Stop when the task context or observed friction is unknown.

    line 71

≈ “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

Cognitive Accessibility (ADHD · autism · dyslexia · neurodivergence)

a11y-pass covers mechanical WCAG defects. This pass asks whether someone can read, understand, remember, and finish without avoidable cognitive cost. Profiles are friction lenses, never diagnoses or universal rules.

Non-negotiables (help every profile)

  • Plain and structured: literal, front-loaded language; short chunks; summaries, visible steps, and progress for long work.
  • Predictable and low-memory: consistent labels/help; no surprise changes; carry forward information instead of requiring recall.
  • Calm and readable: controllable motion, no sensory overload, readable ragged-left type (about 1.5 line-height and 45–75ch), and no justified/all-caps blocks.
  • Forgiving: explain fixes, preserve work, allow pause/extension, and confirm or undo destructive actions.

Profile lenses

Use references/profiles.md. ADHD highlights distraction, progress, and save/resume; autism predictability and sensory control; dyslexia reading support and alternatives to text-only cues. Apply shared rules to every user, including kind, non-judgmental recovery.

Use this skill

Map friction before profiles

Trace one real task through interruption/error and recovery. Record observed friction and demand, a non-diagnostic profile hypothesis, repair, and task-path proof that start, correction, or resume became easier. Make purpose/next action skimmable; externalize memory/progress; preserve work/time control; offer motion, density, and reading support without changing meaning.

Reference files

  • references/profiles.md — profile-specific barriers and repairs.
  • references/patterns.md — checkable cross-cutting patterns/examples.
  • references/decision-records.md — meta-patterns + ADR rules for novel cases.

Self-check (before claiming cognitively accessible)

  • Plain, chunked, predictable, low-memory content with one clear next action?
  • Calm, controllable sensory/readability conditions and kind, recoverable errors?
  • Real path separates observed friction from hypothesis and proves start, recovery, or resume?

How to deliver

Name profiles and concrete moves. This is the cognitive layer; hand technical/WCAG defects to a11y-pass.

Provenance — principle, not property

Grounded in the W3C Cognitive and Learning Disabilities Accessibility Task Force (COGA) "Making Content Usable for People with Cognitive and Learning Disabilities" and established neurodivergent-design practice. Independent synthesis, credited — not copied.

<!-- contract:v1:start -->

Contract (generated)

Canonical detail: contract.json.

  • Route: A flow imposes avoidable memory, attention, predictability, reading, or recovery load for ADHD, autistic, dyslexic, or other neurodivergent users.; avoid: The issue is only color contrast, semantic markup, or translation expansion.
  • Exclude: Do not flatten personality or remove useful complexity without evidence. (+1 in contract.json)
  • Stop / handoff: Stop when the task context or observed friction is unknown. (+1 in contract.json); receives [improve-existing-website, form-ux, empty-states, theming] -> sends [a11y-pass, humanize-copy, tastecheck-pass]
  • Output: prioritized cognitive repair ledger preserving product voice
  • Evidence: table_with_evidence with status, reason, remediation, evidence, provenance.
<!-- contract:v1:end -->

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.