Developer references
Developer color references
Copy syntax for CSS, mobile SDKs, data viz, and terminals — with HEX, RGB, and CMYK on every row. Pair with interactive tools when you need full token ramps.
Search references
FAQ
What is in each developer reference page?
Every page includes a starter template you can copy wholesale, a filterable grid of syntax samples, and HEX plus RGB/CMYK chips for each swatch. Open a card to copy platform-specific code — CSS custom properties, Android XML, Swift UIColor, Flutter Color(0xFF…), and more.
Starter template vs color samples — which should I use?
Use the starter template when bootstrapping a file (colors.xml, tailwind.config.js, :root tokens). Use color samples when you need one-off literals or to compare formats (HEX, rgb(), oklch()) for the same hue.
Are HEX values identical on every platform?
HEX is sRGB. Mobile wide-gamut displays, terminal themes, and Matplotlib backends may render differently. Treat HEX here as the shared design-system anchor; verify on target hardware or emulators for brand-critical UI.
Where do full 50–950 ramps come from?
These pages focus on syntax and single swatches. For scales and export, use ChromaXP CSS variables, Tailwind config, and Android colors.xml generators — including OKLCH-based ramps where supported.