Skip to content

fix(storybook): make design-system stories authoritative #4183

Description

@jeanduplessis

Problem

Storybook renders different fonts from production, advertises unsupported light mode, audits legacy controls, omits key interaction/reduced-motion states, and contains stale token references and a parallel stickersheet system.

Remediation action

Make Storybook an accurate executable reference for DESIGN.md and authoritative web primitives.

Scope

  • apps/storybook/.storybook/preview.ts:7
  • apps/storybook/.storybook/preview.ts:22
  • apps/storybook/stories/Button.stories.tsx:2
  • apps/storybook/stories/Input.stories.tsx:19
  • apps/storybook/stories/Badge.stories.tsx:67
  • apps/storybook/stories/design-system/DriftAudit.stories.tsx:218
  • apps/storybook/stories/design-system/Stickersheet.stories.tsx:25
  • apps/storybook/public/stickersheet.html:33

Acceptance criteria

  • Storybook loads production Inter, Roboto Mono, and JetBrains Mono variables deterministically.
  • Unsupported light-mode control is removed; canvas uses canonical dark surfaces.
  • Primitive stories import authoritative ui/* components and cover variants, disabled/loading/focus, long labels, accessible icon buttons, and reduced motion.
  • Input examples associate labels correctly.
  • Retired brand values, stale guidance, and independent OKLCH/radius/shadow definitions are removed or generated from canonical tokens.
  • Visual checks can validate canvas, raised, and overlay surfaces.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Post-launchenhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions