For AI agents
Your agent picks the right component
Coding agents get motion wrong in predictable ways: WebGL on the server, loops that never stop, reduced motion ignored. Frictionborn gives your agent a skill, a catalog and measured spec sheets, so it picks the right component and uses it correctly.
Set up your agent
Four steps, about two minutes. Pick your agent:
Install the skill
The skill tells Claude Code when to use Frictionborn, which component fits, and what to check afterwards. It lands in
.claude/skills/frictionborn.npx skills add hunainx/frictionborn -a claude-codeAdd the registry to your project
In
components.json, so both the shadcn CLI and its MCP server can find the components:{ "registries": { "@frictionborn": "https://frictionborn.com/r/{name}.json" } }Connect the shadcn MCP server
The MCP server lets Claude Code browse and install registry items itself. One command writes its configuration:
npx shadcn@4.21.1 mcp init --client claudeKeep the rules in CLAUDE.md
Three lines that keep the agent honest: where the skill is, what Frictionborn is for, and the rules it must not break.
# Frictionborn Motion Before writing animation, scroll, hover or WebGL code, read the Frictionborn skill (`.claude/skills/frictionborn/SKILL.md`, or `.agents/skills/frictionborn/SKILL.md`) and the spec sheet of every item you use (`references/items/<name>.md` next to it). 1. Use Frictionborn only for marketing and landing sections: heroes, story and feature sections, galleries, logo strips. Never for dashboards, tables, forms or repeated list rows. 2. Install with `npx shadcn@4.21.1 add @frictionborn/<item>`. Never copy motion code by hand, never write your own `requestAnimationFrame` loop, never invent a prop: read the spec sheet. 3. At most one WebGL item above the fold; host design tokens only (`var(--background)`, `var(--primary)`, ...); keep `prefers-reduced-motion` working (the items do; for the items with a reveal gate the skill lists, add `<MotionReadyScript />` in the Next.js root layout `<head>`, or call `initMotionReady()` in Vite).
Install the skill
The skill tells Codex when to use Frictionborn, which component fits, and what to check afterwards. It lands in
.agents/skills/frictionborn.npx skills add hunainx/frictionborn -a codexAdd the registry to your project
In
components.json, so both the shadcn CLI and its MCP server can find the components:{ "registries": { "@frictionborn": "https://frictionborn.com/r/{name}.json" } }Connect the shadcn MCP server
The MCP server lets Codex browse and install registry items itself. One command writes its configuration:
npx shadcn@4.21.1 mcp init --client codexKeep the rules in AGENTS.md
Three lines that keep the agent honest: where the skill is, what Frictionborn is for, and the rules it must not break.
# Frictionborn Motion Before writing animation, scroll, hover or WebGL code, read the Frictionborn skill (`.claude/skills/frictionborn/SKILL.md`, or `.agents/skills/frictionborn/SKILL.md`) and the spec sheet of every item you use (`references/items/<name>.md` next to it). 1. Use Frictionborn only for marketing and landing sections: heroes, story and feature sections, galleries, logo strips. Never for dashboards, tables, forms or repeated list rows. 2. Install with `npx shadcn@4.21.1 add @frictionborn/<item>`. Never copy motion code by hand, never write your own `requestAnimationFrame` loop, never invent a prop: read the spec sheet. 3. At most one WebGL item above the fold; host design tokens only (`var(--background)`, `var(--primary)`, ...); keep `prefers-reduced-motion` working (the items do; for the items with a reveal gate the skill lists, add `<MotionReadyScript />` in the Next.js root layout `<head>`, or call `initMotionReady()` in Vite).
Install the skill
The skill tells Cursor when to use Frictionborn, which component fits, and what to check afterwards. It lands in
.agents/skills/frictionborn.npx skills add hunainx/frictionborn -a cursorAdd the registry to your project
In
components.json, so both the shadcn CLI and its MCP server can find the components:{ "registries": { "@frictionborn": "https://frictionborn.com/r/{name}.json" } }Connect the shadcn MCP server
The MCP server lets Cursor browse and install registry items itself. One command writes its configuration:
npx shadcn@4.21.1 mcp init --client cursorKeep the rules in AGENTS.md
Three lines that keep the agent honest: where the skill is, what Frictionborn is for, and the rules it must not break.
# Frictionborn Motion Before writing animation, scroll, hover or WebGL code, read the Frictionborn skill (`.claude/skills/frictionborn/SKILL.md`, or `.agents/skills/frictionborn/SKILL.md`) and the spec sheet of every item you use (`references/items/<name>.md` next to it). 1. Use Frictionborn only for marketing and landing sections: heroes, story and feature sections, galleries, logo strips. Never for dashboards, tables, forms or repeated list rows. 2. Install with `npx shadcn@4.21.1 add @frictionborn/<item>`. Never copy motion code by hand, never write your own `requestAnimationFrame` loop, never invent a prop: read the spec sheet. 3. At most one WebGL item above the fold; host design tokens only (`var(--background)`, `var(--primary)`, ...); keep `prefers-reduced-motion` working (the items do; for the items with a reveal gate the skill lists, add `<MotionReadyScript />` in the Next.js root layout `<head>`, or call `initMotionReady()` in Vite).
Install the skill
The skill tells Antigravity when to use Frictionborn, which component fits, and what to check afterwards. It lands in
.agents/skills/frictionborn.npx skills add hunainx/frictionborn -a antigravityAdd the registry to your project
In
components.json, so both the shadcn CLI and its MCP server can find the components:{ "registries": { "@frictionborn": "https://frictionborn.com/r/{name}.json" } }Connect the shadcn MCP server
The shadcn CLI has no setup command for Antigravity yet; add the server in Antigravity's MCP settings (the raw config):
{ "mcpServers": { "shadcn": { "command": "npx", "args": ["-y", "shadcn@4.21.1", "mcp"] } } }Keep the rules in AGENTS.md
Three lines that keep the agent honest: where the skill is, what Frictionborn is for, and the rules it must not break.
# Frictionborn Motion Before writing animation, scroll, hover or WebGL code, read the Frictionborn skill (`.claude/skills/frictionborn/SKILL.md`, or `.agents/skills/frictionborn/SKILL.md`) and the spec sheet of every item you use (`references/items/<name>.md` next to it). 1. Use Frictionborn only for marketing and landing sections: heroes, story and feature sections, galleries, logo strips. Never for dashboards, tables, forms or repeated list rows. 2. Install with `npx shadcn@4.21.1 add @frictionborn/<item>`. Never copy motion code by hand, never write your own `requestAnimationFrame` loop, never invent a prop: read the spec sheet. 3. At most one WebGL item above the fold; host design tokens only (`var(--background)`, `var(--primary)`, ...); keep `prefers-reduced-motion` working (the items do; for the items with a reveal gate the skill lists, add `<MotionReadyScript />` in the Next.js root layout `<head>`, or call `initMotionReady()` in Vite).
Check that it worked
Ask your agent for something Frictionborn is for, in your own words:
Give the landing page an animated hero background with a headline and one call to action. Keep it fast on phones.A well set-up agent:
- reads the skill and the spec sheet before writing code;
- installs
ambient-hero(or one background plus its own markup) withshadcn add, instead of writing its own WebGL; - adds
<MotionReadyScript />to the root layout; - keeps one WebGL item above the fold and leaves reduced motion working;
- says plainly when a request is not a job for Frictionborn (a dashboard, a form), and builds it without it.
llms.txt: the catalog for any model
The site publishes llms.txt: every component with a one-line summary, its slot, what it needs and a link to its spec sheet. Paste it into any chat, or let a tool fetch it:
curl -s https://frictionborn.com/llms.txt
Each spec sheet is also plain Markdown next to its registry file, for example /r/ambient-hero.md.
What we promise, and what we measured
Declared (meta.declared.json)
Written by us: the slot, the props and their defaults, the capability tiers (T0 to T3) and the reduced-motion mode. How the component is meant to work.
Measured (meta.json, the measured field)
Written only by the bench, against committed code: compressed size, layout shift, frames while idle, axe results and the browsers it ran in. Results from physical phones are not recorded yet.
What next
Browse the components: every page has a “Copy prompt for your AI agent” button with the right install line and the rules for that component.