One independent model
ThemeDefinition stores the color system. CSS, Tailwind, Material UI, Bootstrap and Figma remain output formats.
About Tintary
Tintary helps frontend and design system teams turn one source color into coherent scales, semantic roles, realistic previews and portable exports.
Why it exists
Frontend work begins after color selection: accessible foregrounds, semantic roles, surface hierarchy, dark mode and framework output still need decisions.
Tintary keeps those decisions visible and testable without turning the workspace into a complex visual editor.
Product principles
ThemeDefinition stores the color system. CSS, Tailwind, Material UI, Bootstrap and Figma remain output formats.
Culori handles parsing and conversion. OKLCH recipes generate scales and surface depth for light and dark modes.
Product patterns, gallery examples and quality audit show how colors work outside isolated swatches.
No account, backend or database. Workspace state and saved themes stay in the browser.
Architecture
Color generation stays pure. UI and gallery state never become export data.
Source colors
Culori engine
Raw scales
Semantic roles
Preview + adapters
Framework-agnostic product truth.
Local editor state and persistence.
Format output without regenerating colors.
Color-only MVP
Included
Not in MVP
Project
I built Tintary as an independent project. It uses Next.js, TypeScript, Tailwind CSS, shadcn/ui, Culori and Zustand, with Vitest, Playwright and axe-core for testing.
Source code and project updates are available on GitHub. You can also contact me through Twitter or LinkedIn.
Tintary
Build the palette, check it in context and export the formats your project uses.