skills/strategies/brand/branding/SKILL.md
When the user wants to define, audit, or apply brand strategy—purpose, values, positioning, storytelling, voice, narrative (not only visuals). Also use when the user mentions "brand strategy," "brand story," "brand storytelling," "brand voice," "brand identity," "brand guidelines," "brand purpose," "brand values," "origin story," "brand narrative," "brand personality," "brand archetype," "slide deck branding," "PPT brand colors," or "document style guide." For typography, colors, design tokens, and frontend visuals, use brand-visual-generator.
npx skillsauth add kostja94/marketing-skills brandingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guides brand strategy: purpose, values, positioning, storytelling, voice, and visual identity. Companies with consistent branding see 23–33% revenue lift; people remember stories ~22× more than facts alone. Use this skill when defining a new brand, auditing consistency, or aligning messaging across touchpoints.
Keywords: brand strategy, brand guidelines, visual identity, storytelling, brand voice, design tokens, slide deck, corporate identity, style guide, positioning
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read Sections 2 (Positioning), 3 (Value Proposition), 8 (Brand & Voice), 12 (Visual Identity).
Identify:
| Pillar | Purpose | |--------|---------| | Brand purpose | Why the brand exists beyond profit; one sentence | | Brand values | 4–5 core values; what you stand for; differentiators | | Target audience | Who you serve; ICP; jobs to be done | | Positioning | For [customer] who [need], our [product] is a [category] that [benefit]. Unlike [competitor], we [differentiator] because [reasons] | | Differentiation | Why you, not alternatives; concrete, not vague |
| Element | Content | |---------|---------| | Hero | Your customer; their needs, wants, context | | Problem | What they face; how they solve it now | | Inciting insight | Reframing that creates urgency | | Brand's role | Guide, tool, or partner—not hero; how you enable resolution | | Transformation | What better future looks like; proof (case studies, testimonials) |
| Archetype | Tone | Example | |-----------|------|---------| | Creator | Innovative, imaginative | Adobe | | Caregiver | Nurturing, supportive | Johnson & Johnson | | Ruler | Authoritative, premium | Mercedes-Benz | | Innocent | Simple, optimistic | Coca-Cola | | Sage | Wise, knowledgeable | Google | | Explorer | Adventurous, independent | Patagonia | | Outlaw | Rebellious, disruptive | Harley-Davidson | | Magician | Transformative, visionary | Disney | | Hero | Courageous, determined | Nike | | Lover | Passionate, sensual | Chanel | | Jester | Playful, fun | M&M's | | Everyman | Relatable, down-to-earth | IKEA |
Align archetype to customer personality; strengthens storytelling.
| Element | Definition | Example | |---------|------------|---------| | Voice | Brand personality; consistent across touchpoints | Professional / Friendly / Technical / Bold | | Tone | How you say it; adapts to context | Confident but not arrogant; helpful; concise | | Avoid | Buzzwords, terms to never use | "streamline," "revolutionize," "synergy" | | Preferred | Terms to use consistently | "audit" not "analysis"; "customer" not "user" |
Product marketing context Section 8: Document voice, tone, avoid, preferred terms. See project-context template.
| Element | Strategy | Implementation | |---------|----------|-----------------| | Colors | Primary, secondary, CTA; industry mapping | brand-visual-generator | | Typography | Display + body; hierarchy; pairing | brand-visual-generator | | Logo | Variants, clear space, minimum size | logo-generator | | Imagery | Tone, subject matter, visual mood | Brand guidelines | | Consistency | Same identity across web, social, product | All touchpoints |
For full visual specs (fonts, HEX, spacing), see brand-visual-generator. For logo placement and implementation, see logo-generator.
Single source of truth. Include:
When the user needs actionable specs (not only strategy)—for web, slides, or print—produce a token table the team can paste into a design system, media kit, or slide master. Align with brand-visual-generator for full web/CSS detail.
| Token category | What to document | Example fields |
|----------------|------------------|----------------|
| Colors | Named roles + values for light/dark if applicable | Primary #______, text primary #______, background #______, accent 1–3, CTA, border, error/success |
| Typography | Family, weight, size scale, line-height | Display / H1–H3 / body / caption; web-safe or system fallbacks |
| Spacing | Base unit and scale | e.g. 8px base; section gaps; logo clear space in em or px |
| Non-text accents | Charts, shapes, dividers | Rotate accent colors; avoid arbitrary one-off hues outside palette |
Applying tokens across surfaces
If the user pastes an existing brand PDF or bullet list, extract and normalize into this token table before suggesting implementation.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
testing
When the user wants to add or optimize Open Graph metadata for social sharing. Also use when the user mentions "Open Graph," "og:tags," "og:title," "og:image," "og:description," "Facebook preview," "LinkedIn preview," or "social share preview." For X (Twitter) link previews, use twitter-cards. For SERP title/description, use title-tag and meta-description.
tools
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
development
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.