Skip to content
cccskills
FreePublished on GitHub

critique-brand-consistency

Review a rendered screen against existing brand guidelines for visual mood, wording, and design tokens, the named values for colors, spacing, and typography. Report mismatches, suggest specific corrections, and rate each area by issue severity.

OriginalShow the original description

Critique a rendered screen against mood.md, voice.md, and tokens.md. Use when those brand files exist and you are checking compliance. For defining the visual language itself, use `illustration-style` (ui-design).

Run score Not tested

See how to install

Good for

  • Checking a screen against brand guidelines
  • Reviewing button labels and error message wording
  • Finding deviations from defined design tokens
  • Organizing brand issues and specific corrections

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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?
  • Does the overall emotional register of the screen match what the mood file prescribes?

Voice Alignment

Compare all visible copy to the voice guidelines.

  • Does the tone match (e.g., direct vs. conversational, formal vs. friendly)?
  • Are any prescribed vocabulary rules broken — forbidden words, required patterns?
  • Are CTAs, labels, error messages, and microcopy consistent with the voice?

Token Compliance

Compare every design value on screen to the token definitions.

  • Are hardcoded hex values used where a colour token should apply?
  • Are spacing, radius, or shadow values that deviate from tokens present?
  • Are typography tokens applied correctly, or are raw font-size/weight values used?
  • List every non-compliant value with its token equivalent.

Output Format

For each dimension — Mood, Voice, Token Compliance — provide:

  1. Observation — what you see (neutral, factual)
  2. Divergence — what conflicts with the reference file and why it matters
  3. Fix — the exact correction (preferred wording, correct token name, etc.) Rate each dimension: pass / minor issue / major issue.

Common Failure Patterns

  • Hardcoded values drifting from tokens over time
  • Copy written without consulting voice guidelines, defaulting to generic UI language
  • Imagery or illustration sourced outside the brand mood reference
  • Inconsistent radius or shadow values across components on the same screen

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a-b-test-design

FreeSummary

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

affinity-diagram

FreeSummary

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill