Skill
RefineUI agent skill — routes AI assistants to official docs, DESIGN.md, llm.txt, and design rules without duplicating content.
The refineui skill teaches AI agents how to work in RefineUI projects: classify requests, read the live doc index, follow token and composition rules, and optionally use @refineui/mcp.
SKILL.md
Section titled “SKILL.md”SKILL.md is the skill entry point. Agents read it first on any RefineUI-related task. It does not list components or tokens — it defines how to route to official docs and what constraints apply when writing code.
Frontmatter
Section titled “Frontmatter”---name: refineuidescription: RefineUI design-system guide for AI agents…user-invocable: trueargument-hint: "[question or topic]"---| Field | Purpose |
|---|---|
name | Skill identifier (refineui) |
description | When hosts should load this skill |
user-invocable | Users can invoke it directly (e.g. /refineui) |
argument-hint | Optional topic passed with the invocation |
Sections
Section titled “Sections”| Section | What it tells the agent |
|---|---|
| 1. Classify the request | Foundations vs components vs setup vs MCP vs health check — and whether to read the project first |
| 2. Documentation routing | Start from DESIGN.md / llm.txt / llms.txt, open leaf pages on ui.pelagornis.com; use MCP when available |
| 3. Code-writing contract | @refineui/react imports, composable APIs, tokens-only styling, a11y |
| 4. Monorepo contributors | Paths inside this repository (packages/tokens, packages/react, docs) |
| 5. MCP | When and how to use @refineui/mcp tools |
| 6. Doctor | Read-only diagnostics before suggesting fixes |
| 7. Response principles | Cite URLs, separate guidance from edits, no invented APIs |
Deeper detail lives in references/ and rules/ — SKILL.md links to them instead of duplicating content.
Source: skills/refineui/SKILL.md
What it does
Section titled “What it does”| Layer | Role |
|---|---|
| Doc routing | Start from DESIGN.md / llm.txt / llms.txt, open leaf pages on ui.pelagornis.com |
| Codegen rules | Tokens-only styling, composable APIs, no invented props |
| Monorepo hints | Where tokens, components, and docs live in this repository |
| MCP pointer | When to use @refineui/mcp tools |
| Doctor | Read-only setup & contract diagnostics |
The skill does not embed component lists or token tables — those stay in official docs so they never go stale.
Installation
Section titled “Installation”npx skills add https://github.com/pelagornis/refineui --skill refineuiyarn dlx skills add https://github.com/pelagornis/refineui --skill refineuipnpm dlx skills add https://github.com/pelagornis/refineui --skill refineuibun x skills add https://github.com/pelagornis/refineui --skill refineuiFile structure
Section titled “File structure”skills/refineui/├── SKILL.md # Entry — request classification & doc routing├── references/│ ├── design-rules.md # Points to canonical DESIGN.md│ ├── doctor.md # Doctor workflow & report schema│ └── mcp.md # @refineui/mcp setup & tools└── rules/ # Doctor rule definitions (read-only diagnostics) ├── package-setup.md ├── stylesheet-setup.md ├── foundation-contract.md ├── composition-api.md └── component-imports.md| File | When the agent reads it |
|---|---|
SKILL.md | Any RefineUI-related question — routes to docs or references |
references/design-rules.md | Writing or reviewing UI code → opens DESIGN.md |
references/doctor.md | Health check / “using RefineUI correctly?” requests |
references/mcp.md | MCP host setup or tool selection |
rules/*.md | Doctor diagnostics (manual or with refineui-doctor CLI) |
Documentation routing
Section titled “Documentation routing”Agents should fetch the index on each task, not rely on memorized slugs:
- Read
https://ui.pelagornis.com/DESIGN.mdfor visual identity - Read
https://ui.pelagornis.com/llms.txtorhttps://ui.pelagornis.com/llm.txt - Follow links to Foundations, Components, or Development leaf pages
- For code generation, combine component docs with Installation and Theming
If MCP is configured, prefer search_docs, get_doc_page, and get_design_rules from @refineui/mcp.
Request classification
Section titled “Request classification”| Request | Action |
|---|---|
| Token / color / spacing meaning | Foundations docs only |
| Component API or example | Component doc + optional MCP get_doc_page |
| App setup / CSS import | Development docs + inspect package.json |
| “RefineUI 잘 쓰고 있나?” / setup audit | Doctor + references/doctor.md or MCP run_doctor |
| “List all components” | llm.txt or MCP list_components |
Monorepo (this repository)
Section titled “Monorepo (this repository)”In this monorepo, source lives under packages/tokens, packages/react, and docs/. Install the skill in consumer projects; here it is available at skills/refineui/ for review and skills add distribution.