styling
Skill156 starsChanged 7 months agoApache-2.0View on GitHub
Guidance for frontend styling. Use when changing Tailwind classes, CSS tokens, light or dark themes, semantic color usage, accessibility contrast, layout wrappers, or visual UI states.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- chenwei791129/agent-skillstheir own version, first seen Oct 19, 2026
- epicenter-md/epicentertheir own version, first seen Oct 8, 2026
- UI5/webcomponentstheir own version, first seen Oct 8, 2026
- EpicenterHQ/epicentertheir own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- UI5/webcomponents★ 1.8ksame name
- chenwei791129/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 9 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when changing Tailwind classes, CSS tokens, themes, layout, or visual UI states.
- Very specific: line 12
Use cn for conditional class composition.
- Distinctive: line 13
Keep layout classes close to the element that owns the layout behavior.
- Distinctive: line 14
Avoid unnecessary nested wrappers created only to attach styling.
- Very specific: line 18
Do not introduce raw Tailwind color utilities such as text-gray-*, bg-blue-*, or border-red-*.
- Very specific: line 19
Use semantic color tokens from apps/frontend/src/css/index.css, such as background, foreground, muted, muted-foreground, primary, …
- Distinctive: line 20
If a needed semantic color is missing, propose the smallest new token first.
- Distinctive: line 21
Add light and dark theme values together when adding a token.
- Distinctive: line 26
Ensure foreground/background color pairs have sufficient WCAG contrast.
- Distinctive: line 27
Check muted text, badges, destructive states, focus states, disabled states, chart labels, and hover/selected states.
- Distinctive: line 28
Keep focus indicators visible in both light and dark themes.
- Very specific: line 32
Prefer semantic elements for meaningful structure and div for layout, containment, flex/grid, spacing, overflow, or styling when no …
- Distinctive: line 33
Avoid card-inside-card and wrapper-heavy layouts.
- Very specific: line 34
Keep repeated styled concepts as named components in apps/frontend/src/components.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Styling Skill
Use this skill when changing Tailwind classes, CSS tokens, themes, layout, or visual UI states.
Class Composition
- Use
cnfor conditional class composition. - Keep layout classes close to the element that owns the layout behavior.
- Avoid unnecessary nested wrappers created only to attach styling.
Color Tokens
- Do not introduce raw Tailwind color utilities such as
text-gray-*,bg-blue-*, orborder-red-*. - Use semantic color tokens from
apps/frontend/src/css/index.css, such asbackground,foreground,muted,muted-foreground,primary,secondary,accent,destructive,border,input,card, and sidebar/chart tokens. - If a needed semantic color is missing, propose the smallest new token first.
- Add light and dark theme values together when adding a token.
- Account for both light and dark themes in every new UI state.
Accessibility
- Ensure foreground/background color pairs have sufficient WCAG contrast.
- Check muted text, badges, destructive states, focus states, disabled states, chart labels, and hover/selected states.
- Keep focus indicators visible in both light and dark themes.
Layout
- Prefer semantic elements for meaningful structure and
divfor layout, containment, flex/grid, spacing, overflow, or styling when no semantic element fits. - Avoid card-inside-card and wrapper-heavy layouts.
- Keep repeated styled concepts as named components in
apps/frontend/src/components.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.