Skip to content
Back to search

tinte

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

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Railly/tinte with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Railly/tinte'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/railly--tinte/badge.svg)](/listings/railly--tinte)

HTML

<a href="/listings/railly--tinte"><img src="/api/listings/railly--tinte/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 152 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <h3 align="center">
  2. <a href="https://tinte.dev" target="_blank">
  3. <img src="https://github.com/Railly/tinte/blob/main/apps/web/src/app/icon.svg" width="80" alt="Tinte Logo"/>
  4. </a>
  5. <br/>
  6. <span style="font-weight:600;font-size:20px;color:#2563EB;">Tinte</span>
  7. <br/>
  8. <br/>
  9. <a href="https://vercel.com/oss" target="_blank">
  10. <img src="https://vercel.com/oss/program-badge.svg" alt="Vercel OSS Program"/>
  11. </a>
  12. <br/><br/>
  13. <a href="https://github.com/Railly/tinte/stargazers" target="_blank">
  14. <img src="https://img.shields.io/github/stars/Railly/tinte?style=social" alt="GitHub stars"/>
  15. </a>
  16. &nbsp;
  17. <a href="https://github.com/Railly/tinte/blob/main/LICENSE" target="_blank">
  18. <img src="https://img.shields.io/github/license/Railly/tinte" alt="License"/>
  19. </a>
  20. </h3>
  21. <p align="center">
  22. Compile your design system into an Agent Plugin. Extract an identity from any reference, emit SKILL.md + tokens.css, lint what bypasses your tokens.
  23. </p>
  24. A coding agent writes on-brand UI when it can read your tokens as an API and your
  25. composition rules as instructions. Tinte compiles both from one identity config
  26. into a single installable artifact.
  27. ## Quick Start
  28. ```bash
  29. bunx tinte from --emit-script # print the extraction script for a live page
  30. bunx tinte from --normalize <json> # turn captured styles into a draft identity
  31. bunx tinte build --plugin # compile the identity into an Agent Plugin
  32. bunx tinte lint <paths> # exit 1 on any color that bypasses the tokens
  33. ```
  34. Extraction, compilation, and enforcement all read the same `tinte.config.json`.
  35. Nothing is restated by hand.
  36. `tinte build --plugin` emits:
  37. ```
  38. acme-plugin/
  39. ├── plugin.json
  40. └── skills/
  41. └── acme-design/
  42. ├── SKILL.md
  43. └── references/
  44. └── tokens.css
  45. ```
  46. `SKILL.md` carries the type scale, the voice, and the composition law.
  47. `tokens.css` is the token file the agent reads as an API.
  48. ## This site serves its own design context
  49. [tinte.dev](https://tinte.dev) is styled by the plugin Tinte compiles from its own
  50. config, and both artifacts are fetchable at their real paths:
  51. - [tinte.dev/design.md](https://tinte.dev/design.md)
  52. - [tinte.dev/tokens.css](https://tinte.dev/tokens.css)
  53. An agent can install this design system the same way it would install yours.
  54. ## Theme builder
  55. The classic workbench is still here: start from a reference, convert to any
  56. provider, install it.
  57. ```bash
  58. bunx tinte <theme-slug> # install into VS Code, Cursor, or Zed
  59. npx shadcn@latest add https://tinte.dev/api/preset/one-hunter
  60. ```
  61. 13 semantic OKLCH tokens compile to shadcn/ui presets, VS Code themes, terminal
  62. configs (Alacritty, Kitty, Warp, Windows Terminal), and 19+ formats from the same
  63. source of truth.
  64. ## Preset API (shadcn v4)
  65. Every public Tinte theme is installable as a shadcn `registry:base` item:
  66. ```bash
  67. npx shadcn@latest add https://tinte.dev/api/preset/{slug}
  68. npx shadcn@latest add https://tinte.dev/api/preset/{slug}/font?variable=sans
  69. ```
  70. Get the full preset pack (base + fonts + install commands):
  71. ```
  72. GET https://tinte.dev/api/preset/{slug}?type=pack
  73. ```
  74. Browse themes:
  75. ```
  76. GET https://tinte.dev/api/themes/public?search=minimal
  77. ```
  78. ## Ray by Tinte
  79. **[ray.tinte.dev](https://ray.tinte.dev)** — code screenshots + theme extraction.
  80. - 500+ syntax themes, 16 languages, PNG/SVG export
  81. - Free REST API (60 req/min, no auth)
  82. - Extract color themes from images: `POST ray.tinte.dev/api/v1/extract-theme`
  83. - Screenshot with any Tinte theme: `POST ray.tinte.dev/api/v1/screenshot`
  84. ```bash
  85. curl -X POST https://ray.tinte.dev/api/v1/screenshot \
  86. -H "Content-Type: application/json" \
  87. -d '{"code": "const x = 42;", "language": "typescript", "theme": "one-hunter"}' \
  88. --output screenshot.png
  89. ```
  90. ## Ecosystem
  91. | Product | Role | URL |
  92. |---------|------|-----|
  93. | **Tinte** | Compile design systems into Agent Plugins | [tinte.dev](https://tinte.dev) |
  94. | **Elements** | Install via shadcn registry | [tryelements.dev](https://tryelements.dev) |
  95. | **Ray** | Preview and screenshot | [ray.tinte.dev](https://ray.tinte.dev) |
  96. > Tinte generates the system, Elements installs it, Ray shows it.
  97. ## Packages
  98. - `@tinte/core` — Theme primitives, OKLCH color model, type definitions
  99. - `@tinte/providers` — 19+ format converters (shadcn, VS Code, terminals, design tools)
  100. - [`tinte`](https://www.npmjs.com/package/tinte) - Agent Plugin compiler (`from`, `build`, `lint`) and theme installer
  101. ## Development
  102. ```bash
  103. bun install # Install dependencies
  104. bun dev # Start development server
  105. bun build # Production build
  106. ```
  107. ## Links
  108. - **Tinte**: [tinte.dev](https://tinte.dev)
  109. - **Ray**: [ray.tinte.dev](https://ray.tinte.dev)
  110. - **Elements**: [tryelements.dev](https://tryelements.dev)
  111. - **Skill API**: [tinte.dev/api/skill](https://tinte.dev/api/skill)
  112. - **API Docs**: [ray.tinte.dev/docs](https://ray.tinte.dev/docs)
  113. ## License
  114. MIT License - see [LICENSE](LICENSE) for details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.