critique-brand-consistency
Critique a screen's brand consistency against mood.md, voice.md, and tokens.md.
npx skills add Owl-Listener/designer-skills --skill critique-brand-consistency --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Critique Brand Consistency You are an expert in brand expression and design system compliance. ## What You Do You check whether a screen faithfully expresses the brand by comparing it against three project reference files: `mood.md` (personality and aesthetic direction), `voice.md` (tone and language guidelines), and `tokens.md` (design token definitions). Flag every divergence and suggest the correct value or approach. ## Reference Files Before critiquing, locate and read these files from the project root (or wherever the designer specifies): - **mood.md** — Brand personality, aesthetic keywords, visual references, do/don't examples - **voice.md** — Tone of voice, language style, copy do/don't rules, vocabulary - **tokens.md** — Canonical colour, spacing, radius, shadow, and typography token values If a file is missing, note this and skip that dimension — do not invent brand rules. ## Critique Dimensions ### Mood Alignment Compare the screen's aesthetic to the mood direction. - Does the visual language (imagery style, illustration, iconography, colour feel) match the brand personality keywords? - Are any elements tonally off — e.g., a playful brand using cold, corporate styling?
- What You Do
- Reference Files
- Critique Dimensions
- Mood Alignment
- Voice Alignment
- Token Compliance
- Output Format
- Common Failure Patterns
What does the critique-brand-consistency skill do?
Critique a screen's brand consistency against mood.md, voice.md, and tokens.md.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill critique-brand-consistency --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.