i-have-adhd
Skill1 starsChanged 10 days agoNo licenceView on GitHub
Shapes responses for an ADHD reader. Use whenever writing a reply to this person, for any topic. Detects task mode (action requested: fix, build, run, debug, write, set up) vs talk mode (question, venting, thinking out loud) and applies the right structure — leading with the next action, numbered steps, concrete time estimates, visible progress, no filler openers/closers — for task mode, or a plain warm conversational reply for talk mode.
- Deletes or force-pushes
- Installs packages
52 other projects use a version of this, 50 of them edited.
Adopted by
Most recently taken up by
- aegntic/compound-engineeringedited, first seen Nov 8, 2026
- WhiteMuush/Your-Claude-DevOpsedited, first seen Nov 8, 2026
- rohaquinlop/dsh-setupedited, first seen Nov 8, 2026
- halilural/imprimaturedited, first seen Nov 8, 2026
- LeonardiFranco/skillsedited, first seen Nov 8, 2026
- pydantic/pydantic-aiedited, first seen Nov 7, 2026
Used with
Projects with it also use simple-english, diagram-design and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillsimple-english
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before command, every technical term defined at first use, no AI slop. Default mode is Plain. Strict mode applies full STE vocabulary compliance when the user names STE, ASD-STE100, or compliance. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, and explanations for readers outside the field. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "plain English", "layman's terms", "explain it simply", "no jargon", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. The same rules govern the reply: answer first, prose only.
Also in 5 projects that use this
- MicrosoftSkill
diagram-design
Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, pyramid/funnel, treemap and marimekko, heatmap, bar and dumbbell, waterfall, line (slopegraph, ridgeline, streamgraph, bump), Gantt and scatter charts (bubble, beeswarm, box plot), high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, service blueprint, deployment, dependency graph, UML class, story map, or database schema diagrams as HTML/SVG/PNG, with .drawio, Mermaid, and .excalidraw import, plus lifecycle phase maps, block decomposition trees, and onboarding guidance.
Also in 4 projects that use this
GoogleSkillwriting-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Also in 5 projects that use this
AWSSkillwait-what
Stop. That last message did not land: re-pitch it.
Also in 6 projects that use this
- AWSSkill
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
Also in 6 projects that use this
- GoogleSkill
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
Also in 5 projects that use this
- +3 more from google
Other versions52 projects use a version of this.
Word for word · 1
- kshyam/opencode-and-claude-skills★ 0100% same
Edited · 50
- ayghri/i-have-adhd★ 57k51% same
- pydantic/pydantic-ai★ 21k20% same
- TanStack/ai★ 3.3k55% same
- classroomio/classroomio★ 1.7k57% same
- moeru-ai/xsai★ 66752% same
- huang-sh/PiX★ 23555% same
- beefiker/superloopy★ 11249% same
- AlemTuzlak/skills★ 4556% same
- tenequm/skills★ 3952% same
- Fioooooooo/FylloCode★ 2957% same
40 more not listed
Wrote their own version · 1
- aparente/claude-skills★ 65same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- be-a-damn-humanSkill
- client-briefSkill
- decideSkill
- deck-builderSkill
- deep-research-synthesizerSkill
- devils-advocateSkill
- fact-checkerSkill
- go-deeperSkill
- grill-meSkill
- handoffSkill
- how-toSkill
- humanizerSkill
- infographic-builderSkill
- linkedin-hookSkill
- linkedin-post-reportSkill
- negotiationSkill
- personal-voiceSkill
- prompt-masterSkill
- reddit-researcherSkill
- red-penSkill
- skill-auditSkill
- write-a-skillSkill
- steSkill
- tc-social-carouselSkill
- tightenSkill
- viral-recipeSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
9 rules. 4 are common, 5 are distinctive, and 0 are very specific to this project.
4
Common
Most of the 51 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does 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.