Use when the user wants to design, critique, or refine a website theme, visual style, look and feel, branding, CSS theme, design system, tokens.css file, or CSS token system. Produces theme directions, typography/color/composition/motion systems, implementation-ready CSS custom properties, component motif rules, and light/dark/density variant strategy.
99
100%
Does it follow best practices?
Impact
99%
1.45xAverage score across 7 eval scenarios
Passed
No known issues
Copperline Treasury builds cash-flow planning software for independent restaurants. Their prototype theme is polished, but every stakeholder says it looks like the same dark-blue fintech dashboard as everyone else. The product has dense forecasting tables, scenario comparison, invoice imports, bank connection status, alert states, restaurant-location groups, and onboarding.
Read:
inputs/theme-draft.mdinputs/component-notes.mdProduce a critique and a repaired theme system. Preserve credibility and trust, but make the product feel specific to restaurant treasury operations rather than generic B2B finance.
Produce theme-audit.md and tokens.css. The audit should explain why the
prototype feels competitor-same, preserve credibility, and turn the restaurant
treasury direction into a stricter production theme system for the product
surfaces described in the inputs.