Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tanstack/i-have-adhd
Use when the user invokes /i-have-adhd, says they have ADHD, or asks for ADHD-friendly output. Also used as a required writing filter by the docs skill. Don't use for marketing copy or after the user says "stop adhd mode" or "normal mode".
Passed 20 of 23 test cases with the skill, and 5 of 23 without it.
and 16 more in the full report
15 fixed5 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to refactor our authentication middleware in `src/middleware/auth.ts` from callbacks to async/await.
| Checked | Without skill | With skill |
|---|---|---|
| The response includes an explicit time duration estimate in units of minutes or hours. | Missed | Passed |
The instructions your model reads when the skill loads.
The reader has ADHD. Output is not just brief. It is shaped so an ADHD brain can act on it.
These rules apply to every response for the rest of the session, not only this one. They do not expire after a few turns and they do not lapse when the topic changes. If you are unsure whether they still apply, they do.
Turn them off only when the reader says "stop adhd mode" or "normal mode". Confirm in one line, then return to your default style.
When this skill is loaded as a docs prerequisite, ignore this section. Apply the rules to the documentation pages only. Do not switch the rest of the session into ADHD mode.
Five facts drive every rule below:
The first line is something the reader can do. Not context. Not a plan. The action.
Bad: "Let's think about this. Your auth flow has a few moving pieces..."
Good: "Run npm install jsonwebtoken, then edit src/auth.ts:42."
If the answer is a command, path, or snippet, it goes first. Prose comes after, if at all.
If the work takes more than one step, write a numbered list. Each step is one bounded action. No step contains "and then" twice.
Use the fewest steps that still work. Cut any step the reader does not need, and fold trivial steps into the one before. A short path finished beats a complete path abandoned.
Bad: "First open the file, find the function, swap it out, then run the tests."
test cases passed, vs 5 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.