What each finding means—and what it does not.

Flagged when A direct visual value resolves to exactly the same value as a declared token.

Decide Use the token unless the direct value must remain independent from theme or system changes.

Flagged when A direct color is difficult to distinguish from a declared color token under the project’s color-distance setting.

Decide Merge it into the token if the small difference carries no real semantic or accessibility role.

Flagged when Independent tokens in the same context and category resolve to one value without aliasing each other.

Decide Keep separate semantic names when their roles may diverge; otherwise alias them to one canonical token.

Flagged when A rare color sits very close to a more established color in perceptual color space.

Decide Keep both only if the subtle distinction communicates a state, layer, brand role, or accessibility requirement.

Flagged when An undeclared static color appears once and is not visually close to a declared palette token.

Decide Name its specific role or fold it into the established palette. One-off artwork and data visualization colors are often valid exceptions.

Flagged when One base color uses multiple alpha levels within a narrow visual range.

Decide Consolidate levels that do the same job; preserve levels that express distinct states or depth.

Flagged when Different CSS notations normalize to the same color.

Decide Standardize the notation when it improves search and maintenance. Keep authored formats when a tool or color space requires them.

Flagged when A rare font size sits close to an established or declared step.

Decide Align it when the text serves an existing role; keep it when the content hierarchy genuinely needs another step.

Flagged when A rare line height is close to a repeated or declared line-height value.

Decide Reuse the role’s line height unless content density, language, or typeface metrics justify the difference.

Flagged when A weight is near a common 100-step value and may not be supported as authored.

Decide Verify the loaded font’s axes. Variable fonts may make an in-between weight entirely intentional.

Flagged when A font family is used much less often than the project’s dominant stack.

Decide Keep purposeful code, data, editorial, or display faces; remove accidental local stacks.

Flagged when Several selectors produce the same text-style signature, but some use tokens while others repeat values directly.

Decide Prefer one declaration path so later typography changes do not split the roles apart.

Flagged when A rare undeclared spacing value lands near a token or frequently repeated step.

Decide Snap it to the scale unless geometry, optical alignment, or an external asset requires the offset.

Flagged when A static undeclared spacing value appears in one layout declaration.

Decide Confirm it as a local adjustment or replace it with the scale. Screen-reader-only geometry is excluded.

Flagged when Values in different units normalize to the same pixel size.

Decide Keep relative units when they must scale with text or context; otherwise use one convention.

Flagged when An arbitrary utility introduces spacing outside the named utility scale.

Decide Use the nearest named utility when the difference is incidental; retain exact values for real geometry constraints.

Flagged when A rare radius is numerically close to a declared or repeated radius.

Decide Reuse the established shape unless the component’s role needs a visibly different silhouette.

Flagged when A rare border width is near an established step.

Decide Consolidate accidental differences; preserve widths that indicate focus, selection, or hierarchy.

Flagged when A button, field, toggle, or similar control differs from the control radius used most often.

Decide Keep the distinction only when it communicates a different control family or state.

Flagged when Two shadows have nearly identical geometry and color signatures.

Decide Reuse one recipe unless the difference creates a clearly distinct elevation or focus state.

Flagged when A rare z-index is separated from the project’s other observed levels by a large gap.

Decide Name the overlay role and align it with the stacking scale; third-party widgets may need an explicit exception.

Flagged when A declaration forces precedence with !important.

Decide Confirm whether layers, specificity, or source order can express the intent. Utility and accessibility overrides can be legitimate.

Flagged when Two media-query widths sit close enough that they may describe the same transition.

Decide Merge them when the layout change is shared; keep both when distinct breakpoints prevent a real failure.

Flagged when A project with several breakpoints uses one threshold in a single rule.

Decide Confirm the unique transition or align it with the named responsive scale.

Flagged when An arbitrary responsive utility uses a width outside the named breakpoint set.

Decide Prefer a named threshold when related layout changes should stay synchronized.

Flagged when Container-query widths are within a narrow range.

Decide Merge them if the component changes in the same way; keep them when separate internal layouts truly need both.

Flagged when An undeclared visual value is used exclusively inside container-query states.

Decide Promote it when it belongs to the wider system; keep it local when the component owns the decision.

Flagged when The same selector and property receive different values in more than one named layer.

Decide Confirm which layer owns the final value and remove declarations that no longer have a distinct purpose.

Flagged when An unlayered declaration competes with a matching declaration inside a cascade layer.

Decide Keep the override only when its higher precedence is explicit and intentional.

Flagged when Several definitions share a component name or a page-local implementation overlaps a shared component role.

Decide Reuse the shared owner when the behavior is the same; preserve separate domain components when their responsibilities differ.

Flagged when A local component’s visual signature adds or removes values compared with the shared owner of that role.

Decide Bring it back to the shared component or record why this context needs a maintained variant.

Flagged when A normalized visual value is present now but absent from the pinned baseline scan.

Decide Confirm the new vocabulary as intentional or return the source to an established value.

Flagged when A finding previously verified as repaired appears again in a later scan.

Decide Restore the repair, or record that the product decision changed. Regression status is ledger evidence, not guesswork.

Flagged when Static token coverage drops by at least five percentage points from the comparison scan.

Decide Inspect the new direct values and restore token use where the bypass was not deliberate.