Skip to content

Project Adoption

  1. New screens first.
  2. High-frequency controls next.
  3. Shared forms and dialogs.
  4. Data display patterns.
  5. Legacy cleanup only when a touched screen needs it.
  • Uses shared tokens for color, spacing, radius, shadow, and focus.
  • Uses @my-lab/ui components when a matching component exists.
  • Documents any new pattern before repeating it.
  • Has Storybook coverage for reusable UI.
  • Has accessibility notes for keyboard and screen-reader behavior.

Do not rewrite old UI only to match the system. Convert legacy code when the screen is actively changing or when inconsistent behavior creates product risk.