officialcommunitybothconfirmed absentblank: none found
Which AI affordances each of the 21 design systems ships, and whether they’re official, community-built, or both. A dot marks an absence confirmed against the system’s own repository or docs, and the cell says what was checked. An empty cell means the survey found no such affordance.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Confirmed absent: No llms.txt. https://designsystem.digital.gov/llms.txt and /llms-full.txt both return 404. Nothing named llms.txt or llms-full.txt in uswds/uswds at 6c8bde97.
Confirmed absent: No editor rule files of either convention. uswds/uswds at 6c8bde97 has no `.cursorrules` and no `.cursor/` directory, and no `.github/copilot-instructions.md`, `.github/instructions/` or `.github/prompts/` either.
Confirmed absent: No Code Connect. The uswds/uswds tree at 6c8bde97 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.