Directives & settings

Candidate policy

Include known class names or reject unwanted scanning candidates.

Use @safelist to include known classes that source discovery cannot see, and @blocklist to reject unwanted candidates. Keep ordinary application classes complete and literal in source.

@safelist

@safelist adds bounded class candidates that do not exist in scanned source. Safelisted candidates follow the same matching and diagnostic policy as discovered classes; CSS value support never silently filters their declarations.

CSS
@safelist "opacity:1";@safelist "transform:translateY(-5px):hover";@safelist "bg-blue-60@dark";

@blocklist

@blocklist removes candidates that broad scanning accepted by accident. CSS @blocklist values accept exact strings and wildcard patterns with * and ?.

CSS
@blocklist "debug-*";@blocklist "example-token";

A safelist contains complete class names. Wildcard policy belongs in the blocklist. See Scanning latent classes for bounded dynamic-class examples.


© 2026 Aoyue Design LLC.MIT License
Trademark Policy