Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing stylesheets, component styles, and responsive behavior related to Avoid embedded and inline CSS. Check the rendered layout across breakpoints and interaction states before proposing a fix.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-08 | ✗→✓ | ▲ Improved | -6% | 0% |
| case-01 | ✓→✓ | = Same ✓ | -7% | 0% |
| case-02 | ✓→✓ | = Same ✓ | -24% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -24% | 0% |
| case-04 | ✓→✓ | = Same ✓ | -40% | 0% |
Inline CSS cannot be cached separately, increases HTML payload, breaks separation of concerns, and is harder to maintain in large codebases.
Verify that inline CSS and embedded styles are avoided except for valid use cases like critical CSS, dynamic styles, or performance optimization.
Move inline and embedded CSS to external stylesheets, keeping only critical above-the-fold CSS inline for performance optimization.
Explain why external CSS is preferred for maintainability, caching, and separation of concerns, with exceptions for critical CSS and dynamic styles.
Review stylesheets, component styles, and responsive states related to Avoid embedded and inline CSS. Flag exact selectors, declarations, or breakpoints that violate the rule in the rendered UI.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/css/embedded-or-inline-css
Other measured skills in the registry, with their headline benchmark lift.