ui-contrast-review
Skill4 starsChanged 6 months agoMITView on GitHub
Reviewing UI for light/dark contrast, readability, focus states, color-token drift, theme regressions.
In this repository59 other files it gives its agents.
- ad-copy-generationSkill
- ad-creative-fatigue-detectorSkill
- ad-policy-complianceSkill
- amazon-ads-optimizerSkill
- anomaly-detectorSkill
- attribution-modelingSkill
- audience-expansion-strategySkill
- bid-optimizationSkill
- budget-optimizerSkill
- campaign-ide-handoffSkill
- campaign-preflightSkill
- campaign-structure-auditorSkill
- chatgpt-ads-conversion-trackingSkill
- chatgpt-ads-launchSkill
- competitor-analysisSkill
- creative-testingSkill
- cross-platform-attributionSkill
- cross-platform-launcherSkill
- dayparting-schedulerSkill
- executive-reportingSkill
- first-party-data-strategySkill
- google-ads-operatorSkill
- google-ads-quality-scoreSkill
- google-shopping-optimizerSkill
- gtm-metricsSkill
- incrementality-testingSkill
- keyword-researchSkill
- kill-scale-rulesSkill
- klaviyo-campaignsSkill
- landing-page-optimizerSkill
- launch-gatesSkill
- linkedin-ads-operatorSkill
- linkedin-ads-targetingSkill
- media-plan-builderSkill
- meta-ads-diagnosticsSkill
- meta-ads-operatorSkill
- mmm-budget-plannerSkill
- multi-channel-reportingSkill
- multi-platform-ads-operatorSkill
- multi-platform-launchSkill
- negative-keyword-minerSkill
- openai-ads-operatorSkill
- performance-max-optimizerSkill
- pixel-capi-auditorSkill
- pixel-capi-setupSkill
- platform-cost-benchmarksSkill
- public-ad-library-intelligenceSkill
- retargeting-sequence-designerSkill
- roas-calculatorSkill
- seasonal-budget-plannerSkill
- spearSkill
- spec-driven-devSkill
- synter-mcp-setupSkill
- tiktok-ads-operatorSkill
- tracking-leak-detectorSkill
- ugc-creative-briefSkill
- utm-builderSkill
- video-ad-scriptwriterSkill
- x-ads-operatorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Avoid one-off per-page color patches unless the issue is intentionally local.
- Distinctive: line 51
Look for token drift.
- Distinctive: line 64
Use WCAG AA as the baseline heuristic:
- Distinctive: line 70
When exact ratios are not available, make a practical engineering judgment:
- Distinctive: line 72
if text is even slightly hard to read in either theme, treat it as a bug
- Distinctive: line 73
if borders disappear into the background, treat it as a bug
- Distinctive: line 74
if disabled and secondary states become illegible, treat it as a bug
- Distinctive: line 97
If no issues are found, state that explicitly and mention what was checked.
- Distinctive: line 105
ensure disabled text is still readable, not just low-opacity
- Distinctive: line 109
only checking dark mode
- Distinctive: line 110
only checking screenshots without interaction states
- Distinctive: line 116
When browser tooling is available, review the real rendered UI.
- Distinctive: line 118
When browser tooling is not available, inspect:
- Distinctive: line 125
Start with the shared primitives if the same contrast problem appears in multiple pages.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UI Contrast Review
Review UI surfaces for theme-driven readability and visibility failures.
Primary Goal
Catch light-mode and dark-mode contrast regressions before they ship.
Prefer system fixes:
- shared tokens
- semantic color variables
- reusable component classes
Avoid one-off per-page color patches unless the issue is intentionally local.
Review Workflow
- Identify the target surfaces.
- page routes
- reusable components
- empty states
- tables
- dialogs
- badges
- charts
- forms
- Check both themes.
- light theme
- dark theme
- hover / active / disabled / selected states
- focus rings and keyboard focus visibility
- Inspect the highest-risk UI pairs.
- body text vs background
- muted text vs card background
- button label vs button fill
- border vs surrounding surface
- placeholder text vs input background
- badge text vs badge fill
- link text vs surrounding paragraph
- chart lines/bars vs canvas background
- toast/alert text vs status fill
- Look for token drift.
- hard-coded Tailwind colors mixed with semantic theme tokens
text-muted-foregroundon surfaces that are already mutedborder-white/10orborder-black/10used in the wrong theme- color combinations that only work in one theme
- Recommend the smallest durable fix.
- first choice: theme variable / semantic token
- second choice: shared component class
- last choice: local page override
Minimum Contrast Standard
Use WCAG AA as the baseline heuristic:
- normal text: aim for 4.5:1 or better
- large text: aim for 3:1 or better
- UI boundaries and focus indicators: visibly distinct without requiring hover
When exact ratios are not available, make a practical engineering judgment:
- if text is even slightly hard to read in either theme, treat it as a bug
- if borders disappear into the background, treat it as a bug
- if disabled and secondary states become illegible, treat it as a bug
Output Format
For each issue, provide:
- surface
- theme
- failing element
- why it fails
- preferred fix
- file/component reference when available
Use this structure:
Findings
1. [severity] Surface — issue
File: path/to/file.tsx
Theme: light|dark|both
Fix: semantic token or component-level changeIf no issues are found, state that explicitly and mention what was checked.
Good Fix Patterns
- replace hard-coded color with semantic token
- raise muted foreground contrast one step
- strengthen border token for light theme separately from dark theme
- give focus rings a dedicated accessible token
- ensure disabled text is still readable, not just low-opacity
Avoid
- only checking dark mode
- only checking screenshots without interaction states
- fixing with arbitrary hex values when a shared token should exist
- shipping “looks okay on my screen” judgments without checking both themes
Notes
When browser tooling is available, review the real rendered UI.
When browser tooling is not available, inspect:
- route components
- shared UI primitives
- Tailwind utility usage
- CSS variables / theme tokens
Start with the shared primitives if the same contrast problem appears in multiple pages.
About this skill
Part of the Synter free skills collection — open-source agent skills for advertising, PPC, and marketing automation.
Want this skill (and 40+ more) running on autopilot against your live ad accounts? Try Synter — AI Agent Media Buyers that connect to Google, Meta, LinkedIn, TikTok, Reddit, Amazon, and 7+ more platforms.
- 🌐 syntermedia.ai
- 📚 All free skills
- 💬 Built by @syntermedia — questions? Open an issue.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

