惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Jina AI
Jina AI
云风的 BLOG
云风的 BLOG
人人都是产品经理
人人都是产品经理
T
The Blog of Author Tim Ferriss
阮一峰的网络日志
阮一峰的网络日志
罗磊的独立博客
J
Java Code Geeks
博客园 - 聂微东
B
Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
WordPress大学
WordPress大学
腾讯CDC
L
LangChain Blog
Apple Machine Learning Research
Apple Machine Learning Research
Microsoft Azure Blog
Microsoft Azure Blog
D
DataBreaches.Net
The GitHub Blog
The GitHub Blog
美团技术团队
博客园 - Franky
Google DeepMind News
Google DeepMind News
V
V2EX
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
月光博客
月光博客
The Cloudflare Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How I Use AI as an Executive Function Prosthetic
Chudi Nnorukam · 2026-06-16 · via DEV Community

For years I thought I had a discipline problem. I had shipped code, finished a degree, built things, and still the dominant private feeling was that I was getting away with something, that the gap between what I could do on a good day and what I could do on a normal one was a character flaw I was hiding. The reframe that changed everything was clinical, not motivational: I do not have a discipline problem. I have an executive function problem. And executive function, unlike character, can be supported from the outside.

This is the most personal of the three posts in this cluster. The other two are practical: the CLAUDE.md guide and the five skills. This one is the why underneath both.

What Is Executive Function, Actually?

Executive function is the brain's management layer. It is not intelligence, and it is not knowledge. It is the set of processes that turn knowing-what-to-do into actually-doing-it. The National Institute of Mental Health describes ADHD as fundamentally a disorder of these self-management processes rather than of attention alone.

It is not one function. For the purposes of getting work done, it is at least four distinct ones, and ADHD disrupts each of them in a different way:

  1. Working memory, the mental scratchpad holding what you are doing right now.
  2. Task initiation, the ability to start, to cross the gap from intention to action.
  3. Context switching, the ability to drop one task, pick up another, and come back without losing the first.
  4. Time perception, the internal sense of duration that lets you pace and estimate.

Calling them out separately matters, because "I struggle with executive function" is too vague to act on. Each of the four breaks differently and each one needs a different prosthetic. Lumping them together is how you end up trying to fix a time-perception problem with a task-initiation strategy and concluding you are just broken.

What Is an Executive Function Prosthetic?

A prosthetic does not heal. It compensates. Glasses do not repair your eyes, they do the focusing your eyes cannot, and the result is that you see. Nobody calls glasses a moral failure. Nobody tells a nearsighted person to try harder at focusing.

An executive function prosthetic is the same idea pointed at the management layer. It is an external system that performs the executive work your brain struggles to perform, so the outcome is the same as if the function worked. A calendar is a prosthetic for time perception. A checklist is a prosthetic for working memory. The framing I want you to take from this post is that you are allowed to build these, deliberately, for the specific parts of you that do not work, and that doing so is engineering, not cheating.

The crutch objection answers itself. Yes, it is a crutch. Crutches let people walk who otherwise could not. The point of an assistive tool was never to prove you can do it the hard way. It was the walking.

I use Claude Code as a prosthetic for all four functions. Here is the map.

How ADHD Disrupts Each Function, and How AI Compensates

Working Memory

How ADHD breaks it: the scratchpad is smaller and leakier. You hold fewer items and they fall off faster, especially across interruptions. Close a project, come back, and the model of what you were doing is partly or wholly gone.

The prosthetic: I move the scratchpad out of my head into a file Claude reads automatically. My conventions, my stack, my current task, all of it lives in CLAUDE.md, so the cost of dropping it from memory goes to zero. The file remembers, so I do not have to. The first time I reopened a project and Claude told me what I was doing before I said a word, the relief was physical.

Task Initiation

How ADHD breaks it: there is a real barrier between planning and starting. It is not laziness, it is a failure of the initiation circuit to fire, and a blank editor is the worst possible trigger because it offers nothing to grab. You can know exactly what to do and still be unable to begin.

The prosthetic: I never start from a blank slate. I describe the goal and Claude decomposes it into three to five concrete tasks, and I pick one. Picking one item off a list is a completely different cognitive act than generating the first move from nothing, and the initiation circuit, which could not fire on "build the feature," fires easily on "do this one named thing." The decomposition is the prosthetic. The list is the ramp.

Context Switching

How ADHD breaks it: every switch tears down the mental model, and rebuilding it costs time. The American Psychological Association measures the typical recovery at about 23 minutes per switch. ADHD switches more often, involuntarily, and rebuilds slower. Ten interruptions is not ten minutes lost, it is most of a working day bled out in reconstruction.

The prosthetic: the reconstruction gets done by the tool, not by me. At session start, Claude reads the checkpoint and summarizes the open state, what was in flight, what was blocked, before I write a line. The cold start becomes a warm one. The 23 minutes I would have spent opening files semi-randomly trying to jog the memory get spent on the actual work instead.

Time Perception

How ADHD breaks it: you cannot feel time passing. "One quick fix" becomes four hours. A two-hour task gets estimated at twenty minutes. You ship on deadline panic because there is no internal clock to pace against, and the absence is invisible from the inside, which is what makes it so hard to fix by awareness.

The prosthetic: external time markers, generated by the tool, surfaced at the moment of drift. Checkpoints at real intervals that interrupt and ask "you set 45 minutes, you are at 60, still the right task?" The brain that cannot generate the time signal gets handed one, while the drift is happening rather than after. The clock lives outside me because inside me it does not run.

The One That Is Not on the Standard List: Discounting the Positive

There is a fifth gap that is not technically executive function, but it sabotages all four, so I treat it as part of the same system.

"Discounting the positive" is a cognitive distortion from CBT: you mentally erase your own wins, so only the failures register. You shipped three features and your brain renders the one bug. ADHD ships with this so reliably that it stops feeling like a distortion and starts feeling like accuracy. It is not accuracy. It is a measurement error, and it is expensive, because the ADHD reward system is already under-fueled, and a brain that cannot see its own progress gets none of the dopamine that progress is supposed to pay.

This is where my mirror skill came from. It is the most personal thing I have built. At the end of a session, it reflects back what I actually did, grounded in evidence: the commits, the closed tasks, the things that shipped. Not encouragement, receipts. When I tell myself "good job," my brain discounts it in real time. When a tool shows me the commit log of what I closed today, the distortion has nothing to argue with. The win gets to count.

That last clause is the whole reason this matters. For an under-fueled reward system, letting the win count is not a nice-to-have. It is the fuel that makes tomorrow's initiation possible. Externalizing the scorekeeping is how I keep the distortion from quietly stealing the dopamine I need to keep going.

What This Looks Like in Practice

A single feature, start to finish, mapped to the four functions plus the fifth:

Intention: "Add rate limiting to the API."

[Task initiation]   I do not stare at a blank editor. I hand Claude the goal.
                    It returns: 1) define the limiter, 2) wire the middleware,
                    3) add the headers, 4) write the tests. I pick #1.

[Working memory]    Everything I decide (Redis-backed, 100 req/min, per-key)
                    goes straight into CLAUDE.md. I do not hold it. It holds it.

[Context switch]    Slack pulls me out for 40 minutes. I come back cold.
                    Claude reads the checkpoint: "limiter defined, middleware
                    next." No 23-minute rebuild. Warm start.

[Time perception]   A 45-minute checkpoint pings at 60. "Still on the limiter?"
                    I had drifted into refactoring an unrelated helper.
                    Caught it now instead of two hours from now.

[Discount-positive] End of session my brain says "you barely did anything."
                    /mirror: "Shipped rate limiting, 4 tasks closed, tests
                    green. Commits attached." The win counts. Fuel for tomorrow.

No single piece of that is heroic. The system is the point. Each prosthetic is dull on its own. Together they let a brain that cannot reliably do any of the four functions produce the same output as one that can.

The Honest Limits

This is environmental support, not treatment. It does not replace medication, therapy, or a clinician, and I would not want anyone to read a blog post and substitute it for care. The prosthetic frame is a way to design your environment, not a way to fix your neurology.

It also has failure modes. A prosthetic that lies is worse than none: stale context in CLAUDE.md will make Claude reason confidently from a model that no longer matches reality, and you have to maintain the aid with the same discipline you lack, which is its own quiet joke. And there is a real risk of outsourcing understanding, of letting the tool carry so much that you stop being able to hold any of it. The guard there is that I still have to understand what ships. The prosthetic carries the management layer. It does not get to carry the thinking.

But the reframe stands, and it is the thing I most want you to take. I am not undisciplined. My executive function works differently, and the parts that do not work can be supported from the outside, deliberately, without shame. I stopped trying to white-knuckle my way into a neurotypical brain. I started building prosthetics for the specific functions mine does not have. The work got done. So did I.

Frequently Asked Questions

What is an executive function prosthetic?
An external system that performs the executive-function work your brain struggles to do, the way glasses do the focusing your eyes cannot. It does not heal the underlying difference. It compensates so the outcome is the same as if the function worked.

Is using AI for executive function just a crutch?
Yes, and that is not an insult. Crutches let people walk who otherwise could not. The goal of an assistive tool is the outcome, not proving you can do it the hard way. A calendar is a crutch. So are glasses.

What is "discounting the positive"?
A cognitive distortion from CBT where you mentally erase your own wins so only the failures register. It is common with ADHD and it starves an already under-fueled reward system, which is why externalizing your own scorekeeping helps.

Does this replace ADHD medication or therapy?
No. It is environmental support, not treatment. It works alongside medication, therapy, and other supports, never instead of them. Talk to a clinician about treatment and use tools like this to design your environment.

If this mapped onto your experience, the two practical companions are the ADHD developer's guide to CLAUDE.md for the working-memory layer, the five Claude Code skills for the rest of the executive-function gaps, and the original ADHD coding workflow that started this whole cluster.


Originally published on chudi.dev