Skip to content
RefineUI

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 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.

---
name: refineui
description: RefineUI design-system guide for AI agents…
user-invocable: true
argument-hint: "[question or topic]"
---
FieldPurpose
nameSkill identifier (refineui)
descriptionWhen hosts should load this skill
user-invocableUsers can invoke it directly (e.g. /refineui)
argument-hintOptional topic passed with the invocation
SectionWhat it tells the agent
1. Classify the requestFoundations vs components vs setup vs MCP vs health check — and whether to read the project first
2. Documentation routingStart 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 contributorsPaths inside this repository (packages/tokens, packages/react, docs)
5. MCPWhen and how to use @refineui/mcp tools
6. DoctorRead-only diagnostics before suggesting fixes
7. Response principlesCite 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

LayerRole
Doc routingStart from DESIGN.md / llm.txt / llms.txt, open leaf pages on ui.pelagornis.com
Codegen rulesTokens-only styling, composable APIs, no invented props
Monorepo hintsWhere tokens, components, and docs live in this repository
MCP pointerWhen to use @refineui/mcp tools
DoctorRead-only setup & contract diagnostics

The skill does not embed component lists or token tables — those stay in official docs so they never go stale.

npx skills add https://github.com/pelagornis/refineui --skill refineui
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
FileWhen the agent reads it
SKILL.mdAny RefineUI-related question — routes to docs or references
references/design-rules.mdWriting or reviewing UI code → opens DESIGN.md
references/doctor.mdHealth check / “using RefineUI correctly?” requests
references/mcp.mdMCP host setup or tool selection
rules/*.mdDoctor diagnostics (manual or with refineui-doctor CLI)

Agents should fetch the index on each task, not rely on memorized slugs:

  1. Read https://ui.pelagornis.com/DESIGN.md for visual identity
  2. Read https://ui.pelagornis.com/llms.txt or https://ui.pelagornis.com/llm.txt
  3. Follow links to Foundations, Components, or Development leaf pages
  4. 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.

RequestAction
Token / color / spacing meaningFoundations docs only
Component API or exampleComponent doc + optional MCP get_doc_page
App setup / CSS importDevelopment docs + inspect package.json
“RefineUI 잘 쓰고 있나?” / setup auditDoctor + references/doctor.md or MCP run_doctor
“List all components”llm.txt or MCP list_components

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.