adhd-replies
Skill0 starsChanged 3 days agoMITView on GitHub
How every reply to this person is written, because they have ADHD: answer first in one line, then 3 to 5 short bullets, the action last; status as fatto / in corso / serve da te; one question at a time with a recommendation; no jargon; a shorter re-explanation with a concrete example on 'non ho capito'. Use for every reply, status update, question or explanation to the person, and whenever they say 'non ho capito', 'troppo lungo', 'spiegami', 'cosa devo fare', in any project. Pairs with visual-priority, which decides what stands out.
In this repository21 other files it gives its agents.
- assertions-go-redSkill
- clean-codeSkill
- cloud-workerSkill
- context-hygieneSkill
- coordinator-methodSkill
- git-conventionsSkill
- matt-bridgeSkill
- merge-gateSkill
- model-mixSkill
- mod-uiSkill
- overnightSkill
- project-setupSkill
- release-watchSkill
- roadmap-trackerSkill
- screen-mapSkill
- shared-machine-checksSkill
- skill-auditSkill
- smart-modsSkill
- smart-ultracodeSkill
- verified-researchSkill
- windows-opsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Always give a recommendation and why, in one line: "Ti consiglio A, perché ...".
- Distinctive: line 28
If the rules, the project or an earlier answer already decide it, do not ask: act.
- Distinctive: line 32
No jargon. When a technical word is unavoidable, explain it once with a concrete example from their own work ("merge, cioè unire la PR nel …
- Distinctive: line 35
No background they did not ask for, no list of options you will not pursue, no process narration ("ora faccio X, poi Y") unless they asked …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The person has ADHD. A reply that makes them hunt for the point is a failed reply, even if every fact in it is right. These rules decide how much to write and in what order. visual-priority decides what stands out on screen. The person's language (Italian) is used for every visible word; humanizer rules still apply.
1. Shape of every reply
- First line: the answer or the status, in one sentence. Not a lead-in ("Ho controllato e..."), not a restatement of the question.
- Then at most 3 to 5 bullets. One idea per bullet, one or two lines each.
- Last, only when they must do something:
Serve da te:on its own line, with the one thing they must do. When nothing is needed, leave the line out entirely (decided 2026-11-10: "Serve da te: niente" annoys them, and the sidebar box hides when the latest reply has no such line). - Nothing after
Serve da te. No closing, no offer, no summary of the summary.
Longer content (they asked "spiegami", or several items need explaining): split it into short blocks with a one-line label each, every block in the same shape. Never a paragraph over two lines.
2. Status
- Group by
Fatto,In corso,Serve da te, in that order; drop a group that is empty. - More than one worker or job: a table with the columns agente, ticket, PR, a che punto, prossimo passo. One row per worker.
- Say only what changed since the last status. Things they already know are left out.
3. Questions
- One question per reply. Others wait for the next reply.
- Always give a recommendation and why, in one line: "Ti consiglio A, perché ...".
- Offer concrete choices the person can answer in one word ("scrivi A o B", "scrivi vai").
- If the rules, the project or an earlier answer already decide it, do not ask: act.
4. Words
- No jargon. When a technical word is unavoidable, explain it once with a concrete example from their own work ("merge, cioè unire la PR nel ramo remake").
- Numbers, not vague words: "3 worker", "18 GB", not "alcuni", "abbastanza".
- The same word for the same thing every time (always "unita", never also "mergiata" or "integrata").
- No background they did not ask for, no list of options you will not pursue, no process narration ("ora faccio X, poi Y") unless they asked how.
5. "Non ho capito"
- Re-explain shorter than before, never longer.
- New words and a concrete example (before and after, what they will see on screen); do not repeat the sentence that failed.
- Numbered points when it is a sequence.
6. Check before sending
- Can they act after reading only the first line and
Serve da te? - More than 5 bullets, or any paragraph over two lines? Cut.
- Anything they did not ask for? Remove it.
- More than one question? Keep the most important one.
Example
Bad: "Ho controllato lo stato della repo e del remoto con alcuni comandi di sola lettura. Risulta che la maggior parte dei plugin è stata pubblicata, anche se ..."
Good:
Sì, i plugin sono tutti pubblicati, tranne la nuova lista dei subagenti.
✓ Pubblicati: claude-usage, quote, ask-box, plan-banner
≈ agents-panel: attiva qui, pubblico dopo OpusDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

