Storybook

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

[Storybook @storybookjs]

Storybook 10.4 is here!

🤖 Automated setup
✦ Change detection
🤝 Quick sharing
🌴 TanStack React framework
💯 Improvements and bug fixes

[Storybook @storybookjs]

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

[Storybook @storybookjs]

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 👇

[Storybook @storybookjs]

Read it here 👉 https://t.co/EiZsuF7ZH8

[Daniel Williams @Danny_H_W]

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

[Storybook @storybookjs]

🎟️ Register to join live and receive the recording:

https://t.co/oDTGXLikqo

[Storybook @storybookjs]

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. 👇

[Yogi Seezatnap @seezatnap]

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.

[Storybook @storybookjs]

@caseycollins yessir!

then use Storybook's MCP to feed that context to your agents » SB Test for the self-healing loop

[Chromatic @chromaticcom]

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 👇

[parker landon @LordPrkr]

@storybookjs + @ApiMocking gives me fully interactive app in Storybook and MCP for my agents

[Storybook @storybookjs]

Join for live Q&A and get the recording: https://t.co/w1r9GmF0EL

[Storybook @storybookjs]

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 👇

[Storybook @storybookjs]

🎟️ Register to join live and receive the recording: https://t.co/w1r9GmF0EL

[Storybook @storybookjs]

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 👇

[Julien Huang @JulienHuang_dev]

Hey people 👋
What do you think of possibly having @storybookjs as a vite plugin ?
You'd get Storybook under a specific (configurable) path in dev mode within a single Vite Server alongside your application (and a single process)

[Storybook @storybookjs]

And a big thanks to @TkDodo, @beaussan, and the rest of the @tan_stack team for their kind assistance in building this out.

[Storybook @storybookjs]

Upgrade your `@storybook/react-vite` Storybook project today:

> npx storybook@latest automigrate

Or start a new Storybook in your TanStack app:

> npm create storybook@latest

The full post has more details.

https://t.co/GAB0wjQNfc

[Storybook @storybookjs]

TanStack Start’s `createServerFn` is amazing. In Storybook, it’s automatically stubbed, so you can spy on it and provide your own mock implementation.

Start’s internal functions are redirected to browser-safe mocks, too.

[Storybook @storybookjs]

Did you know Storybook has @tan_stack React support built-in?

🛣 Automatic Router wrapping with memory history
🧭 Type-safe route, params, query, and path configuration
🌲 Code-based, file-based, and nested Route support
🧪 Auto-mocked Start server functions
⚙️ Zero-config setup

[Storybook @storybookjs]

All stories automatically run inside a <RouteProvider>, so your components are properly isolated.

Provide a Route and configuration details like params, path, and query are typechecked.