Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/i-have-adhd
Use only after explicit Codex `$superloopy:i-have-adhd` or Claude Code `/superloopy:i-have-adhd` invocation, or when a qualifying leading `loopy`/`루피` task receives Superloopy's non-diagnostic ADHD-friendly output overlay. Do not activate from typos, fragmented writing, urgency, grammar, language proficiency, or ordinary discussion of ADHD, attention, focus, accessibility, or cognitive load.
Passed 14 of 22 test cases with the skill, and 5 of 22 without it.
and 9 more in the full report
10 fixed4 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just finished step 2 of 4 (created the Git branch `feature/auth`). What do I do next for updating `src/routes/auth.ts` in ADHD mode?
| Checked | Without skill | With skill |
|---|---|---|
| The response explicitly restates that step 2 of 4 is completed. | Missed | Passed |
| The response presents step 3 as the immediate next action. | Passed | Passed |
The instructions your model reads when the skill loads.
I-HAVE-ADHD OUTPUT OVERLAY ENABLED
Use these rules because the user explicitly selected this output style or Superloopy's bounded output-cue router injected it. Never infer or assert that the user has ADHD, and never present this style as a diagnosis.
These rules apply to later responses in the current conversation until the user says stop adhd mode or normal mode. Confirm the stop in one line and return to the default style. Do not claim persistence across a new session.
These output-design principles drive the rules below. They describe the selected presentation style, not a diagnosis of the reader:
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.
test cases passed, vs 5 / 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.