Compile your design system into an Agent Plugin. Extract an identity from any reference, emit SKILL.md + tokens.css, lint what bypasses your tokens.

A coding agent writes on-brand UI when it can read your tokens as an API and your composition rules as instructions. Tinte compiles both from one identity config into a single installable artifact.

bunx tinte from --emit-script       # print the extraction script for a live page
bunx tinte from --normalize <json>  # turn captured styles into a draft identity
bunx tinte build --plugin           # compile the identity into an Agent Plugin
bunx tinte lint <paths>             # exit 1 on any color that bypasses the tokens

Extraction, compilation, and enforcement all read the same tinte.config.json. Nothing is restated by hand.

tinte build --plugin emits:

acme-plugin/
├── plugin.json
└── skills/
    └── acme-design/
        ├── SKILL.md
        └── references/
            └── tokens.css

SKILL.md carries the type scale, the voice, and the composition law. tokens.css is the token file the agent reads as an API.

tinte.dev is styled by the plugin Tinte compiles from its own config, and both artifacts are fetchable at their real paths:

• tinte.dev/design.md
• tinte.dev/tokens.css

An agent can install this design system the same way it would install yours.

The classic workbench is still here: start from a reference, convert to any provider, install it.

bunx tinte <theme-slug>             # install into VS Code, Cursor, or Zed
npx shadcn@latest add https://tinte.dev/api/preset/one-hunter

13 semantic OKLCH tokens compile to shadcn/ui presets, VS Code themes, terminal configs (Alacritty, Kitty, Warp, Windows Terminal), and 19+ formats from the same source of truth.

Every public Tinte theme is installable as a shadcn registry:base item:

npx shadcn@latest add https://tinte.dev/api/preset/{slug}
npx shadcn@latest add https://tinte.dev/api/preset/{slug}/font?variable=sans

Get the full preset pack (base + fonts + install commands):

GET https://tinte.dev/api/preset/{slug}?type=pack

Browse themes:

GET https://tinte.dev/api/themes/public?search=minimal

ray.tinte.dev — code screenshots + theme extraction.

• 500+ syntax themes, 16 languages, PNG/SVG export
• Free REST API (60 req/min, no auth)
• Extract color themes from images: POST ray.tinte.dev/api/v1/extract-theme
• Screenshot with any Tinte theme: POST ray.tinte.dev/api/v1/screenshot

curl -X POST https://ray.tinte.dev/api/v1/screenshot \
  -H "Content-Type: application/json" \
  -d '{"code": "const x = 42;", "language": "typescript", "theme": "one-hunter"}' \
  --output screenshot.png

Tinte generates the system, Elements installs it, Ray shows it.

• @tinte/core — Theme primitives, OKLCH color model, type definitions
• @tinte/providers — 19+ format converters (shadcn, VS Code, terminals, design tools)
• tinte - Agent Plugin compiler (from, build, lint) and theme installer

bun install      # Install dependencies
bun dev          # Start development server
bun build        # Production build

• Tinte: tinte.dev
• Ray: ray.tinte.dev
• Elements: tryelements.dev
• Skill API: tinte.dev/api/skill
• API Docs: ray.tinte.dev/docs

MIT License - see LICENSE for details.