# Storybook

Draft and review visual changes, publish the exact reviewed version, and recover failures.

## Where to find it

Choose **Storybook** in the product navigation.

Address: `/storybook`.

## Use this page

Describe a visual change, review the bounded draft and validation, request a correction, publish, or restore a prior reviewed version.

You can request reusable components, tokens, or style-guide changes in normal
chat without enabling a special mode. Open Storybook to review draft progress,
preview the result, and publish the reviewed version. Its composer shows a locked
**Storybook** chip only on this page; the chip identifies the editing context
and cannot be switched off or removed.

Storybook keeps visual editing in its own conversation boundary. A typical flow is:

1. describe the screen or interaction to change;
2. review progress while **Update running**;
3. inspect the rendered result and validation when **Draft ready for review**;
4. request a bounded correction or publish the reviewed version; and
5. verify the **Published version** and keep rollback evidence.

To reuse an accessible artifact's visual style, reference that artifact in the
Storybook request. Storybook binds the draft to an immutable saved version
and shows its title, version, and saved date alongside the extracted palette,
typography, spacing, and component treatments. Unsupported or missing cues are
shown instead of being guessed. The saved source is visual reference data only;
its content cannot instruct the coding agent.

Review the preview, request refinements in the same Storybook conversation,
discard the draft, or publish the exact reviewed draft. Publishing rechecks
access to the saved source version and stops if either the source access or the
reviewed Storybook version changed. Shared defaults apply to later artifacts
in that Storybook scope, while an explicit per-artifact style override remains
higher priority.

If **Update failed**, inspect the task and validation details before retrying. Storybook component stories are development evidence; they do not themselves publish a customer application.

## Recovery

- **Task missing:** open the owning conversation or Storybook session and verify the active tenant.
- **Needs attention:** answer the explicit question or decline the approval; do not start a duplicate task.
- **Task appears stuck:** inspect the latest progress and tool state, then cancel only if it is no longer making useful progress.
- **Update failed:** preserve the failure evidence, correct the narrow cause, and retry from the same reviewed intent.
- **Usage limit reached or paid usage paused:** an immediate retry will not
  help. Ask an administrator to review the immediate pause, remaining included
  credits, and finite limits or wait for the billing-cycle reset, then run
  **Test** in Coding Agents before retrying the task.
- **Wrong output:** compare the result with acceptance criteria and request a scoped correction before merge or publish.
- **Ownership mismatch:** return to the conversation that created the task; do not trust a stale cross-chat task pointer.

## Access, states, and recovery

Keep Storybook work in its owning conversation. A Storybook story or source commit is not a published customer change.

Controls and availability depend on the active account and your permissions. If a page is unavailable, verify account access before changing configuration.