critique-brand-consistency
Critique a screen's brand consistency against mood.md, voice.md, and tokens.md.
What this skill does
# 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
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".