Your colors, in every prompt.
Stop correcting your AI. Give it a file that explains your palette.
Your AI defaults to Tailwind blue
You spend hours building a color system. Roles, tokens, contrast ratios. Then you open your AI tool and say "build me a card component" and it gives you bg-blue-500 and text-white.
Your colors are gone. The AI has no idea they exist. You correct it. Every. Single. Time.
Everything the AI needs to stay on brand
Roles
Background, Ink, Accent, Support, Neutral — each with hex, RGB, and usage guidance. The AI knows what goes where.
Contrast ratios
Pre-computed WCAG AA/AAA scores for every meaningful pair. The AI makes accessibility-correct decisions without calculating anything.
Code blocks
Copy-paste CSS custom properties and Tailwind v4 @theme tokens. The AI drops them straight into your code.
Rules
Explicit do/don't constraints. Never use accent as body text. Always maintain 4.5:1 contrast. The AI stays on brand.
Plain markdown. Every tool picks it up.
Claude Code
Reads project files automatically. COLORS.md in your root is picked up on every conversation.
Cursor
Indexes your workspace files. The palette becomes part of the codebase context.
Windsurf
Reads project files for context. Your colors are always available.
GitHub Copilot
Uses open files and workspace context. Keep COLORS.md open or reference it in prompts.
Three steps. One file. Done.
Generate
Extract from an image, build from color theory, or remix an inspiration palette.
Export
Hit the AI Palette button. Get a complete COLORS.md with roles, tokens, contrast ratios, and rules.
Drop in project root
Same convention as README.md or CLAUDE.md. Every AI tool picks it up. No plugins, no config.
Generate your AI palette
One click. One file. Your colors in every prompt.