Skills
A usage guide your AI assistant loads once, so it stops guessing at the catalog's conventions.
A skill is a markdown file your assistant reads before it works. Ours teaches it how the catalog is organised, where files belong, how tokens and effects are wired, and which component to reach for.
Without it, an agent with MCP access still works — it just rediscovers the conventions every session, and sometimes invents its own.
Getting it
The skill ships through the MCP server. Ask once:
Call get_vuesax_skill and install it.
The tool returns the full markdown plus install instructions for Claude Code. For other editors, save the returned text to whatever file that editor reads as project instructions:
| Editor | Where it goes |
|---|---|
| Claude Code | ~/.claude/skills/vuesax/SKILL.md |
| Cursor | .cursor/rules/vuesax.mdc |
| VS Code (Copilot) | .github/copilot-instructions.md |
| Windsurf | .windsurfrules |
| Zed | .rules |
Restart the editor afterwards — instruction files are read at startup.
What it covers
- Connecting — the endpoint, the header, how to check the connection.
- The tools — when to list, when to search, when to pull source, and why listing is free but pulling is metered.
- File placement — where a component’s
vs-*.jsfile (and any sibling tag it reuses) goes, and how to register it once. - Framework wiring — that the same custom element binds to React, Svelte, Vue or vanilla, with attributes for strings and DOM properties for objects/arrays.
- Conventions — the shared
size/variant/tone/radiusprop language, the token-fallback pattern, the reduced-motion rule.
Why it changes the output
A model that has read the skill will, on its own:
- search before pulling, so it doesn’t burn quota on the wrong component;
- pull one item’s source and reuse it, instead of fetching four variants to compare;
- add
tokens.cssonce and stop re-copying it; - keep the props API intact instead of rewriting it to its own taste;
- put shared helpers in one place instead of duplicating
usePress.tsper component.
Keeping it current
The catalog grows weekly. Re-run get_vuesax_skill every so often and
overwrite the file — it is regenerated from the live catalog, so a stale copy
is the main way an agent ends up looking for a component that has since been
renamed.