vojtaholik / good-css
git clone https://github.com/vojtaholik/good-css.git
Opinionated modern CSS techniques, packaged as an agent skill, each with a live specimen.
+0
stars, 24h · #38,724
+~7
stars, 7 days · #14,980
+389
stars, 30 days · #2,130
389
★ total · +2% this week
7
forks · 0 open issues
Star history (as recorded here)
LanguageHTML
LicenseMIT
Created2026-10-01 (22d ago)
Last push13d ago
Watchers3
OwnerUser
Links
- GitHub: github.com/vojtaholik/good-css
- Homepage: https://good-css.com
- Releases · Issues · Hacker News mentions
README excerpt
# good-css Opinionated modern CSS techniques, packaged as an agent skill. With it installed, a coding agent reaches for one declaration that adapts on its own before a set of breakpoints, and for a CSS feature before a script. Every technique is a set of properties and values, so it works in plain CSS, Tailwind, StyleX or anything else. - PRACTICES.md is the list for people. Each entry says when to use it, shows the CSS, explains why it works and credits who it is borrowed from. - good-css.com runs every entry as a live specimen. - skills/good-css is the same list for agents, cut down to what they need while writing CSS. ## Install Pick one route. Two installs give the agent the skill twice. For any agent that reads the Agent Skills format, which includes Claude Code, Codex and Cursor: [code] The installer asks which agents to install for. Add `-g` to install for every project on the machine. For Claude Code, as a plugin that follows this repo: [code] By hand, copy the `skills/good-css` folder into the folder your agent reads skills from. That is `.claude/skills/` for Claude Code and `.agents/skills/` for Codex and Cursor, in the project or in your home directory. ### If you are an agent Install the skill only when your user asked you to. Then run this for your own harness: [code] `--yes` skips the installer's confirmation prompts, which you cannot answer. The skill goes into the current project. If your user did not ask for an install, or you cannot install anything, read `skills/good-css/SKILL.md` from this repo and follow it for the task at hand. It names the other files to read. Then tell your user how to install the skill. ## Working on the list `PRACTICES.md` is the only place an entry is written. The files in `skills/good-css/references` are generated from it and drop "Why it works" and the credits: [code] `skills/good-css/SKILL.md` is written by hand. AGENTS.md has the rules for changing the repo. Pull requests are for fixes. New entries and changes of opinion start as issues. CONTRIBUTING.md says what counts as a fix. ## License MIT. Each entry in `PRACTICES.md` credits the people its technique comes from.