Guard · check library

Every finding needs a rule, a measurement and a stated limit.

These five definitions govern Guard Lite. They explain what the checker reads, when a finding is justified and what still requires human or browser review.

PPG-COLOR-001

Literal colour outside the declared palette

Reads: Literal hexadecimal, RGB, RGBA, HSL or HSLA values in supported colour, background, border, outline, fill and stroke declarations.
Violation: The contract contains approved colours and the normalised literal value is absent from that set.
Skipped: Values expressed through CSS variables, calculations, gradients without a supported literal or browser-derived state.
Common review: Semantic status colours, third-party widgets, illustrations and temporary campaign surfaces may have approved exceptions not present in the small contract.
Repair: Identify the semantic role first. Replace the raw value with the correct named token, then inspect the rendered element in every relevant state.

PPG-TYPE-001

Font family outside the declared type system

Reads: The first family in a literal font-family declaration.
Violation: The contract lists approved families and the declared primary family is not one of them.
Skipped: Variable references, computed inheritance, font loading status and text drawn inside images or canvas elements.
Common review: Code blocks, data tables and third-party controls may use a separately approved mono or system family.
Repair: Apply the family assigned to the text role. Keep an appropriate fallback stack and verify that the intended font actually loads.

PPG-TYPE-002

Font size outside the declared type scale

Reads: Literal pixel, rem and em values in font-size declarations.
Violation: The contract contains approved font sizes and a different literal value is declared.
Skipped: Fluid calculations, viewport units, inherited values, browser zoom and the final size after media queries are applied.
Common review: Legal notes, data visualisation labels and responsive interpolation may need documented exceptions.
Repair: Choose the intended text role before mapping to a scale value. Do not round every number mechanically without checking hierarchy and line length.

PPG-SPACE-001

Spacing value outside the declared scale

Reads: Literal pixel, rem, em and zero values in margin, padding, gap, row-gap and column-gap declarations.
Violation: The contract contains approved spacing values and one of the declared literal values is absent.
Skipped: Percentages, viewport units, calculations, layout results and spacing created by line height or content.
Common review: Optical alignment, one-pixel borders and third-party component geometry may need explicit exceptions.
Repair: Map the space to its structural role. Replace it with the corresponding token and review the surrounding rhythm at mobile and desktop widths.

PPG-RADIUS-001

Corner radius outside the declared set

Reads: Literal pixel, rem, em and zero values in supported corner-radius declarations.
Violation: The contract contains approved radii and the declared value is not present.
Skipped: Percentages, calculated values, clip paths and the final shape after dimensions are known.
Common review: Avatars, circular indicators and media masks often need a role-specific exception.
Repair: Use the radius assigned to the component type. Confirm that controls, surfaces and media do not all require the same shape.

Run the five checks Read the complete method