AD

UI Kit Libraries

Automattic Design System

system.automattic.design · checked 9 Oct 2026

Open-source packages for creating Automattic and WordPress interfaces.

How it plugs in

—Public API
NoOpen source
NoFree tier

Signal on UI Kit Libraries5.2#22 of 26

Automattic Design System brings shared packages, tokens, components, and product guidance together. Its public core covers WordPress UI, theming, icons, and data views. React powers the components; packages commonly include Figma libraries and Storybooks, while an MCP server offers documentation to AI agents. Accessibility guidance uses WCAG 2.1 AA as its baseline.

Automattic Design System home page

Review

In a line

Automattic Design System combines packages that teams use to build products. It is free and open source.

What it does

The system gives designers, engineers, and AI tools a shared vocabulary of interface parts, design values, and rules. Its website maps the relationships among those pieces, while package repositories and Storybooks contain detailed component guidance.

Its core packages cover UI components, icons, themes, and data views. The UI package offers product-neutral controls such as buttons, inputs, notices, and overlays. DataViews supplies patterns for collections, including tables, grids, lists, filters, sorting, pagination, bulk actions, and switching views.

The Theme package defines tokens for color, spacing, corner radius, and typography, and it can generate light and dark themes. The system also supports user or plugin customization and dynamic colors intended to maintain accessible contrast. Icons supplies reusable system icons.

How it connects

The public core consists of @wordpress/theme, @wordpress/ui, @wordpress/icons, @wordpress/dataviews, and @wordpress/admin-ui. Distribution of the UI package uses npm, and it is unavailable under window.wp.

Most packages pair with a Figma library and a Storybook instance; the site says those Figma libraries remain aligned with the shipping codebase. Public tokens are exposed as CSS custom properties conforming to the Design Token Community Group specification.

The WordPress Design System publishes an MCP server with component documentation, usage advice, and token details for AI agents. Work on public packages takes place in the Gutenberg repository, where contributors can file issues or pull requests; Slack is suggested for questions.

Good fit

This is intended for teams creating new WordPress products, plugins, or standalone React interfaces built for WordPress. It also serves designers and engineers working across Automattic products, brands, and contexts.

The packages let teams reuse responsive components, data-interface patterns, icons, theme values, and accessibility guidance rather than create each element anew. WCAG 2.1 AA is the baseline in its design principles.

Watch for

The website labels the Automattic Design System layer internal, while marking its core packages public. Check which package and usage guidance applies to your project before adopting it.

Detailed component rules are maintained in separate repositories and Storybooks, so adoption requires consulting those package-level resources. Figma is the primary design asset format.

Pricing

There is no charge for Automattic Design System. Its pricing note identifies the project as open source, and its core packages are public.

Verdict

Choose this system for WordPress-facing React interfaces or shared Automattic-style components, tokens, and data views, with Figma and Storybook references. npm distribution, token exports, and the AI documentation server connect different parts of the workflow.

Consider alternatives if your project does not use the WordPress-oriented packages or if the internal-only system layer is unsuitable.

Our take

Automattic Design System is a practical starting point for WordPress product and plugin teams seeking shared React components, data patterns, icons, and theme tokens. Free, open-source access lowers the barrier to entry, while Figma, Storybook, npm, and MCP resources support different workflow needs. The key limitation is scope: an internal Automattic layer is separated from public core packages, and detailed guidance is distributed elsewhere. Teams outside the WordPress ecosystem should verify that the packages and guidance fit their interfaces.

  • Free, open-source offering
  • Public packages for UI, themes, icons, and data views
  • Figma libraries and Storybooks commonly accompany packages
  • MCP server offers component and token guidance to AI agents
  • WCAG 2.1 AA guidance with responsive components
  • Automattic Design System layer is labeled internal
  • Detailed guidance is distributed across repositories and Storybooks
  • UI package uses npm and is unavailable under window.wp
  • Figma is the primary design asset format
  • Pick it ifWordPress products, plugins, and standalone React interfaces; Teams sharing UI patterns across Automattic-related products; Designers and engineers working with Figma and Storybook
  • Skip it ifYou need a system unrelated to WordPress-oriented packages; An internal-only layer conflicts with your project needs

Pricing

Free; the project is open source and its core packages are public.

Questions

What is Automattic Design System?

It combines packages for product construction, with a website explaining their relationships and contribution process.

Which packages are public?

The public core lists @wordpress/theme, @wordpress/ui, @wordpress/icons, @wordpress/dataviews, and @wordpress/admin-ui.

Does it work with Figma?

Packages commonly include a Figma library and Storybook instance, and the site says those libraries stay aligned with the shipping code.

Is it accessible?

Its design principles use WCAG 2.1 AA as the baseline, and public tokens are exported as CSS custom properties conforming to the Design Token Community Group specification.

Can AI tools use it?

Yes. Its MCP server gives AI agents component documentation, usage advice, and design-token details.

How can people contribute?

Development of public packages occurs in the Gutenberg repository, where contributors can file an issue or pull request; Slack is suggested for questions.

Where is the UI package distributed?

@wordpress/ui is distributed through npm and is not available under window.wp.