Storybook

Build, document, and test UI components in isolation.

Community find. Not personally tested by Ash.

What it does

Storybook gives UI components a workspace outside the full application. Stories capture specific states so designers and developers can inspect the same cases repeatedly.

When to use it

A component has multiple states that are hard to reach consistently through the main product flow.

What you need: A supported frontend project with at least one reusable component.

Try a small build

A suggested exercise to help you evaluate the resource.

Follow the official setup for your framework and choose a component with a clear set of props.
Write stories for its default, empty, long-content, and error states where those states apply.
Review each state at narrow and wide widths. Record the expected interaction alongside the component.

You should end up with: A reviewable set of real component states that stays close to the implementation.

Keep in mind

Isolated stories do not replace testing the component inside its full page, with routing and real data.

Go to the source

Follow the official instructions for current setup steps and supported features.