brand-visual-generator
The brand-visual-generator skill helps users define, audit, or apply a brand's visual identity including typography, color palettes, design tokens, spacing systems, and frontend aesthetics. Use it when establishing or refining how a brand looks across web products, presentations, print materials, and documents, or when the user references design systems, brand guidelines, style guides, or specific visual elements like fonts and color schemes.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/brand-visual-generator && cp -r /tmp/brand-visual-generator/skills/components/branding/brand-visual ~/.claude/skills/brand-visual-generatorSKILL.md
# Components: Brand Visual Identity Guides visual identity for consistent brand presentation. Companies with consistent branding see up to 23-33% revenue lift; 94% of consumers say consistency influences buying decisions. **Keywords**: visual identity, design tokens, color palette, typography, CSS variables, slide deck, brand guidelines, frontend aesthetics, accessibility **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Section 12 (Visual Identity) for colors, typography, spacing. See **branding** for brand strategy and visual identity strategy layer. Identify: 1. **Scope**: New brand, audit, or component design 2. **Touchpoints**: Web, print, social, product UI, **slides** (PowerPoint, Google Slides, Keynote), **documents** (Word, Google Docs, PDF reports) 3. **Existing assets**: Logo, style guide, design files ## Best Practices ### Typography - **Two-font system**: One display font for headlines, one body font for text. Contrast + harmony: different enough for distinct roles, similar enough to feel cohesive. - **Body font**: Prioritize legibility—large x-height, open counters. For neutral/safe: Source Sans 3, Lora, IBM Plex Sans. **For distinctiveness**: avoid overused AI fonts (Inter, Roboto, Arial, system fonts); prefer characterful choices that elevate the brand. See **Frontend Aesthetics**. - **Headline font**: Communicates brand voice; must be readable in under one second. Carries personality while body handles infrastructure. - **Type scale**: Use ratios 1.25–1.5 (Major Third or Perfect Fifth) for hierarchy. Limit to 3–4 styles per block. - **Pairing rule**: Decorative fonts only with neutral typefaces. Assign distinct roles; avoid mixing more than two families. - **Sizes**: Hero, section, subheading, body, caption; responsive scaling. Line length max 120 chars; generous line-height. ### Color Palette - **Structure**: Primary, secondary, CTA, background, text. Use flexible systems (core hero color + complementary shades), not single rigid colors. - **Industry mapping**: Finance → blue, gray, navy (stability); Luxury → rose gold, burgundy, black (exclusivity); Tech → teal, neon accents, charcoal (innovation); Wellness → lavender, peach, mint (calm); Sustainability → sage green, earthy tones. - **Reproduction**: HEX, RGB, CMYK for print and digital. For **programmatic slides** (e.g. python-pptx), map brand HEX to RGB tuples `(R, G, B)` for fills and text; keep a single source of truth table (HEX + RGB) in the deliverable. - **Accessibility**: Contrast >=4.5:1 for normal text, >=3:1 for large text (18px+ or 14px+ bold). Don't rely on color alone for information. ### Spacing - **Margins**: Horizontal (e.g. 120px), vertical section padding - **Grid**: Consistent spacing scale (8px base common) - **Logo clear space**: Minimum space around logo; document in brand guide ### Logo Usage - **Variants**: Primary, secondary, monogram; light/dark backgrounds - **Minimum size**: Prevent illegibility - **Don't**: Stretch, recolor, add effects without approval ### Anti-Patterns (Avoid) - **Aesthetics over functionality**: Don't sacrifice usability for visual appeal. - **Unclear CTAs**: Limit primary CTA to one per section; visually differentiate primary vs secondary. - **Inconsistent elements**: Pixelated icons, mismatched spacing/typography/color reduce trust. - **Poor text hierarchy**: Disordered, cluttered text confuses users. - **Overusing effects**: Drop shadows, pop-ups, crowded UI distract from content. - **Chasing trends blindly**: Adopt trends only when they fit project needs. - **Ignoring performance**: Heavy assets and complex layouts hurt load times. - **Generic AI aesthetics**: Inter, Roboto, Arial, Space Grotesk, and system fonts contribute to cookie-cutter design; avoid clichéd schemes (e.g., purple gradients on white). Prefer distinctive choices when brand differentiation matters. - **Emoji as icons**: Use SVG icons (Heroicons, Lucide, Simple Icons)—never emojis (🎨 🚀 ⚙️) as UI icons; emojis look unprofessional and inconsistent. - **Unstable hover states**: Use color/opacity transitions on hover; avoid scale transforms that shift layout or cause content jump. ### Accessibility Checklist - **Contrast**: Normal text >=4.5:1; large text >=3:1; interactive elements >=3:1. - **Focus**: Visible focus indicator (>=2px solid, 3:1 contrast); logical Tab order; no keyboard traps. - **Color**: Never use color alone to convey information; add text or icons for states (error, success). - **Keyboard**: All interactive elements reachable via Tab, Enter, Spacebar. - **Reduced motion**: Respect `prefers-reduced-motion` for animations. ## Frontend Aesthetics Guides distinctive, production-grade frontend implementation. Components (hero, CTA, footer, etc.) and pages (landing, home, features) should reference these principles for visual differentiation. **Intentionality over intensity**: bold maximalism and refined minimalism both work when executed with precision. ### Typography - **Avoid generic AI fonts**: Inter, Roboto, Arial, system fonts, Space Grotesk. These create cookie-cutter aesthetics. - **Distinctive pairing**: One display font (headlines, personality) + one refined body font (readability). Choose characterful, unexpected fonts that elevate the interface. - **Consistency**: Use CSS variables; limit to 3–4 type styles per block. ### Motion - **High-impact moments**: One well-orchestrated page load with staggered reveals (`animation-delay`) creates more delight than scattered micro-interactions. - **Prioritize**: CSS-only for HTML; Motion library for React when available. Scroll-triggering and hover states that surprise. - **Accessibility**: Always
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.