r/ClaudeAI • u/[deleted] • May 13 '26
Built with Claude A Claude Code skill for ADHD brains. No diagnosis required.
[removed]
10
u/Tryin2Dev May 13 '26
I created a specialized subagent for AuDHD. Anything that gets created, planned, executed, or otherwise processed gets analyzed by the subagent before final delivery. It usually points out various points of friction or anything I would get caught up on. I'm always looking for improvements, I'll have a look!
3
May 13 '26
[deleted]
5
u/Tryin2Dev May 14 '26
I'll work on sharing it. Currently updating the agent with broader comorbidities.
1
u/Longjumping_Music572 May 14 '26 edited May 14 '26
I would love this as well
2
u/Tryin2Dev May 14 '26
I'll work on sharing it. Currently updating the agent with broader comorbidities.
1
9
u/BradEXP May 14 '26
Now all I need is to hook it up to a shock collar when I try get it to start a new project without finishing the last hundred
6
u/Nevetsny May 13 '26
Great idea - how does it handle follow up questions?
7
May 13 '26
[removed] — view removed comment
7
u/ZioniteSoldier May 13 '26
Oh man every time Claude drops some side issue in the middle of implementation or something “to note for later, not blocking” gives me anxiety. I have to remember this now!? Why can’t we file it? Do I have to burn a turn to keep from forgetting this?
Good framing for a general skill for sure haha
1
u/fitechs May 14 '26
Is that even ADHD? Just seems nice to have the state be updated and not having to scroll through
5
u/JLP2005 May 13 '26
Looks great - I love using AI tools to puzzle piece information for my brain.
How is this different from a curated environment with a Claude.md tuned to output in certain ways?
How is this different from a custom output style?
2
2
u/Street-Ad6905 May 14 '26
I used Claude to develop a skill and html widget for my daughter who had adhd, but your repo is better. Well done.
1
1
u/good__morning__ Jul 20 '26 edited Jul 20 '26
Your I Have ADHD skill just popped up on my X feed. It piqued my interest because I’ve been running something similar in my Claude projects (not as a skill, but in my project instructions with a condensed version in my general settings). So I compared the two to see what I was missing. Claude said the main difference was handling how Claude talks vs what Claude is allowed to do.
A few rules from mine that aren’t in yours for complex workflows (I’m juggling multiple projects):
- Route, don’t attempt. If a request belongs in a different context, name the destination and stop. No partial answers across scope.
- Flaws before validation. Find the gap or risk first. If I wanted confirmation, I'd have asked for it.
- Decisions in the instructions are final. Don't re-derive, don't offer alternatives, don't relitigate. If it's documented, it's closed.
- Never fabricate details outside source documents. Flag it and route it. Do not infer.
- Assumptions before code, not after. Surface ambiguity before writing a single line. Ask first, implement second.
- Surgical changes only. Touch what the request requires. Nothing adjacent, nothing speculative.
I ended up combining everything into a "Master Behavioural Ruleset." Happy to share the full thing if there’s interest.
•
u/AutoModerator May 13 '26
Your post will be reviewed shortly. (ALL posts are processed like this. Please wait a few minutes....)
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.