Adapters

An adapter is the layer that makes a third-party component library wear your theme. You keep the library your team already uses; the adapter reads the Recursica tokens and applies them, so a re-themed export restyles every component without touching a call site. See Architecture for how those tokens are structured.

Each adapter is its own repository now, and each one publishes an ADAPTER_STATUS.md saying exactly which components it maps, which it hand-builds, and which it deliberately leaves alone. The sections below are generated from those documents, so what you are reading is whatever the adapters last said about themselves rather than a second copy kept here.

Mantine is the reference implementation and the one this site is built with; Material UI and Carbon are in progress behind it. The adapters are MIT licensed and all follow one pattern, so a contribution is tractable: join the Slack and advocate for it, or build it and open a PR.

Shared packages

Every adapter below builds on the same packages, still in the recursica monorepo — the adapters stay thin because what they have in common is factored out.

• adapter-common — the token plumbing every adapter reads, including the overStyled escape hatch and the props each component accepts.
• adapter-tester — the harness that checks an adapter renders every component in every variant and state.
• storybook-template — the Storybook a designer reviews a themed branch in, before a developer sees the PR.
• recursica-postcss-vars — resolves the exported CSS custom properties at build time.
• recursica-token-analyzer — reports which tokens a codebase actually uses, and which it hardcodes instead.
• recursica-mcp — the MCP server that gives an agent the same token and component knowledge.