component-consistency-validation

You can validate UI-kit changes by running local scripts under libs/ui that verify TSX exports, token references, and Storybook story definitions to detect alignment drift and produce prescriptive fix commands.

UI-kit cross-consistency validation is a verification process that aligns Figma mappings, TSX component props, token CSS, and Storybook stories to ensure supported configurations match and visual consistency is maintained during handoff.

You need to run Storybook and Figma mapping validation whenever TSX components, token CSS, story definitions, or Figma artifacts have been modified to ensure cross-consistency and prevent drift before handoff.

Yes, you can use local scripts under libs/ui to verify TSX component exports and token CSS references, which produces a concise report of inconsistencies and actionable commands that maintainers can run to fix discrepancies.

The best way to prevent UI-kit drift during handoff is to validate that TSX props, variants, token CSS mappings, and Storybook stories stay aligned by running a cross-consistency check that reports actionable recommendations and fix commands.

Your Storybook story may not match TSX component variants because of uncaught drift after modifying UI-kit artifacts, which cross-consistency validation detects by checking supported configurations against story definitions and token usage.