The Claude Code ADHD Skills I Actually Run (Install in 2 Minutes) Developer Chudi Nnorukam released a public MIT-licensed repository, github.com/ChudiNnorukam/claude-code-adhd-skills, containing two Claude Code skills—mirror and librarian—that he runs daily to address specific executive-function gaps in session review and codebase navigation. The skills install in about two minutes via a git clone and copy into ~/.claude/skills/, and are distinct from two unrelated projects also named 'ADHD' (i-have-adhd by Ayoub G. and adhd by UditAkhourii). The Claude Code ADHD Skills I Actually Run Install in 2 Minutes Two Claude Code skills for ADHD developers, copied unedited from the skills directory I run daily, in a public MIT repo. The install command, which skill does what, and how they differ from the two other skills called ADHD. Why this matters The repo is github.com/ChudiNnorukam/claude-code-adhd-skills. It holds two skills, mirror and librarian, copied unedited from the skills directory I run every day, under MIT. Clone it, copy the two folders into ~/.claude/skills/, restart Claude Code, type /mirror. Neither is the i-have-adhd formatting skill or the adhd divergent-reasoning skill, which are two unrelated projects that share the name. If you searched for a Claude ADHD skill and want a file on disk in the next ten minutes, this page is the file. The repository is public, MIT licensed, has no installer and no dependencies, and the two SKILL.md files in it are byte-for-byte copies of the ones in my own ~/.claude/skills/ directory. Nothing in it is a demo written for a blog post. The two-minute install Claude Code loads any directory under ~/.claude/skills/ that contains a SKILL.md . So the install is a clone and a copy. git clone https://github.com/ChudiNnorukam/claude-code-adhd-skills.git mkdir -p ~/.claude/skills cp -r claude-code-adhd-skills/mirror claude-code-adhd-skills/librarian ~/.claude/skills/ Restart Claude Code, then type: /mirror Repository: github.com/ChudiNnorukam/claude-code-adhd-skills https://github.com/ChudiNnorukam/claude-code-adhd-skills To install for one project only, copy the two folders into that repo’s .claude/skills/ instead of your home directory. Claude Code reads both locations. I send a short note when a skill in the set is renamed, retired, or added. It is a plain newsletter /newsletter , and nothing on this page depends on it. Which ADHD skill is which Three unrelated things are currently called “the Claude ADHD skill”, and nothing on the search results page tells them apart. The AI Overview describes one of them, the second organic result is a different one, and the searcher can end up installing a skill that does something other than what they were told. i-have-adhd | adhd | This repo | | |---|---|---|---| | Author | Ayoub G. | UditAkhourii | Chudi Nnorukam | | What it changes | The output format | The reasoning process | Session review and codebase navigation | | Relation to the condition | Built for readers with ADHD | A metaphor for divergent thinking | Built for a specific executive-function gap each | | Published benchmark | None | Six problems, self-judged | None. First-hand daily use instead. | | Runs on | Every reply | Open design problems | End of session; abstract requests in a codebase | i-have-adhd is ten writing rules: lead with the next action, number the steps, suppress tangents, restate state, make wins visible, cap lists at five, no preamble. It changes where the answer sits in the reply and nothing else. If Claude’s answer being in paragraph four is the same to you as the answer not being there, that skill fixes it in one step. It publishes no benchmark and does not need one, because you can feel a formatting rule working inside a day. adhd replaces a single chain of reasoning with five independent branches under different frames, scores the ideas, discards the ones it flags as traps, and develops the survivors. The name is a metaphor. It has nothing to do with the condition and does not claim to. Its published benchmark shows large gains on breadth, novelty and trap detection, which are close to asking whether the method ran, and a gain of under one point out of ten on builder usefulness. It lost the one problem that already had a known answer, a retry and timeout strategy, because a wider search walked it away from the standard solution. Use it on open problems. Do not use it on problems with a known answer. This repo is neither. It is two skills that each patch one named executive-function deficit, described below, and it exists because those two gaps cost me more than output formatting ever did. To check which one you already have, run /plugin in Claude Code and read the names. Shorter replies that open with the next step mean the formatting skill. Long option lists with a section headed traps mean the reasoning skill. A three-line readback that starts with Hearing: means you have librarian from this repo. mirror: the counter to discounting the positive The gap it patches: the cognitive distortion of discounting the positive. “Discounting the positive” is a cognitive-behavioural-therapy term for deleting your own wins from the ledger. You shipped three features and your brain renders only the bug. ADHD bundles this so reliably that it feels like realism. It is a measurement error, and it starves a reward system that is already under-fuelled. mirror pulls the actual record before it says anything: the git log since the session started, the diff of uncommitted work, the decisions made in the conversation, the dead ends ruled out. Then it reflects that back, specific and unembellished. Not “you did great”. “You shipped three commits, fixed the auth redirect, and ruled out the caching theory. That is the bug closed.” It names invisible work explicitly, because an hour spent understanding a race condition is the reason the fix took ten minutes. When it fires. “I got nothing done.” “Today was a waste.” “I am so behind.” “Was this session even worth it?” Any end-of-session reflection where the tone is self-erasing. It stays quiet when you want a genuine critique of the work, and it does not pathologise a good mood. What it refuses to do. Flatter, argue with the feeling, invent accomplishments, or turn into a pep talk. If little genuinely got done, it says so and locates the cause accurately, which is usually the plan and not the person. Try it now, at the end of a session: I feel like I got nothing done today. How did it actually go? librarian: the map you do not have to hold The gap it patches: working-memory overload from navigating a codebase. Working in a large codebase means holding a map of it in your head: where things live, what calls what, which file owns which concern. ADHD working memory does not hold that map, so every navigation is a fresh expensive search, and the expense becomes a reason to avoid unfamiliar parts of the code. librarian holds the map instead. You describe the goal in your own words, “why is startup slow”, and it walks the project’s knowledge graph, checks each node it touches for drift against the current code, and answers in exactly three lines: Hearing: