Agent Skills
One command gives your AI assistant full knowledge of BoardUI: every component and template, the design rules, theming, patterns, and motion. Claude Code, Codex, and other skill-capable agents load it automatically and build with real BoardUI components instead of inventing lookalikes.
Skills follow the open SKILL.md standard: markdown your agent discovers on its own, no server needed. Content is fetched fresh from boardui.com on every install.
Install
One command, run from your project root. Pick the tab for where it should live: the default writes to .claude/skills/boarduiin the project, so the skill rides your repo and your whole team's agents pick it up. Global and the agents directory cover user-wide installs and clients like Codex or Gemini.
npx boardui@latest skillAlready connected to the BoardUI MCP server? Just ask your agent to run install_skill, no terminal needed.
What's inside
A lean SKILL.md the agent always loads, plus reference files it reads on demand (progressive disclosure, per the skills standard):
SKILL.md
The core file your agent always loads: the build workflow (detect setup, discover, install, compose, verify), a digest of the design rules, guidance on choosing the right component for the job, known gotchas, and how Pro licensing works.
references/components.md
The full catalog, generated from the live registry: every component and template with description, install command, and a usage example.
references/theming.md
Token architecture, the semantic color families, the composite type scale, dark mode mechanics, and how to rebrand the accent ramp.
references/patterns.md
Page anatomy recipes: dashboard, table page, auth, AI chat, and settings, each as an annotated skeleton with real imports.
references/motion.md
The hand-tuned micro-animation language: the duration scale, signature easings, the blur-in entrance, press feedback, springs.
Where it goes per client
Claude Code discovers skills in the project's .claude/skills/ (the default install) and in ~/.claude/skills/ (--global). Codex, Gemini CLI, and other clients that share the agents convention read ~/.agents/skills/ (--client codex). Anything else: --path puts the folder wherever your client looks. Skills load when a session starts, so restart your agent or open a fresh chat after installing.
Updating
The skill carries a version stamp in its frontmatter, and the registry rebuilds it on every deploy: new components appear in the catalog automatically. Re-run the install with --force to update in place; the command prints installed and fetched versions so you can see what changed.
npx boardui@latest skill --forceSkill vs MCP
They complement each other. The skill is knowledge the agent always has: the catalog, the rules, the patterns, loaded every session with zero setup. The MCP server is live tooling: full component source on demand, installs without a terminal, project init, and Pro license activation in chat. Best setup: install both. The skill makes the agent plan with real BoardUI components; MCP lets it execute.
BoardUI Pro
The skill's catalog covers Pro components and templates too, marked PRO, with public usage examples but never source. With a Pro license activated once (npx boardui@latest login <key>, key in your Lemon Squeezy receipt), your agent installs Pro items exactly like free ones. Without one, it knows what exists and points you to pricing instead of guessing at a lookalike.