sage-design-review

Enforce BEM naming conventions and SCSS token usage by applying design-review criteria to code changes, checking classname structures, verifying Pine token alignment, and ensuring new components meet BLOCKER and SHOULD FIX severity guidelines.

A Sage design-system review is a quality-assurance process for SCSS, token JSON, and classname changes. You need to run it during gauntlet reviews or when adding new components and variants to sage-assets to prevent API instability and design drift.

Check Storybook story coverage by reviewing the latest Sage code changes in your PR and verifying that all new components and variants include corresponding stories that meet the established design-system guidelines.

Yes, the design review process verifies dark-mode token alignment by checking that new SCSS work aligns with Pine tokens for dark-mode shims, preserving existing helper conventions and ensuring stability across theme changes.

Automated SCSS design-token checks focus on BLOCKER and SHOULD FIX severity levels, covering token JSON, BEM naming, and Storybook coverage, but may not capture every nuanced design-context decision beyond the established framework.