| AI-native · 14 |
|---|
| Ant Design | Official and community: @ant-design/cli mcp (official antd MCP server) · @jzone-mcp/antd-components-mcp (community) (community) (opens in new tab) | Official: llms.txt / llms-full.txt / llms-semantic.md family (opens in new tab) | Official: antd skill (skills/antd/SKILL.md in ant-design-cli) · .agents/skills/ — six maintainer skills (symlinked to .claude/skills and .cursor/skills) (opens in new tab) | Official: .github/copilot-instructions.md (opens in new tab) | Official: CLAUDE.md (root, 291 lines) with AGENTS.md symlinked to it (opens in new tab) | Official: docs/react/for-agents (“For Agents”) (opens in new tab) | None found | Official: @ant-design/cli — antd setup / antd lint / antd migrate --apply (opens in new tab) | Confirmed absent: No Code Connect. The ant-design/ant-design tree at 12522b38 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Confirmed absent: No Storybook. A complete recursive listing of master (4,973 files, not truncated) holds no .storybook directory, no *.stories.* or *.story.* module, and no path containing “storybook” at all. Component demos run on dumi, Ant Group’s own React docs framework, from an in-repo .dumi/ theme. | Official: design.md (google-labs-code/design.md format) (opens in new tab) |
|---|
| Astryx | Official: Hosted MCP server at astryx.atmeta.com/mcp (opens in new tab) | Official: astryx.atmeta.com/llms.txt (opens in new tab) | None found | Official: .github/copilot-instructions.md plus four path-scoped instruction files (opens in new tab) | Official: Generated agent context (astryx init --features agents) · Root CLAUDE.md that hands maintainers the consumer CLI (opens in new tab) | Official: /docs/working-with-ai (opens in new tab) | Official: Graded template gallery as the exemplar corpus (opens in new tab) | Official: @astryxdesign/cli — the machine interface, and the source of truth (opens in new tab) | Confirmed absent: No Code Connect. The facebook/astryx tree at a03e2286 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Official: apps/storybook (opens in new tab) | Official: Public nightly vibe-test ledger · Claude Code slash commands (.claude/commands/) (opens in new tab) |
|---|
| Atlassian Design System | Official: ADS MCP server (remote, hosted) · @atlaskit/ads-mcp (local stdio) (opens in new tab) | Official: llms.txt + topic-split sets (opens in new tab) | Official: atlassian-design-system agent skill (opens in new tab) | None found | None found | None found | None found | None found | None found | Official: @atlaskit/storybook-addon-design-system (opens in new tab) | Official: DESIGN.md — portable design-context manifest · @atlaskit/eslint-plugin-design-system + @atlaskit/eslint-plugin-ui-styling-standard · Hypermod codemod CLI + ads_migration_guides (opens in new tab) |
|---|
| Carbon Design System | Official: Carbon MCP (opens in new tab) | Official: llms.txt (opens in new tab) | Official: carbon-builder skill (v1.1.0) (opens in new tab) | Official: Multi-client skill install matrix (Bob, Claude Code, Claude Desktop, Cursor .mdc, GitHub Copilot coding agent, VS Code) (opens in new tab) | Official: AGENTS.md (root + per-package) in carbon monorepo · Bob AI bug-triage bot (.github/prompts/bob-bug-triage.md + .bob/custom_modes.yaml + issue-triage.yml) · AGENTS.md across sibling Carbon repos (ibm-products, carbon-labs, carbon-ai-chat) (opens in new tab) | Official: Carbon MCP docs section: Overview / Onboarding and setup / Prompts / Token conservation (opens in new tab) | None found | None found | Official: Figma Code Connect, auto-published from main (opens in new tab) | Official: packages/react/.storybook (opens in new tab) | Official: Prompt guidance page (DOs / DON’Ts / starter template / sample prompts) (opens in new tab) |
|---|
| Chakra UI | Official: @chakra-ui/react-mcp (official Chakra UI MCP Server) (opens in new tab) | Official: llms.txt + six sliced variants (opens in new tab) | Official: chakra-ui-builder / chakra-ui-migrate / chakra-ui-refactor (official Claude Code Skills) · .claude/agents — github-issue-triage & ark-ui-version-bumper subagents (opens in new tab) | Confirmed absent: No editor rule files of either convention. chakra-ui/chakra-ui at 065f71ce has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Official: CLAUDE.md (repo root) (opens in new tab) | Official: Dedicated “AI” docs section (get-started/ai/) (opens in new tab) | None found | Official: @chakra-ui/cli snippet add + @chakra-ui/codemod upgrade (opens in new tab) | Confirmed absent: No Code Connect. The chakra-ui/chakra-ui tree at 065f71ce carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Official: .storybook (Storybook 9.1.8) (opens in new tab) | Official: .claude/commands — ark, changelog, github-reviewer slash commands (opens in new tab) |
|---|
| daisyUI | Official and community: daisyUI Blueprint MCP (v1.5) · Community daisyUI MCP servers (birdseyevue/daisyui-mcp et al.) (community) (opens in new tab) | Official: daisyui.com/llms.txt (opens in new tab) | Official: Official daisyUI skill (skills/daisyui/) · Paid Dashboard Skill and Charts Skill (opens in new tab) | Official: .github/instructions/.instructions.md (6 files) (opens in new tab) | Official: AGENTS.md, three of them, one per workspace (opens in new tab) | Official: Editor/LLM setup docs + /ai landing page (opens in new tab) | Official: Agent-plugin marketplaces (.claude-plugin, .codex-plugin, .cursor-plugin, .grok-plugin, .agents) (opens in new tab) | Official: npx skills add saadeghi/daisyui (opens in new tab) | Confirmed absent: No Code Connect. The saadeghi/daisyui tree at 4be86ac8 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Confirmed absent: No Storybook. A complete recursive listing of master (1,016 files, not truncated) holds no .storybook directory, no story module and no path containing “storybook”, and a GitHub code search for “storybook” in the repo returns 0 results. daisyUI ships CSS classes rather than components, and documents them on a SvelteKit site. | None found |
|---|
| HeroUI | Official and community: @heroui/react-mcp (and @heroui/native-mcp) · T-hash06/heroui-mcp (community) (community) (opens in new tab) | Official: llms.txt family (8 files, sliced by context budget) (opens in new tab) | Official: heroui-react Agent Skill (+ heroui-migration, heroui-native) · .claude/agents/ — five specialized subagents + .claude/guides/ (opens in new tab) | Confirmed absent: No editor rule files of either convention. heroui-inc/heroui at 270a475b has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Official: AGENTS.md + CLAUDE.md (contributor-facing) (opens in new tab) | None found | None found | Official: heroui-cli agents-md · heroui.com/install — multi-harness skill installer (opens in new tab) | Confirmed absent: No Code Connect. The heroui-inc/heroui tree at 270a475b carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Official: packages/storybook (opens in new tab) | Official: prompts/ — vendor-specific system prompt packs · .claude/hooks.mjs — pre/post-edit validation loop (opens in new tab) |
|---|
| Nuxt UI | Official and community: Nuxt UI MCP Server · nuxt-mcp (antfu) (community) (opens in new tab) | Official: llms.txt / llms-full.txt (opens in new tab) | Official: nuxt-ui Agent Skill (skills/nuxt-ui/) (opens in new tab) | Confirmed absent: No editor rule files of either convention. nuxt/ui at 282759e7 has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Official: AGENTS.md (repository root) (opens in new tab) | Official: Docs-site AI assistant with live applyTheme tool calling (opens in new tab) | Official: skills/index.json manifest · Agent discovery layer: .well-known/api-catalog, MCP server-card.json, Link headers, sitemap.md, markdown content negotiation (opens in new tab) | Official: nuxt-ui make component CLI (opens in new tab) | Confirmed absent: No Code Connect. The nuxt/ui tree at 282759e7 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Confirmed absent: No Storybook. A complete recursive listing of the v4 default branch (2,151 files, not truncated) holds no .storybook directory, no story module and no path containing “storybook”. Component demos are served by the docs site’s own MDC component-example module and by the Nuxt and Vue playgrounds. | Official: @nuxtjs/mcp-toolkit (opens in new tab) |
|---|
| PatternFly | Official: @patternfly/patternfly-mcp (opens in new tab) | Confirmed absent: https://www.patternfly.org/llms.txt and /llms-full.txt both return 404 (S3 NoSuchKey), as do /mcp and /ai (the AI section lives at versioned paths and 302-redirects from /ai/...). No llms.txt in patternfly-org, patternfly-react, patternfly, or patternfly-mcp repo roots. | Official: pf- consumer skills (32 across 8 plugins) (opens in new tab) | Confirmed absent: No editor rule files of either convention. patternfly/patternfly-org at d849cbd7 has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Official: patternfly-cli AGENTS.md · ai-helpers CLAUDE.md (opens in new tab) | Official: patternfly.org AI section (guidelines + AI-assisted development) (opens in new tab) | Official: patternfly/ai-helpers plugin marketplace (opens in new tab) | Official: @patternfly/patternfly-cli (opens in new tab) | Confirmed absent: No Code Connect. The patternfly/patternfly-org tree at d849cbd7 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Confirmed absent: No Storybook in either repo. Complete recursive listings of main in patternfly-org (2,434 files) and patternfly-react (3,405 files), neither truncated, hold no .storybook directory, no story module and no path containing “storybook”. Components are documented on patternfly.org, built from the org’s own docs framework. | Official: patternfly-mcp repo agent guidelines + builder skills · ai-helpers docs/ — curated LLM-facing PatternFly documentation (opens in new tab) |
|---|
| Primer | Official: @primer/mcp · @primer/brand-mcp (opens in new tab) | Confirmed absent: No llms.txt. https://primer.style/llms.txt returns 404, and /llms-full.txt answers 200 with the docs site’s HTML shell rather than a text file, which is a 404 wearing a different status code. Nothing named llms.txt or llms-full.txt in primer/react at f7872333. | Official: primer/react .github/skills/ (7 skills) (opens in new tab) | Official: primer/react .github/copilot-instructions.md · primer/react .github/instructions/.instructions.md (5 files) (opens in new tab) | Official: primer/primitives AGENTS.md (opens in new tab) | Official: MCP server (primer.style docs) (opens in new tab) | None found | None found | Official: Figma Code Connect (primer/react and primer/brand) (opens in new tab) | Official: packages/react/.storybook (MCP endpoint at /mcp) (opens in new tab) | Official: primer/react .github/agents/*.agent.md (custom subagents) · gh-aw agentic workflows (issue triage + maintenance) (opens in new tab) |
|---|
| React Spectrum / Spectrum 2 (S2) | Official: @react-spectrum/mcp (React Spectrum S2 MCP server) (opens in new tab) | Official: llms.txt + per-page .md twins + “Copy for LLM” button (opens in new tab) | Official: react-spectrum-s2 Agent Skill · spectrum-audit Agent Skill · migrate-react-spectrum-v3-to-s2 Agent Skill · .claude/ in adobe/react-spectrum (release-notes skill + oxfmt hook) (opens in new tab) | Confirmed absent: No editor rule files of either convention. adobe/react-spectrum at c9d3ad08 has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Confirmed absent: No agent instruction file at any depth: adobe/react-spectrum at c9d3ad08 has no AGENTS.md and no CLAUDE.md anywhere in the tree. | Official: “Working with AI” docs page (/ai, aliased from /mcp) (opens in new tab) | Official: Agent Skills discovery manifest (/.well-known/skills/index.json) (opens in new tab) | None found | Confirmed absent: No Code Connect. The adobe/react-spectrum tree at c9d3ad08 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Official: .storybook-s2 (opens in new tab) | Official: .mcpb Claude Desktop connector bundle · @react-spectrum/codemods s1-to-s2 --agent mode (opens in new tab) |
|---|
| Salesforce Lightning Design System | Official: Salesforce DX MCP Server — SLDS tools (lwc-experts toolset) · guide_figma_to_lwc_conversion (Figma → LWC, Beta) (opens in new tab) | Confirmed absent: No llms.txt. https://www.lightningdesignsystem.com/llms.txt and /llms-full.txt both return 404 from zeroheight, which hosts the docs. Nothing named llms.txt or llms-full.txt in salesforce-ux/design-system at 9bc6a404. | Official: @salesforce/afv-skills — design-systems-slds-apply / -validate / -slds2-migrate · design-system-2-starter-kit — local .agent/skills/ (opens in new tab) | Official: design-system-2-starter-kit — .builderrules (opens in new tab) | Official: design-system-2-starter-kit — AGENTS.md + CLAUDE.md (opens in new tab) | Official: AI and SLDS 2 (docs page) (opens in new tab) | Official: Bundled SLDS artifact registries + search scripts (hooks/utilities/blueprints/icons) (opens in new tab) | Official: @salesforce-ux/slds-linter (opens in new tab) | Confirmed absent: No Code Connect. The salesforce-ux/design-system tree at 9bc6a404 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Official: .storybook (SLDS 1) (opens in new tab) | Official: mcp.json — zero-config MCP wiring in the starter kit (opens in new tab) |
|---|
| shadcn/ui | Official and community: shadcn MCP server (bundled in the CLI) · Community MCP servers (Jpisnice, heilgar, magnusrodseth) (community) (opens in new tab) | Official: ui.shadcn.com/llms.txt (opens in new tab) | Official: shadcn Agent Skill (skills/shadcn) · migrate-radix-to-base skill (opens in new tab) | Official: .cursor-plugin/plugin.json (Cursor plugin) · .cursor/rules/registry-bases-parity.mdc (opens in new tab) | Confirmed absent: No agent instructions of shadcn’s own. The only AGENTS.md files in shadcn-ui/ui at 47c7f92d are templates/next-app/AGENTS.md and templates/next-monorepo/AGENTS.md, and the two are byte-identical, four lines long, and fenced in <!-- BEGIN:nextjs-agent-rules --> markers that say who wrote them. What they say is about Next.js: this is not the Next.js you know, the APIs may differ from your training data, read the guides in node_modules/next/dist/docs/ before writing any code. Neither file mentions shadcn, the registry, or a component. No CLAUDE.md anywhere in the tree. | None found | Official: Registry system + community registry index (opens in new tab) | Official: shadcn CLI as the agent’s action surface (opens in new tab) | Confirmed absent: No Code Connect. The shadcn-ui/ui tree at 47c7f92d carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Confirmed absent: No Storybook. A complete recursive listing of main (5,748 files, not truncated) holds no .storybook directory, no story module and no path containing “storybook”. Documentation is a bespoke Next.js app (apps/v4) with a live registry preview instead. | Official: .claude/ directory (launch.json + settings.local.json) (opens in new tab) |
|---|
| Shopify Polaris | Official and community: @shopify/dev-mcp (Shopify Dev MCP server) · polaris-mcp-server (community) (community) (opens in new tab) | Confirmed absent: No llms.txt. https://shopify.dev/llms.txt returns 404, and so does the same file under the Polaris docs path. Nothing named llms.txt or llms-full.txt in Shopify/polaris at 2b1ea886. | Official: shopify-polaris-app-home (Shopify AI Toolkit skill) (opens in new tab) | Confirmed absent: No editor rule files of either convention. Shopify/polaris at 2b1ea886 has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Confirmed absent: No agent instruction file at any depth: Shopify/polaris at 2b1ea886 has no AGENTS.md and no CLAUDE.md anywhere in the tree. | None found | Official: Shopify AI Toolkit multi-host plugin distribution (opens in new tab) | None found | Confirmed absent: No Code Connect. The Shopify/polaris tree at 2b1ea886 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Official: polaris-react/.storybook (opens in new tab) | Official: AI-crawler blocklist + noai meta (anti-affordance) · @shopify/polaris-types (machine-readable component contract) · Per-page markdown twins with Accept: text/markdown negotiation (opens in new tab) |
|---|
| Invested · 5 |
|---|
| Cloudscape Design System | Community: @agentience/react-design-systems-mcp (community) · praveenc/cloudscape-docs-mcp (community) (opens in new tab) | Official: cloudscape.design/llms.txt (opens in new tab) | None found | Confirmed absent: No editor rule files of either convention. cloudscape-design/components at e9c0c768 has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Official: AGENTS.md across 14 cloudscape-design repos (opens in new tab) | Official: AI Tools Support (official docs page) (opens in new tab) | Official: Per-component JSON API definitions (index.html.json) · Code Snippets corpus (181 addressable exemplars) (opens in new tab) | None found | Confirmed absent: No Code Connect. A GitHub code search for ‘code-connect’ across org:cloudscape-design returns nothing, so Figma Dev Mode has no first-party binding from a design node to a Cloudscape component. What AWS does publish is an official Figma library at figma.com/@cloudscape, with every component, its variants and its variables (color, text, layer styles), usable as a published library or as a sticker sheet. That is a designer’s artifact, not a machine-readable one. | Confirmed absent: No Storybook. A complete recursive listing of main (3,705 files, not truncated) holds no .storybook directory, no story module and no path containing “storybook”, matching the 0 hits an org-wide code search returns. Cloudscape runs its own docs site plus an internal pages/ dev harness. | None found |
|---|
| Mantine | Official and community: @mantine/mcp-server (official, experimental) · hakxel/mantine-ui-server (community, stale) (community) · mantine-mcp (community, projectashik) (community) (opens in new tab) | Official: llms.txt + llms-full.txt (regenerated every release) (opens in new tab) | Official: mantinedev/skills — three official Claude Code skills (opens in new tab) | Confirmed absent: No editor rule files of either convention. mantinedev/mantine at 953192e2 has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Official: AGENTS.md / CLAUDE.md (byte-identical duplicates) · .claude/settings.json — PostToolUse auto-format hook (opens in new tab) | Official: “Mantine with LLMs” guide (mantine.dev/guides/llms/) (opens in new tab) | Official: Static MCP data registry — mantine.dev/mcp/index.json (opens in new tab) | None found | Confirmed absent: No Code Connect. The mantinedev/mantine tree at 953192e2 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Official: .storybook (opens in new tab) | None found |
|---|
| Material UI (MUI) | Official: @mui/mcp — official MUI MCP server (opens in new tab) | Official: Per-package llms.txt + .md twin for every docs page (opens in new tab) | Official: skills/ — four official Material UI Agent Skills · Org-wide contributor skills in mui/mui-public (.claude/skills + .agents/skills) (opens in new tab) | Confirmed absent: No editor rule files of either convention. mui/material-ui at 7fb01101 has no .cursorrules and no .cursor/ directory, and no .github/copilot-instructions.md, .github/instructions/ or .github/prompts/ either. | Official: Root AGENTS.md (with CLAUDE.md pointer) (opens in new tab) | Official: Getting started > Model Context Protocol (MCP) for MUI (opens in new tab) | None found | None found | Confirmed absent: NOT Code Connect. MUI ships a commercial Figma/Sketch design kit (1,500+ elements, 600+ components) and a free beta Figma plugin, ‘Material UI Sync’, which generates a Material UI theme file of design tokens and component customizations from Figma, previewable in an embedded Storybook panel inside the plugin. The AI bridge to Figma instead runs through the MCP’s generateReactCode designContext argument (grounding codegen in a Figma frame). A code search across the whole mui GitHub org found zero figma.config.json files and zero Code Connect references. | Confirmed absent: No Storybook for the component library. A complete recursive listing of master (41,097 files, not truncated) holds no .storybook directory and no story module. Four paths do contain “storybook”, and none of them is one: two screenshots and an mp4 documenting the Figma sync plugin, and packages-internal/core-docs/src/svgIcons/StorybookIcon.tsx, an icon. mui.com’s own docs site with live demos is the canonical surface. | Official: MUI Recipes (recipes.mui.com) — hosted AI codegen product (opens in new tab) |
|---|
| Microsoft Fluent UI | Official and community: Microsoft.FluentUI.AspNetCore.McpServer (Fluent UI Blazor) · Internal Microsoft Fluent UI React MCP (unreleased) · fluentui-mcp (community, blendsdk) (community) · Other community Fluent UI MCP servers (community) (opens in new tab) | Confirmed absent: No llms.txt. https://fluent2.microsoft.design/llms.txt and /llms-full.txt both answer 200, but what they serve is the docs site’s Astro HTML shell, not a text file, so a fetcher that trusts the status code gets a page where it expected a context file. Nothing named llms.txt or llms-full.txt in microsoft/fluentui at 4aacb7b8. | Official: .agents/skills/ and .claude/skills/ — nine executable skills (opens in new tab) | Official: .github/instructions/copilot.instructions.md (opens in new tab) | Official: AGENTS.md (repo root) (opens in new tab) | None found | None found | None found | Confirmed absent: No Code Connect. The microsoft/fluentui tree at 4aacb7b8 carries no *.figma.tsx, no figma.config.json and nothing on a code-connect path, so Figma Dev Mode has no first-party binding from a design node to a component here. | Official: per-component stories packages (opens in new tab) | Official: copilot-setup-steps.yml — Copilot coding agent environment provisioning (opens in new tab) |
|---|
| Nord Design System | None found | Official: /llms.txt and /llms-full.txt (two-tier, context-budget aware) (opens in new tab) | Official: Nord Agent Skills (nord and nord-full) served from /.well-known/skills/ (opens in new tab) | None found | None found | Official: Working with AI docs section (/ai/ → /docs/developer/working-with-ai) (opens in new tab) | Official: /.well-known/skills/ discovery manifest (opens in new tab) | None found | None found | Official: Storybook 10 playground embedded on every component page (opens in new tab) | Official: /raw/
State of AI in Design Systems