Audit and fix the color palette in my app or website
Reviews how color is used across your interface, then gives a consistent palette, color tokens, contrast fixes, and dark-mode adjustments.
The prompt
Help me audit and fix the colors used across my app or website.
Product and audience: [WHAT IT IS, who uses it, business domain]
Primary and secondary brand colors: [HEX CODES]
Colors currently in use: [paste the CSS variables, design tokens, or a list of hex codes and where they appear, or describe screenshots]
Dark mode: [yes / no / planned]
Known problems: [e.g. "too many grays", "buttons look different on each page", "low contrast text"]
Deliver:
1. Audit findings: near-duplicate colors to merge, inconsistent uses (the same meaning shown in different colors), colors that clash with the brand, and text or controls that fail WCAG contrast (4.5:1 for normal text, 3:1 for large text and UI components).
2. Recommended palette: primary and secondary scales (e.g. 50-900), a neutral scale, and semantic colors for success, warning, error, and info, all in harmony with my brand colors.
3. Color tokens: a token table (Token | Light value | Dark value | Use) mapping colors to roles such as background, surface, text, border, primary action, and focus, so components use roles rather than raw hex codes.
4. Dark mode adjustments: avoid pure black, reduce saturation, keep contrast, and check states like hover, disabled, and focus.
5. Before and after mapping: which current colors become which tokens.
6. Accessibility checks: never use color alone to convey meaning; consider common color vision deficiencies.
Give the tokens as CSS custom properties I can paste in. Flag any contrast ratio you have estimated rather than calculated as [CHECK WITH A CONTRAST TOOL].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- WHAT IT IS, who uses it, business domain
- HEX CODES
- yes / no / planned
- CHECK WITH A CONTRAST TOOL
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Review a part design for manufacturability before releaseA design for manufacturability (DFM) review that flags features driving cost, scrap, or long lead times, with suggested changes ranked by impact.
- Decide which enterprise features to build before moving upmarketA prioritized enterprise-readiness roadmap covering SSO, SCIM, audit logs, permissions, and admin controls, tied to deals.
- Design a form people actually finishReviews or designs a form field by field, cutting questions, fixing input types, and improving layout, validation, and completion rates.
- Run a UX teardown of a competitor's product flowBreaks down how competitors handle a specific user flow step by step, comparing patterns, friction, and ideas worth borrowing or avoiding.