A rules file that teaches a coding agent to write Yumma CSS & check its classes.
View as MarkdownA coding agent writes the class names it has seen most. agents.md gives it the Yumma CSS syntax, the values that exist & the command that checks its work, in one short file it reads before it starts.
Add It to a Project
Save it as the instructions file your agent reads. Most read AGENTS.md at the project root.
curl -s https://www.yummacss.com/agents.md >> AGENTS.md
In PowerShell:
irm https://www.yummacss.com/agents.md | Add-Content AGENTS.md
>> & Add-Content append, so instructions already in the file stay.
Claude Code reads CLAUDE.md. A CLAUDE.md holding this one line brings the rules in:
@AGENTS.md
Other agents that read a file of their own name take the same pointer, or the rules saved there instead.
What It Covers
| Section | Contents |
|---|---|
| Migrating From 3.x | How to tell a 3.x project, & the codemod to run before anything else. |
| Syntax | Property & value initials joined by a colon, variants, opacity, negatives & CSS functions. |
| Values | The spacing scale, every color family & its shades, breakpoints, states & pseudo-elements. |
| Examples | Four Yumma UI components to read before building something similar: Button, Field, Tabs & Dialog. |
| Check | Run yummacss lint after editing & use its suggestion, plus the Oxlint rules where a project lints. |
The lists come from the same tables the generator reads, so the file always matches the current release.
Check the Result
The file asks the agent to run the check itself, but it is worth running in CI as well:
pnpm dlx yummacss lint
It exits with 1 when a class does not exist. @yummacss/lint covers the command & the Oxlint rules.