Ui css performance
A curated collection of practical, evidence-backed skills for coding agents.
npx -y skills add zacharygcook/agent-skills --skill ui-css-performanceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Prevent unused UI source, CSS growth, Tailwind scanning waste, and frontend dependency bloat while adding or changing components and visual effects. Use for UI primitives, Tailwind configuration, CSS files, component libraries, or frontend dependency changes.
SKILL.md
2.0 KB, as published. Nobody here has run it
UI and CSS Performance
Add the smallest UI surface that solves the real task and measure the result when bundle or stylesheet size may change.
Core Rules
- Prefer an existing component or simple local markup before adding a new reusable primitive.
- Add only component-library primitives that product code actually imports.
- Delete dormant components, providers, hooks, forms, and wrappers; source scanners may include them even when the JavaScript bundle does not.
- Declare every directly imported package and remove packages whose final consumer disappears.
- Keep utility-class names as static strings or finite maps of complete strings. Avoid dynamically assembled class fragments that scanners cannot discover reliably.
- Do not broaden content globs, enable plugins, or import global styles without measuring their effect.
- Keep admin/editor CSS out of public routes unless those routes need it.
New Primitive Checklist
- Confirm no existing primitive already fits.
- Add only the primitive and direct dependencies it needs.
- Import it from real application code in the same change.
- Run the repository's UI lint, unused-code/dependency scan, typecheck, and build.
- If it remains unused, remove it instead of suppressing the check.
Measure
Use repository-native build and bundle tooling. Compare the relevant route chunks and emitted CSS before and after when the change adds a library, plugin, global stylesheet, animation system, icon set, or broad content glob. Record units and whether sizes are raw, minified, or compressed.
If exact bundle tooling is unavailable, report that limitation and use bounded evidence such as emitted asset sizes and import reachability. Do not claim a performance win without measurement.