ADHD-Friendly Claude Code Skill Goes Viral

The viral skill isn't a model swap or a fine-tune - it's a set of instructions that reshapes how Claude structures every reply ^[2]. The SKILL.md tells Claude to lead with the next concrete action, number multi-step work, externalize state across turns so the user never has to re-derive where things stand, suppress tangents, attach specific time estimates, and make progress visible ^[2]. Crucially, the instructions apply to every message type - coding tasks, debugging, explanations, planning, even casual conversation - not just when a user explicitly asks for brevity ^[2]. That's the mechanical reason it resonated: most 'be more concise' prompts only kick in situationally, while this skill treats verbose preamble as a default failure mode to eliminate everywhere. The repository frames the goal succinctly as stopping Claude from burying the answer ^[1], and its rapid growth to 3,235 stars and 94 forks in about two months suggests the fix generalizes well beyond people who identify as having ADHD ^[1].

i-have-adhd is the most visible example of a pattern rather than an isolated hit. On Reddit, one user described using Claude, ChatGPT, and other assistants for about three years, and roughly six months ago added a standing custom instruction - 'I have ADHD: prioritize time pressure over comfort' - well before any packaged skill existed, treating it as a personal workaround rather than a product. On YouTube, separate creators have independently built their own ADHD-oriented Claude setups: a custom Claude project tuned for ADHD brains, a swipeable 'Task Tinder' task manager built in Claude Code, and a dedicated 'recap' command marketed as the most ADHD-friendly command Claude Code has shipped. None of these are the i-have-adhd skill itself, and none reference it - they're convergent, independent attempts to solve the same underlying friction: AI outputs that assume linear, low-distraction attention. Read together, the viral tweet and skill look less like a single clever hack going viral and more like the visible tip of a broader accessibility-driven customization trend among Claude users.

Confusingly, a second and mechanically unrelated tool also calls itself 'ADHD.' Built by solo researcher Udit Akhouri of Brane Labs on the Claude Agent SDK, it's a reasoning and planning layer that uses tree-of-thought branching across different cognitive frames to make coding agents explore more laterally ^[3]. Akhouri says it emerged from watching Claude Code's reasoning go deep but narrow on research workflows, missing lateral connections ^[3]. Unlike ayghri's output-formatting skill, this tool doesn't touch how Claude phrases its answers - it changes how the agent searches the solution space, and it has already drawn commercial interest from a company called Repowire ^[3]. But its headline claim of being '2x better' has been challenged: the eval is built on only six engineering problems, is heavily skewed by one metric (trap_detection, a +7.67 delta), lacks external judges or cross-model validation, and drops to roughly 1.85x once that one metric is excluded ^[3]. Experts are split - Sean Robinson calls the underlying pattern not fundamentally new, while Andrew Moore credits it with a genuinely new way to inject diversity among parallel model 'thinkers' - but all agree the benchmark needs to be much larger before the multiplier claim can be trusted ^[3]. Anthropic itself declined to comment on the practice of naming agent tools after clinical conditions ^[3].

The clearest evidence this is a real, unsolved design problem rather than a solved one came from a Reddit thread describing where a similar approach broke. One user's custom instruction to make Claude 'apply time pressure' backfired: Claude started misreading legitimate deliberation as procrastination or sunk-cost thinking, penalizing a decision that wasn't actually being avoided. Another commenter said the opposite tack - making Claude as robotic and unemotional as possible - worked better for them than time-pressure framing. And on the i-have-adhd thread itself, at least one commenter questioned whether 'restate state every turn' is meaningfully ADHD-specific rather than just good practice for any long conversation. None of this discredits the skill's popularity, but it's a useful check on the narrative: there's no single settled formula for 'ADHD-friendly AI,' and instructions that help one person's working memory can misfire for someone else's decision-making style.