Industry standard frontend workshop. Develop, test, and document components with ease. Open-source & maintained by @chromaticcom

npx storybook@latest init
Joined May 2017
Storybook 10.4 is here! 🤖 Automated setup ✦ Change detection 🤝 Quick sharing 🌴 TanStack React framework 💯 Improvements and bug fixes
1
27
2
232
22,044
How are agents really doing on your frontend? 🤖 Are they saving you work or shipping a button that’s 2px off? Tell us in the State of AI in Frontend Delivery 2026 survey. It takes 5 minutes and 5 people get a $75 Amazon gift card as a thank you. 🙏 Survey in comments 👇
1
1
8
976
Your Storybook notes just got Enriched ✨ In the next @storybookjs React Native release, the Notes addon renders Markdown natively with react-native-enriched-markdown. Same notes parameter, nothing to rewrite. Highlighted code, callouts, tables, task lists, text selection, and much more. Huge thanks to @Danny_H_W for reviewing and merging the PR 🙌
2
9
51
2,131
IBM Carbon, Adobe Spectrum, GitHub Primer, and thousands of others have documented their design systems with Storybook for years. We have learned what leads design systems to succeed or fail, so we put what we know into one guide 👇
1
1
13
1,296
The guide covers: 📌 What belongs in the docs 🚲 Practices that keep them accurate 🧰 Which tool owns which layer 🤖 Documenting for agents
1
299
Edge states are where UX bugs hide, yet they're the hardest to reach in E2E tests, and unit tests don't run in real UI. Component testing reaches every UX state in a real UI, fast. That’s why it’s been Storybook’s focus for years. We've put what we know into one full guide 👇
1
10
1
41
3,457
The guide covers: 📘 What component testing is and where it fits in a testing stack 🧪 Common techniques and the tools that match each ⚡ What a component test looks like 🤖 What changes when agents write UI
6
526
Storybook retweeted
Experimenting with a new e2e testing solution 🔹@vitest_dev runner 🔹Detox like api for selectors 🔹@agent_device ios/android driver 🔹Screenshot testing built in 🔹No custom build needed
8
10
4
106
20,156
You finally got the agent to use your components, but then it just stopped working. The new Oversight addon can alert you to issues that break the pipeline between components and agents. Join us for a chat with Rachel Cantor, the addon creator, + Q&A. Register in comments. 👇
1
4
1,039
Storybook retweeted
i do highly recommend scaffolding up an asset lib (or anything else) with @storybookjs; claude was able to inspect the outputs very granularly to improve the families autonomously, then build up from there. sort of crazy to watch.
1
1
1
608
Storybook retweeted
Our upcoming public API lets agents test their own frontend work, diagnose what failed, and fix it in the same loop. Join Jarel Fryer and Varun Vachhar for a live preview and our roadmap for agents. Register in comments 👇
1
1
3
526
Storybook retweeted
Replying to @storybookjs
@storybookjs + @ApiMocking gives me fully interactive app in Storybook and MCP for my agents
1
4
716
If you’ve ever spent longer reviewing an agent’s PR than writing the code yourself, then you know the bottleneck has moved. Tomorrow, Storybook maintainers walk thru: → Claude Code + Codex plugins connected to Storybook → Agents flaggin what to check Register in comments 👇
2
7
1,326
The frontend bottleneck is no longer code generation. It's now reviewing the output of an agent. Storybook's building two key fixes: ✅ Claude Code + Codex plugins ✅ Agentic review to surface key changes Join Storybook team for a live walkthrough + Q&A. Register in comments 👇
2
3
21
1,601