Review Storybook

Read the catalog contract and find the requested capability in its generated index. Check the relevant feature recipe, production subject, and story before driving it. Catalog status is prior review context, not proof of the current revision. This skill consumes the maps/catalog; corrections belong to maintain-storybook or maintain-verification-skill.

Choose discriminating states for the requested change: the normal action and result, relevant failure/retry, gate/permission presentation, and mobile/theme variants where affected. Record chosen files/exports and omitted scope. For a full source review, account for every file; do not describe sampling as full render or interaction coverage.

When reviewing navigation/index changes, compare the guide and sidebar with the full ordered index generated from feature recipes' navigation metadata. Open a feature without examples and a feature whose related suite lives elsewhere; check capability order, gap messages, classifications, recipe links, and actual suite navigation. Compare built entry IDs before/after so existing links survive. Generated Overview pages do not establish new example coverage.

Use the existing Storybook commands: pnpm build-storybook, or an owned Storybook dev server on an available local port. Use the built ui/storybook-static/index.json for actual story IDs and links. Do not trust an unrelated server on the default port. Keep the process handle and stop only the server this review started, retaining useful evidence.