@addisonschultz
Account based inJapan
About this account
- Account based in
- Japan
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
web stuff | developer relations @GitBookIO | prev @framer @miroHQ
Tokyo-to, Japan
Joined September 2011
- Tweets6.4K
- Following1.6K
- Followers1.6K
- Likes21.1K
Pinned Tweet
Over the last few weeks, we rebuilt @GitBookIO's docs from scratch.
We started by digging into the data on what new and existing users were actually trying to do when they landed in our docs.
🧵
Since launch, support gets fewer "where do I find…" questions, and our AI insights show a clear shift in what people are asking about getting started.
Very happy with how it turned out!
Of course, you should check out the docs for yourself! gitbook.com/docs/
Or head to our blog for a deep dive on the tools and workflow we used to get it done: gitbook.com/blog/how-we-rebu…
Super excited for the swag we’ve been cooking up for @GitBookIO this year 👀
Come meet me and the team at one of our upcoming events and we’ll give you some!
Register at gitbook.com/events
More and more @GitBookIO teams are using our MCP to create and manage their docs — and it's exciting to hear how flexible it’s been for different use-cases.
If you haven't tried the GitBook MCP yet, I wrote a quick guide with some best practices:
gitbook.com/blog/create-docu…
Proud to have contributed to this one!
The State of AI Search for Dev Tools 2026 confirms what we're seeing at @GitBookIO : docs are becoming AI infrastructure.
AI reads them before it recommends a tool for you.
Read the full report: devtune.ai/dev-tools-state-o…
This report is much richer because of the practitioners that contributed their own observations from the field.
Thanks to the following folks for sharing your experience so generously.
@addisonschultz - @GitBookIO
@_Dapp - @clerk
@BarrieSegal - Kind Stranger
Chris Bright - @depotdev
Dan Poppy - @dbt_labs
@gandharva - @measure_sh
Holly White - @GearsetHQ
continued...
AI agents are only as good as the context you give them — that's why skill.md files are taking off right now
Auto-generating one from your docs is fast but inherits every gap. Writing by hand is precise but slow.
I wrote about how we're building @GitBookIO's skills here: gitbook.com/blog/ai-vs-human…
Added a few more locations 🗼
I've been falling down a rabbit hole of Tokyo neighborhood names — 三軒茶屋 means "three teahouses," 目黒 means "black eye."
I quickly made an app to explore Tokyo neighborhoods and their kanji to understand their meaning.
Explore for yourself: chimei.vercel.app/
We’re experimenting with better instructions for agents in your @GitBookIO docs 🤖
Now live on all sites with GitBook Assistant enabled!
I've been falling down a rabbit hole of Tokyo neighborhood names — 三軒茶屋 means "three teahouses," 目黒 means "black eye."
I quickly made an app to explore Tokyo neighborhoods and their kanji to understand their meaning.
Explore for yourself: chimei.vercel.app/
I’m seeing the same story over and over when it comes to docs: Most teams don't know what their docs are actually doing.
We just shipped AI insights at @GitBookIO: a bird's-eye view of how your users are getting answers from GitBook Assistant.
This is part of a bigger picture: docs that don't just sit there, but actively surface what needs to improve.
We're shipping more soon on closing that loop, making it easier to act on what you learn.
Check it out in our launch from last week: gitbook.com/blog/close-the-p…
You can learn more about AI insights in our docs as well: gitbook.com/docs/publishing-…
