Agent skill
Give your coding agent working knowledge of Appica UI.
The rules keep an agent from breaking Appica UI. The skill teaches it to use the library well: which of the 75+ components fits a request, the parts each one really exports, how to theme without forking a component, and how to check its own work.
It is an Agent Skill: a folder of instructions that your agent loads only when a task needs it, so it costs nothing in the sessions that don't. Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI and most other coding agents read the format.
Install
Run this in your project root:
The skill is named after the package it covers, @appica/ui-react. The
skills CLI finds the agents you use and puts it where each one looks
for it: .claude/skills/ for Claude Code, .agents/skills/ for Cursor, Codex, GitHub
Copilot, Gemini CLI and most others. Commit the folder, and everyone who works on the
project gets it.
What the CLI needs, and what it sends
The CLI runs on Node.js 22.20 or later. It counts installs anonymously, which is how a skill gets listed on
skills.sh. Set DISABLE_TELEMETRY=1 to opt out.
Without the CLI
A skill is just files. Copy the
skills/appica-ui-react
folder from the repository into .claude/skills/appica-ui-react for Claude Code, or
.agents/skills/appica-ui-react for the others. Keep the folder name: it has to match the
skill's name.
What's inside
The agent reads SKILL.md when the skill triggers, and opens a reference only when the
task calls for it. Component pages are not bundled: the agent fetches the 1 page it needs
as markdown, the same way it does from llms.txt.
Use it
There is nothing to call. Describe the interface you want and the agent loads the skill on its own, even when you never name Appica UI or a component:
Add a filter drawer to the products page, with a price range and a brand checklist.
To be explicit, name it: "use the appica-ui-react skill". In Claude Code you can also type
/appica-ui-react followed by the task.
With the skill loaded, an agent works in this order:
- Runs the check script, so a broken setup is fixed before it writes a component.
- Looks the component up in the catalog, where a "filter drawer" is
drawerand a "dropdown" isselect,combobox,autocompleteordropdown-menu. - Reads that component's page, or its types in
node_modules, instead of guessing props. - Writes the code, then runs the check on the files it changed and fixes what it reports.
The check script
The script is plain Node.js with no dependencies, and it never writes a file. You can run it yourself:
Setup. React 19, Tailwind CSS v4, the stylesheet import, and whether the @source path
resolves to the installed library from the stylesheet it's written in. When it doesn't, the
script prints the line to write:
Usage. In the files you name, it reports:
- An import that doesn't exist in your installed version, with the one that does:
@appica/ui-react/sheetisdrawer, andCardContentis not a part ofCard. - Hue utilities (
bg-gray-100) and color literals (bg-[#fafafa]) where a role token belongs. - A link rendered through
Button, and aclassNameon the element passed torender. - A form whose buttons can't submit it, because none has
type="submit". - With
--rtl, physical utilities such aspl-4andtext-leftthat won't mirror.
It exits with 1 when it finds an error, so it also works in CI or a pre-commit hook.
Rules or skill?
Use both. They do different jobs:
The skill carries a copy of the rules, so it works on its own. The copy that ships in your
node_modules describes the version you have installed, and the skill tells the agent to
trust that one when the 2 differ.
Keep it current
Each release of the skill describes 1 release of the library. When the 2 drift apart, the check script says so and lists the difference: the components your installed version doesn't have yet, or the ones the skill doesn't know yet. Update the skill after you upgrade Appica UI.
To remove it, run npx skills remove appica-ui-react.