Integrations

Integrations The color engine, where you already work.

Five ways to use the site’s color and accessibility engine outside the site, each with a setup you can follow from start to a first result. Only what you can install today is listed, and every version and example was checked on 14 October 2026.

Ready to install

Five integrations, each with a setup guide

Each guide goes from installing to a first real result. The product pages linked beside them describe every feature.

Workflows

Four workflows built on the exports and the API

Nothing from this site to install: each takes the token studio’s exports, or the API, into a tool you already use, with files to reproduce it.

Choosing

Which one for which job

Which integration fits which job
JobUse
Check the contrast and accessibility of a page you are looking atBrowser extension
Catch low contrast while you write CSS, and fix it in placeVS Code
Lint markup against WCAG across a whole projectVS Code
Convert colors or check pairs from your own code or serviceREST API
Put a contrast checker on your own pageContrast embed
Give a Tailwind or CSS codebase a measured color systemDesign tokens
Create the same tokens as variables in a Figma fileDesign tokens
Start a Tailwind project with an accessible theme and componentsTailwind theme
Bring a Figma file’s variables into CSSFigma variables
Use the tokens in a React app, with light, dark and system themesReact tokens
Fail a pull request when a color pair drops below its contrastContrast in CI

Not available yet

Built, but not released

These exist in the site’s code but have no public listing or package, so there is nothing to install. They get a setup guide here when they are released.

Integrations that are not released yet
IntegrationStatus
Figma pluginNo Figma Community listing.
Penpot pluginNo listing in Penpot’s plugin catalog.
Sketch pluginNo published download.
Raycast extensionNot in the Raycast Store.
Alfred workflowNo published download.
Slack and Discord botsNot open for teams to add.
JavaScript and Python clients, and the auric CLI@auric-artisan/api, @auric-artisan/cli, auric-artisan are not on npm or PyPI. Call the API over HTTP, as the API guide shows.
MCP serverNo published package.

Method

How these guides stay accurate

  1. Versions come from the stores. The Chrome Web Store, Firefox Add-ons, the VS Code Marketplace and the API itself are read on the day of each check.

  2. Permissions and settings come from the shipped packages. They are read from the extension’s release ZIP and the published VS Code packages, not from notes.

  3. Every example is run. The VS Code diagnostic comes from the published extension’s own code, the API responses from the API’s own server, and the Tailwind classes from a real Tailwind build.

  4. Nothing unreleased is linked. A package the registries do not have is listed as not available rather than given an install command.

Checked against

Where these facts come from

Versions, requirements and examples on this page were checked on . Each guide records how it was checked.

Found a mistake? Write to us and we will correct it.