When should this skill be used?

Use it when reviewing stylesheets, component styles, and responsive behavior related to removing unused CSS rules.

What kinds of styles does it work with?

Stylesheets and component styles, including responsive behavior across breakpoints.

Remove unused CSS rules

SkillDev tools

unused-css is a skill for AI agents that finds and removes unused CSS rules from stylesheets and component styles. Before proposing a fix, it checks the rendered layout across breakpoints and interaction states so that removing rules does not break responsive behavior.

Use Remove unused CSS rules in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Remove unused CSS rules and connect your AI. About a minute.

Claude ChatGPT Ahel Desktop

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Remove unused CSS rules skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.

No other account needed.

Have the stylesheets or component styles you want reviewed available in your project.

Remove unused CSS rulesStart free

What your AI can do with it

Identify unused CSS rules in stylesheets
Find unused rules in component styles
Check rendered layout across breakpoints
Verify interaction states before proposing a fix
Remove unused CSS rules safely

Getting started

Have the stylesheets or component styles you want reviewed available in your project.
Add the unused-css skill to your agent's available skills.
Ask the agent to review the styles for unused rules.
Let the agent check the rendered layout across breakpoints and interaction states before applying any fix.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/unused-css/SKILL.md and read by ahel’s review.

Most projects use only 10-25% of their CSS—removing the rest can cut bundle sizes by 75%+ and dramatically improve load times.

Quick Reference

Use PurgeCSS or UnCSS to remove unused selectors
Integrate into build pipeline (Webpack, Vite, PostCSS)
Safelist dynamic classes and framework-specific patterns
Typical reduction: 50-90% for CSS framework users

Check

Use tools like PurgeCSS, UnCSS, or Chrome DevTools Coverage to identify and remove unused CSS to reduce bundle size and improve performance.

Fix

Implement automated unused CSS removal in your build process and regularly audit CSS files to eliminate dead code and unused selectors.

Explain

Explain how unused CSS bloats bundle sizes, slows page loading, and how modern tools can safely remove unused styles without breaking functionality.

Code Review

Review stylesheets, component styles, and responsive states related to Remove unused CSS rules. 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/unused-css

Signals

GitHub stars: 74k
Forks: 7k
Last commit: Oct 2026

ahel review

K1binfo
installs-packages (in references/rule.md)

Automated review, not a security audit. Ruleset v1+k2.

Questions

When should this skill be used?: Use it when reviewing stylesheets, component styles, and responsive behavior related to removing unused CSS rules.
Does it check that removing rules is safe?: Yes. It checks the rendered layout across breakpoints and interaction states before proposing a fix.
What kinds of styles does it work with?: Stylesheets and component styles, including responsive behavior across breakpoints.

Advanced

Item type: skill
Key: unused-css
Source: github.com/thedaviddias/front-end-checklist

github.com/thedaviddias/front-end-checklist