Scanning latent classes

Understand how Master CSS finds possible class names in source files and turns visible usage into generated CSS.

Keep complete classes in source

Static scanning reads source text; it does not run your application. When a component selects a status color, put each complete class in the source:

const className = error ? 'bg-red-60' : 'bg-green-60'

Avoid assembling the utility from separate bg- and color fragments. The complete-class contract explains why the scanner cannot infer that result.

Find why a style is missing

1. Inspect the complete class against the active project manifest with the class inspection tool.
2. Confirm the source file is part of the scan. Ordinary app files use integration or CLI defaults; add @source only for an explicit exception.
3. Check candidate policy when an otherwise valid class is absent. @source not can exclude a file, and @blocklist can remove a class. Use @safelist for a bounded set of known external classes.
4. For a changing value, keep the class static and pass a CSS variable. For class names created only at runtime, review rendering modes.

See Extraction for source boundaries and validation, and runtime values for a complete example.

Look up a rule

• Overview

• Source boundaries

• Candidate scanning

• Validation

• Complete classes

• Runtime values

• Included and excluded classes

• Checklist

• Markdown and MDX display boundaries

• Scanner source lifecycle