SkillAgentSearch skills...

Design-components-for-AI-agents

Animated React, Tailwind CSS and React Native components for AI coding agents. Source code, design prompts and JSON briefs, with a shadcn registry, CLI and MCP for Claude Code, OpenAI models, Cursor and Codex.

Install / Use

claude mcp add richawo -- npx -y github:richawo/Design-components-for-AI-agents

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

83/100

Supported Platforms

Claude Code
Claude Desktop
Cursor
OpenAI Codex

Our assessment of Design-components-for-AI-agents

Design-components-for-AI-agents scores 83/100 on our quality scale, 3024th of 4,583 Development & Engineering skills we index.

Its MCP Server is 13 KB long, well organised into 17 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so Design-components-for-AI-agents is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Design-components-for-AI-agents compared with similar skills

All 4 of these similar skills score higher than Design-components-for-AI-agents; compare them before choosing.

SkillScoreStarsUpdatedFormat
Design-components-for-AI-agents (this skill)by richawo833todayMCP Server
taste-skillby Leonxlnx100101.2k2d agoCLAUDE.md
Agent-Reachby Panniantong100101.1k2d agoCLAUDE.md
headroomby headroomlabs-ai10077.6ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10063.7k2d agoCLAUDE.md

Frequently asked questions

How do I install Design-components-for-AI-agents?
Run claude mcp add richawo -- npx -y github:richawo/Design-components-for-AI-agents. The install tabs above show the steps for each supported agent.
Which AI agents does Design-components-for-AI-agents work with?
It is written for Claude Code, Claude Desktop, Cursor and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
Is Design-components-for-AI-agents safe to use?
It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is Design-components-for-AI-agents still maintained?
The repository was last updated today, so Design-components-for-AI-agents is actively maintained.
<div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset=".github/assets/wordmark-dark.png"> <img src=".github/assets/wordmark-light.png" alt="Design for AI" width="360"> </picture>

React components for AI coding agents

Bring taste to what your agent ships.

Animated React, Tailwind CSS and React Native components for Claude Code, Cursor, Codex and other AI coding agents. Every component comes with source code, a design brief and a JSON prompt.

Explore components · Documentation · Connect your agent · Design principles · Pricing

<a href="https://design.yaps.ai/components"> <picture> <source media="(prefers-reduced-motion: reduce)" srcset=".github/assets/showcase-still.png"> <img src=".github/assets/showcase.gif" alt="Design for AI component collection: an animated AI agent terminal, a portfolio chart, a Three.js particle sphere and React Native navigation" width="100%"> </picture> </a> </div>

Why Design for AI?

  • A designed starting point. Give your agent a specific component instead of asking it to invent a design system from a blank prompt.
  • Three ways to build. Install the React or React Native source, paste the design brief, or pass the JSON prompt to your agent. Each describes the same interface.
  • Motion with a purpose. Chart ranges morph, replies stream, navigation moves on springs, and loading resolves into a result. Preview the behaviour before using it.
  • Your code, your stack. Free components are MIT. Components live in your project, with typed props and explicit dependencies. Pro source is licensed separately.

See the components in motion

These are recordings of the actual components. Open any preview to try its controls, see the code or copy its brief. Readers with reduced motion enabled see still images.

<table> <tr> <td width="50%" valign="top"> <a href="https://design.yaps.ai/components/hero-terminal-agent"> <picture> <source media="(prefers-reduced-motion: reduce)" srcset=".github/assets/hero-terminal-agent.png"> <img src=".github/assets/hero-terminal-agent.gif" alt="Animated React AI agent hero with a terminal that plans work, writes files and runs tests" width="100%"> </picture> </a> <p><strong>AI agent hero</strong><br>A live terminal session, ordered reveals and a copyable install command.<br><a href="https://design.yaps.ai/components/hero-terminal-agent">Try the component</a> · Free</p> </td> <td width="50%" valign="top"> <a href="https://design.yaps.ai/components/three-globe-arcs"> <picture> <source media="(prefers-reduced-motion: reduce)" srcset=".github/assets/three-globe-arcs.png"> <img src=".github/assets/three-globe-arcs.gif" alt="Animated Three.js globe with illuminated routes and live network metrics" width="100%"> </picture> </a> <p><strong>WebGL globe</strong><br>A rotating point globe with flight arcs and a quiet, precise readout.<br><a href="https://design.yaps.ai/components/three-globe-arcs">Try the component</a> · Pro</p> </td> </tr> <tr> <td width="50%" valign="top"> <a href="https://design.yaps.ai/components/chart-portfolio"> <picture> <source media="(prefers-reduced-motion: reduce)" srcset=".github/assets/chart-portfolio.png"> <img src=".github/assets/chart-portfolio.gif" alt="Animated React portfolio chart with a crosshair, changing ranges and live price readouts" width="100%"> </picture> </a> <p><strong>Portfolio chart</strong><br>A hand-drawn SVG chart with range morphs, volume and a crosshair.<br><a href="https://design.yaps.ai/components/chart-portfolio">Try the component</a> · Free</p> </td> <td width="50%" valign="top"> <a href="https://design.yaps.ai/components/bento-grid"> <picture> <source media="(prefers-reduced-motion: reduce)" srcset=".github/assets/bento-grid.png"> <img src=".github/assets/bento-grid.gif" alt="Animated React analytics bento grid with a drawing chart, counting metrics and activity tiles" width="100%"> </picture> </a> <p><strong>Live analytics bento</strong><br>Drawing charts, counting figures and six tiles that tell one story.<br><a href="https://design.yaps.ai/components/bento-grid">Try the component</a> · Pro</p> </td> </tr> <tr> <td width="50%" valign="top"> <a href="https://design.yaps.ai/components/mobile-tab-bar"> <picture> <source media="(prefers-reduced-motion: reduce)" srcset=".github/assets/mobile-tab-bar.png"> <img src=".github/assets/mobile-tab-bar.gif" alt="Animated React Native glass tab bar with morphing icons, a spring lens and a radial action menu" width="100%"> </picture> </a> <p><strong>React Native navigation</strong><br>Glass, morphing icons and a spring-driven lens, with an arc menu.<br><a href="https://design.yaps.ai/components/mobile-tab-bar">Try the component</a> · Free</p> </td> <td width="50%" valign="top"> <a href="https://design.yaps.ai/components/three-particle-sphere"> <picture> <source media="(prefers-reduced-motion: reduce)" srcset=".github/assets/three-particle-sphere.png"> <img src=".github/assets/three-particle-sphere.gif" alt="Animated Three.js particle sphere with a breathing, flowing surface of silver points" width="100%"> </picture> </a> <p><strong>Particle sphere</strong><br>A living point cloud with depth, rhythm and a restrained silver palette.<br><a href="https://design.yaps.ai/components/three-particle-sphere">Try the component</a> · Pro</p> </td> </tr> </table>

Browse the full component library →

What you get with every component

| Format | What it contains | When to use it | | --- | --- | --- | | Source code | A self-contained .tsx file with typed props. React + Tailwind CSS, or React Native with declared dependencies. | Install it in your project and adapt it. | | Design brief | Type, spacing, colour, motion, responsive behaviour, accessibility and the choices to avoid. | Ask your agent to rebuild it in your brand or stack. | | JSON prompt | The same brief as structured data with a consistent schema. | Automate generation or change one design decision at a time. |

Explore by category

| Build | Start here | | --- | --- | | AI chat, streaming answers and agent workflows | AI interfaces · Agent components | | Landing pages and product marketing | Heroes · Features · Pricing | | Dashboards and analytics | Charts · App UI | | Generative visuals and WebGL | 3D components · Pixel components | | Mobile apps | React Native components | | Product UI and forms | Inputs · Authentication · Feedback |

Quick start

shadcn CLI

npx shadcn@latest add https://design.yaps.ai/r/chart-portfolio.json

MCP server (Claude Code, Claude, ChatGPT, Cursor, VS Code, Codex)

The site is a remote MCP server; nothing to install. Your agent signs in through the browser, so there's no key to copy:

claude mcp add --transport http design-for-ai https://design.yaps.ai/mcp/pro
# then run /mcp in Claude Code and choose Authenticate

The agents guide has one-click installs for Cursor and VS Code and steps for the Claude app, ChatGPT and Codex. Free components also work at https://design.yaps.ai/mcp with no sign-in.

Then ask: "Find a Design for AI chart component and add it to the dashboard." Prefer a local process? npx -y https://design.yaps.ai/mcp.tgz.

CLI

npx https://design.yaps.ai/cli.tgz search sign in
npx https://design.yaps.ai/cli.tgz add auth-sign-in      # writes the file, installs its dependencies
npx https://design.yaps.ai/cli.tgz prompt auth-sign-in   # the design brief, for your agent

Claude skill

Copy skills/design-for-ai into .claude/skills/ (one project) or ~/.claude/skills/ (every project). It teaches your agent when to reach for a component, how to adapt one without flattening it, and the checklist to run before it says it's done.

Paste the brief

Open any component page, hit Copy for agent, and paste it into your chat. You get the install command, the design brief and the source in one message.

For language models

Repository layout

app/                    Next.js site (App Router): gallery, docs, blog, API, SEO routes
components/site/        Site chrome, never shipped to users
registry/free/<slug>/   Free components: <slug>.tsx, meta.json, prompt.md, prompt.json (MIT)
registry/pro/           Pro components, cloned from a private repo at build time (gitignored)
registry/pro-manifest.json   Public metadata for Pro components
content/                Public documentation (Markdown)
registry/pro/_site/     Private blog source and localization dictionaries
scripts/                Registry build, screenshots, Pro sync
packages/mcp/           design-for-ai-mcp, the local (stdio) MCP server
packages/cli/           design-for-ai, the CLI
lib/mcp.ts, app/mcp/    the remote MCP server at /mcp and /mcp/pro (OAuth: lib/commerce/oauth.ts)
skills/design-for-ai/   Claude skill: find, adapt and review against the principles
docs/COMPONENT_SPEC.md  The bar every component is held to

Develop

npm install
npm run dev                                   # http://localhost:3000
node scripts/build-registry.mjs               # validate every component
node scripts/shot.mjs <slug> --base=http://localhost:3000   # screenshots at 1440/768/390

Production runs on Cloudflare Workers (design-yaps, on design.yaps.ai) via OpenNext; see docs/DEPLOY.md. npm run preview runs the built Worker locally.

The site builds without the Pro source: Pro components render as locked cards using registry/pro-manifest.json. With access to the private repo, npm run pro:sync (needs PRO_REPO_TOKEN) clones it into registry/pro/.

Site pages and live demos support the same 30 languages as Yaps. English keeps its root URLs; other editions use /{locale}. Saved dictionaries live in content/site-i18n/, with reviewed terminology in content/site-i18n-overrides.json. After changing visible copy, run npm run site:translate (resumable), npm run site:audit, then rebuild the registry. In a proxy-based environment, run the translation command with NODE_USE_ENV_PROXY=1. The audit reports missing copy and invalid placeholders, names or URLs. Missing copy falls back to English while provider limits are resolved; it does not block other verified deployments.

Preview localisation is applied by the build loader; the downloadable source stays standalone. State values

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3
CategoryDevelopment
Updated2h ago
Forks0

Languages

TypeScript

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low