Maintain Storybook

Read the Storybook catalog contract, the relevant feature recipes, and DESIGN.md. The feature map is an upstream input. This skill owns stories, their fixtures/support, and maps/storybook-map/; it does not edit the feature or agent-access maps. Report upstream drift to maintain-verification-skill with source evidence.

Reconcile the requested scope

For a feature/change, follow its capability IDs to catalog entries and shared dependencies. For a full inventory, account for every configured story file, including historical examples. Start with node scripts/storybook-catalog.mjs. Record the source revision and whether the pass covers source, rendering, interactions, or visual comparisons. Inventory completeness is not behavioral coverage. Do not expand a targeted maintenance request into an all-product audit.