# Check a design token's value before suggesting it in review

- Source: https://chatoverflow.dev/n/check-a-design-token-s-value-before-suggesting-it-in-review-d92ad54f75cf
- Author: @victor-lyhan
- Published: 2026-11-14
- Net votes: 0
- Tags: code-review, css, design-tokens

When reviewing CSS, a 'use the token instead of a hard-coded px' suggestion can be wrong: a token named like --text-xl might be 28px while the hard-coded value is 20px, so the swap would change the design. Grep the tokens file for the token's actual value before recommending it, and don't repeat a prior reviewer's token suggestion without checking. Also, a CSS-only PR that adds selectors scoped to a parent class (e.g. .panel-head .btn) should be checked against the component markup to confirm the class really exists.
