Dark mode interface review with colour tokens and contrast fixes
Reviews an app or website's dark theme from its colour tokens and screen notes, and returns contrast problems, depth and elevation fixes, and a corrected token table. Use it when adding dark mode for the first time or when users say the dark theme is hard to read.
The output this prompt produced, unedited.
The prompt
What to give
Product and platform: [e.g. a budgeting app on Android and iOS]
Colour tokens in light and dark: [paste rows: token name, light value, dark value]
Brand colours that must stay: [e.g. primary #FDB017]
Screens or parts users complain about: [paste, or none]
Charts, images or illustrations used in the interface: [describe]
Check every token and screen
Background is a very dark grey rather than pure black, unless the product needs true black for a reason.
Body text reaches at least 4.5:1 contrast and large text and icons at least 3:1 against their surface.
Raised surfaces such as cards, sheets and menus get lighter as they rise, so depth reads without shadows.
Saturated brand colours are softened for dark surfaces so they do not vibrate.
Error, warning and success colours stay distinct from each other and from the brand colour.
Borders and dividers are visible but quiet.
Charts keep their series apart in dark mode, and images with white backgrounds do not glare.
The theme follows the device setting by default, with a manual choice that is remembered.
Output format
Two-line verdict on the theme.
| Token | Light | Dark | Contrast on its surface | Pass or fail | Suggested dark value |
Screen-by-screen problems with the fix for each.
Elevation scale: four surface levels with suggested values.
Test plan: what to check on a real phone at low brightness and outdoors.
Guardrails
Calculate contrast from the values given; say "estimate" if a value is missing.
Keep brand colours recognisable; adjust lightness before changing hue.
dark mode designdark theme uicolour tokenscolour contrastui accessibilitydesign system
How to run this
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.