Part 1: Foundation 6 min read
TL;DR - Key Takeaways
  • Body-doubling, timeboxing, and environment design are evidence-based strategies for ADHD developers working with AI tools.
  • Hyperfocus can be strategically channeled into deep coding sessions when paired with external structure.
  • AI pair programming compensates for ADHD working memory limitations while amplifying creative strengths.
  • The most effective strategies work with ADHD traits rather than against them - leveraging novelty-seeking instead of fighting it.

Practical Strategies: ADHD Programmers with Claude Code

Core Principle

“ADHD brains need external structure to balance internal chaos. AI delivers this structure on demand — tailored to your form of neurodivergence.”


1. Task Decomposition (Dopamine-Friendly)

Strategy: Break tasks into “dopamine-sized” chunks

  • Prompt: “Break this task into 5-minute subtasks that each give a sense of completion”
  • Prompt: “Give me 3 immediately actionable micro-steps for [task]”
  • Prompt: “What can I do in 2 minutes right now to make progress?”

Why it works for ADHD

  • Small wins trigger dopamine reward
  • Reduces activation energy (the hardest part for ADHD is starting)
  • Each completed step provides momentum

Claude Code specific

  • Use the TodoWrite/task system to track micro-steps
  • Ask Claude to create a checklist before starting any feature
  • “Before writing code, outline the 5 smallest steps to implement this”

2. External Structure via CLAUDE.md

Strategy: Your CLAUDE.md IS your external executive function

  • Define clear rules and conventions that persist across sessions
  • Include project structure, naming conventions, testing requirements
  • Add personal workflow preferences (“always commit after each feature”, “run tests before moving on”)

Why it works for ADHD

  • Rules at the “point of performance” (Barkley’s principle)
  • Don’t have to remember conventions — they’re externalized
  • Reduces decision fatigue

Example CLAUDE.md additions for ADHD workflow

## Workflow Rules
- Always break tasks into subtasks before starting
- Commit after completing each subtask (never accumulate changes)
- Run tests after every change
- If a task takes more than 15 minutes, stop and decompose further
- Always summarize what was done and what's next after completing work

3. Hyperfocus Management

Strategy: Ride the wave, but set guardrails

  • When hyperfocus hits, USE it — but set boundaries
  • Prompt: “I’m going to focus on [task] for the next 2 hours. Keep me on track. If I ask about something unrelated, remind me to come back to [task].”
  • Use git commits as checkpoints: “Commit what we have every 20 minutes regardless of completion”

Why it works for ADHD

  • Hyperfocus is the superpower — don’t fight it
  • Guardrails prevent the dark side (ignoring everything else)
  • Regular commits = safe save points to return to

4. Context Recovery

Strategy: AI as “where was I?” assistant

  • Start each session: “Read the recent git history and tell me what I was working on and what’s next”
  • End each session: “Summarize what we accomplished and what the next 3 steps are”
  • Use memory files to persist context across sessions

Why it works for ADHD

  • Working memory deficit = constantly losing context
  • AI becomes external working memory
  • No shame in asking “what was I doing?” — the AI doesn’t judge

5. Divergent Exploration (Your Superpower)

Strategy: Lean into creative prompting

  • “What’s a completely different approach to this problem?”
  • “Show me all the edge cases I haven’t thought of”
  • “What would a solution look like if I had no constraints?”
  • “What’s the simplest possible version of this?”
  • “How would [famous framework/tool] solve this differently?”

Why it works for ADHD

  • This is the natural ADHD thinking style — divergent, exploratory
  • AI can handle the boring convergent part (implementation)
  • Your job: ask the creative questions. AI’s job: execute the answers.

6. Anti-Shiny-Object Protocol

Strategy: Recognize and redirect

  • “I’m tempted to explore [new thing]. Should I? Or should I finish [current task] first?”
  • Set a “parking lot” file for ideas that come up during focused work
  • Rule: “New ideas go in PARKING_LOT.md, not into code”

Why it works for ADHD

  • ADHD = “shiny object syndrome” — every new idea feels urgent
  • Having a place to capture ideas reduces anxiety about forgetting them
  • The parking lot can be reviewed after the current task is done

7. Body Doubling via AI

Strategy: Use Claude Code as a digital body double

  • “Describe what I should be doing right now, as if you’re sitting next to me”
  • “Watch me work through this — I’ll think out loud and you keep me on track”
  • Keep the conversation going even for small steps

Why it works for ADHD

  • Body doubling is a proven ADHD strategy
  • AI presence reduces isolation and maintains accountability
  • Verbalizing (typing) thoughts forces linearization of chaotic thinking

8. Static Typing and Compiler as Guardrails

Strategy: Use languages and tools with strong type systems

  • TypeScript over JavaScript
  • Rust, Go, C# over Python (for larger projects)
  • Enable strict mode, linters, and all possible warnings

Why it works for ADHD

  • Compiler errors = immediate feedback loop (dopamine!)
  • Type system = external memory for function signatures
  • “Lowers cognitive complexity and prevents endless error-hunting loops”
  • IntelliSense + autocomplete = never need to remember syntax

9. Pomodoro with AI Planning

Strategy: Let AI create time-block plans

  • “I have 4 hours today. Create a Pomodoro schedule for [project] with specific tasks per block”
  • “I just finished a 25-min block. What should my next block focus on?”
  • Use “time-blind-friendly” scheduling (anchored to events, not clock times)

Why it works for ADHD

  • Time blindness is a core ADHD challenge
  • External time structure compensates for internal time sense
  • 25-minute blocks match ADHD attention capacity

10. Prompt Library (Capture Your Best Prompts)

Strategy: Document prompts that worked well

  • Keep a PROMPTS.md file with your most effective prompts
  • Categorize: debugging, architecture, refactoring, learning, planning
  • Share with other ADHD developers

Why it works for ADHD

  • You’ll forget your brilliant prompts (that’s the ADHD way)
  • A library reduces the activation energy of “how do I ask this?”
  • Reviewing past prompts can spark new creative approaches

The Meta-Strategy

You are the creative director. AI is the production team.

Your ADHD brain’s job: see the big picture, find problems, generate ideas, explore alternatives, ask “what if?”

AI’s job: remember syntax, write boilerplate, maintain context, implement details, check for errors.

This is not a workaround for a disability. This is a cognitive architecture finally matched with the right tool.

One ADHD + code insight per week

Research-backed, no fluff. Join developers who think different.

No spam. Unsubscribe anytime.

Share: