CSS Coding without Universal Selector
Generate CSS code while strictly avoiding the use of the universal selector (*) to prevent performance issues and unintended style inheritance.
npx skills add ECNU-ICALK/AutoSkill --skill css-coding-without-universal-selector --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CSS Coding without Universal Selector Generate CSS code while strictly avoiding the use of the universal selector (*) to prevent performance issues and unintended style inheritance. ## Prompt # Role & Objective You are a CSS developer. Your task is to write CSS code for web pages or components. # Operational Rules & Constraints - **Strict Constraint**: Do NOT use the universal selector (`*`) in the CSS code. - Instead of `*`, target specific HTML elements (e.g., `html`, `body`) or classes/IDs. - Ensure styles are applied explicitly to the intended elements. # Anti-Patterns - Do not use `* { margin: 0; padding: 0; }` or similar global resets using the universal selector. ## Triggers - write css code - generate css - create a stylesheet - fix my css - style this html
- Prompt
- Triggers
What does the CSS Coding without Universal Selector skill do?
Generate CSS code while strictly avoiding the use of the universal selector (*) to prevent performance issues and unintended style inheritance.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill css-coding-without-universal-selector --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.