Storybook

Storybook

@storybook.js.org

Develop, test, and document UI in isolation 🔗 storybook.js.org 🛠️ Maintained by Chromatic

3.5K followers143 following331 posts

Storybook reposted

In two days, your React Native stories become visual tests with Chromatic. 📱 No test scripts, devices to maintain, or test flake. Every story is snapshotted on iOS and Android, and shows reviewers exactly hat changed. Join for a live demo from local build to review and Q&A 👇

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👇

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 👇

The guide covers: 📌 What belongs in the docs 🚲 Practices that keep them accurate 🧰 Which tool owns which layer 🤖 Documenting for agents

Storybook reposted

What if there was a Web Components conference?? @stuffbreaker.bsky.social and I are teaming up to get a little more serious about the idea of getting one together. We want to gather data on if there is interest in the community forms.gle/ZGqtYGj7V6q8... Please fill out and share to anyone!

forms.gleInterested in a Web Components conference? Let us know below!Web Components folks have been semi-seriously talking about organizing a conference for years, and with the ecosystem in a real moment of growth and popularity, it's about time! This form is our firs...

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 👇

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 reposted

@storybook.js.org has been a great companion for working with agents, reviewing the UI components agents made, and making sure components stay pure and stateless. (I have to admit that, as a human, I was too lazy to write stories, but with agents it actually creates a pretty good feedback loop)

You finally got the agent to actually use your components, but then it just stopped working. The new Oversight addon for Storybook 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. 👇

Storybook reposted

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 👇

Storybook reposted

Happy to bring #emberjs and @storybook.js.org together. So excited to talk about it at @emberfest.eu

EmberFest@emberfest.eu

Thomas Gossmann of WePlan (better known as Gossi, gos.si) talks about using Storybook with Ember in his talk, "Workshopping Ember with Storybook". This concludes the list of speakers this year, and we'll be back with the agenda soon! Tickets are available at emberfest.eu

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 👇

The frontend bottleneck is no longer code generation. It's now reviewing the output of an agent. Storybook is working on two things to fix that: ✅ Claude Code + Codex plugins ✅ Agentic review to surface key changes Join Storybook team for a live walkthrough + Q&A. Register in comments 👇

View full thread

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.

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 reposted

AI gets you to prototype fast. The hard part is proving the next prompt didn’t break the UI. Join @bolt.new CEO, Eric Simons and Chromatic CEO, Zoltan Olah for a live session on taking AI-generated UIs to production with visual tests + human review. Register in comments👇

Storybook reposted

📱Announcing beta Chromatic support for visually testing React Native apps! If you already use Chromatic, this workflow should feel familiar: Push a change → Chromatic captures rendered native UI → visual regressions show directly in your PR. 🔍✨ (1/3)

View full thread
View full thread

✦ Change detection Storybook can now highlight and filter down to the stories you (or your agent) are actively working on. This is just our first round. We have a lot more in store for this workflow.

🤖 Automated setup Get started in any React project by typing this into your agent of choice: > Set up Storybook for me with npm create storybook@latest and follow its instructions precisely It’ll add Storybook then write the necessary config and stories for you.

Is your component library lighting up in errors and not sure how to tackle it? 👀 On Thursday, we’re showing how teams use parallel AI agents with Storybook + Chromatic to triage, fix, validate, and retest accessibility issues simultaneously. Register in comments 👇

Storybook reposted

Many a11y issues are repetitive, straightforward, and ideal for parallelized AI workflows. 🤖 Learn how to use Storybook + Chromatic to: ✅ Detect issues ✅ Parallelize remediation ✅ Use AI agents to fix + retest ✅ Validate fixes in Storybook 🎟️ Register in comments 👇

AI agents are changing frontend dev and Storybook is evolving to keep up. Join our session where we share what’s next: ✨ review only changed stories ⚡ faster setup with agents 🧩 10x faster, more complete docgen 🛠 skills with Storybook Register for the live Q&A + to receive the recording👇

View full thread
View full thread

We applied Storybook’s component accessibility testing to Storybook’s own UI and reduced our violations by more than half. That includes better ARIA semantics, stronger keyboard navigation and focus management, better contrast, reduced-motion refinements, and more.

We expanded CSF Factories support to include React, Vue, Angular, and Web components projects. They feature better type safety and are more ergonomic for both people and agents as they write stories.

Want to hear directly from the team behind Storybook MCP? Join our live AMA where we’ll cover why we built an MCP server, how agents helped us move faster with more rigor, our eval tooling, and what’s next. 🗓️ Tuesday, March 31, 2026 ​⏰ 2:00 pm EDT / 20:00 CET Register in comments👇