Storybook and Chromatic
Generate executable component catalogs from versioned visual scenario contracts, reuse selected dependency catalogs, and publish only approved synthetic or sanitized captures.
Install and configure
bun add -D @lssm-tech/integration.storybook \ @storybook/react-vite @storybook/nextjs-vite \ @storybook/addon-a11y @storybook/addon-vitest contractspec create visual-scenario contractspec validate contractspec build --target storybook contractspec build --target storybook --check
Contract-owned stories
Presentation references and case keys keep story IDs stable.
JSON args stay reviewable; named bindings handle icons, callbacks, providers, and composite JSX.
Generated CSF is committed and CI rejects drift from its source contracts.
Foundational package catalogs
The ContractSpec monorepo explicitly composes design-catalog, design-system, ui-kit-web, and CommunicationOS. Design-catalog owns the neutral 480-case web matrix, while design-system owns its real surface fixtures, ThemeSpec providers, semantic styling, and local fonts.
catalogs: [ designCatalogStorybookCatalog, designSystemStorybookCatalog, uiKitWebStorybookCatalog, communicationOsStorybookCatalog, ]
Visual qualification
A successful static build is not sufficient. Browser checks verify that Tailwind utilities, semantic tokens, fonts, theme modes, providers, responsive layouts, and accessibility rules are active. Browser-default controls or one placeholder reused across multiple surfaces fail the release gate.
Governed Chromatic capture
Chromatic is optional. A published snapshot must declare synthetic or sanitized data and explicitly set external capture permission. KeepCHROMATIC_PROJECT_TOKENin CI secrets; never commit it to a visual scenario or Storybook config.