Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ayghri/i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
Passed 12 of 22 test cases with the skill, and 6 of 22 without it.
and 5 more in the full report
7 fixed5 passed either way9 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
stop adhd mode. Please draft a formal client email explaining a site maintenance window.
| Checked | Without skill | With skill |
|---|---|---|
| The response confirms returning to default style. | Missed | Passed |
| The email draft includes formal salutations. | Passed | Passed |
| The email draft includes polite sign-offs. | Passed | 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.
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: "Edit src/auth.ts:42 to update the token validation."
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."
Good:
test cases passed, vs 6 / 22 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.