Class hygiene
Webflow class naming, with a Webflow token. Review signals.
Some elements stack many classes
Section titled “Some elements stack many classes”class_hygiene.combo_complexity · Review signal (Needs review) · Severity: Set per finding
Why it matters. Heavy reliance on combo classes can make styling behavior difficult to predict and increase the risk of unintended changes.
How to fix. Review whether repeated combo stacks should become components, utilities or simpler base classes.
The page structure is nested very deeply
Section titled “The page structure is nested very deeply”class_hygiene.deep_nesting · Review signal (Needs review) · Severity: Set per finding
Why it matters. Deeply nested elements and selectors increase structural coupling, making responsive changes and component maintenance more fragile.
How to fix. Review over-nested layout structures and simplify the hierarchy where it remains semantically safe.
Some class names look generated
Section titled “Some class names look generated”class_hygiene.naming.review · Review signal (Needs review) · Severity: Set per finding
Why it matters. Inconsistent or unclear class names make styles harder to understand, reuse and change safely as the project grows.
How to fix. Review class naming and rename only after confirming the runtime evidence with a source or rendered-DOM scan.
The class naming system is uncertain
Section titled “The class naming system is uncertain”class_hygiene.system_detection · Review signal (Needs review) · Severity: Set per finding
Why it matters. An uncertain naming-system detection affects how later class-hygiene findings are interpreted and should be confirmed before cleanup decisions are made.
How to fix. Confirm whether the detected naming system is intentional and document or standardize it in the project.