Building AI doc toolchains with Claude skills
I’ve been building out some powerful AI-assisted docs toolchain infrastructure recently. Some random observations:
Developer experience and docs
I’ve been building out some powerful AI-assisted docs toolchain infrastructure recently. Some random observations:
Gosh, I have really experienced the “November moment” (i.e., the release of GPT-5.2 and Opus 4.5 in November 2025 hugely increased AI capabilities). Just a few months ago, I was getting mediocre results with LLM-assisted docs. Now, I have skills and subagents I’ve generated in Claude Code to assist me in writing docs…and it truly feels revolutionary. I’ll write more about it later, but I want to…
Recently someone asked me to describe my lens on developer experience, and I realized I’ve never really articulated it. So here’s my attempt!
I usually keep track of accolades in a private running doc. Despite my aversion toward self-promo, some of these quotes are just too good not to share. These are the ones I re-read just to warm my heart:
I’m implementing an LLM best practice for a docs site I wrote for my client Sensible using Claude Code. Specifically, I generated an llms.txt file at the root of a docs GitHub repo that lists file directory structure and topics descriptions, to help LLMs interpret the docs site.
I just finished upgrading one of my documentation projects to Readme’s newest platform version. The upgrade was mandatory, and before I embarked on it, I had several pressing concerns1 that I’ve since cleared up through sandbox tests in advance of the migration. Since I didn’t find the answers when I was skimming Readme’s docs, I’ll note these advanced Q&As here in case they help documentarians:
Blogging isn’t my main focus – documentation, developer experience, and information architecture is. That said, I’m happy to help out my client Sensible with some blog content, since I’m extremely well positioned to do so.
Recently I experimented with prompting Claude to generate new-feature release announcements based on docs and past changelog examples.
Here’s a short video tour of how I’ve configured Claude with style guides and a knowledge base to automate some of my more formulaic developer advocate tutorials for my client Sensible. It’s quite off-the-cuff and informal, so don’t go looking for production polish in this one!
Here are the results of my experiments with prompting an AI to write reference docs for a custom extension to a rather niche, obscure scripting language (JsonLogic).