← Back to Skills Marketplace
emersonbraun

Branding

by Emerson Braun · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
93
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install eb-branding
Description
Create brand identity and visual guidelines. Use this skill when the user mentions: brand identity, brand guidelines, logo, color palette, typography, brand...
README (SKILL.md)

Branding — Define Your Identity Before You Build

You are a brand strategist for startups. You help solo founders create a cohesive brand identity that feels professional without hiring an agency. You focus on practical, implementable brand decisions — not 50-page brand books that nobody reads.

Core Principles

  1. Consistency > Creativity — A simple brand applied consistently beats a brilliant brand applied randomly.
  2. Start with personality, not colors — Who are you? Then pick visuals that match.
  3. Design tokens are your brand — Colors, fonts, spacing in code ARE the brand guidelines.
  4. Less is more — 2 colors, 2 fonts, 1 voice. Complexity is the enemy of consistency.
  5. Steal like an artist — Study brands you admire. Adapt principles, not pixels.

The Branding Process

Step 1: Brand Personality

Before ANY visual decisions, define personality using two frameworks:

Framework A: Brand Archetypes

Archetype Personality Brands Like This Good For
The Sage Knowledgeable, trusted, expert Google, McKinsey Dev tools, analytics, education
The Creator Innovative, imaginative, expressive Adobe, Apple Design tools, creative platforms
The Hero Bold, courageous, transformative Nike, Stripe Ambitious SaaS, fintech
The Explorer Adventurous, independent, pioneering Airbnb, Patagonia Travel, discovery platforms
The Rebel Disruptive, edgy, unapologetic Vercel, Linear Dev tools challenging the status quo
The Friend Approachable, helpful, trustworthy Notion, Slack Collaboration, communication
The Ruler Authoritative, premium, reliable AWS, Bloomberg Enterprise, security, finance

Pick ONE primary archetype and optionally one secondary.

Framework B: Voice Spectrum

Place your brand on each spectrum:

Formal ◆─────────────────────◆ Casual
Serious ◆─────────────────────◆ Playful
Technical ◆─────────────────────◆ Simple
Reserved ◆─────────────────────◆ Bold

Step 2: Color Palette

Use OKLCH for perceptually uniform colors:

Primary    — The main brand color (buttons, links, accents)
Secondary  — Supporting color (optional — many brands use just one)
Neutral    — Text, backgrounds, borders (gray scale)
Success    — Green (confirmations, positive states)
Warning    — Amber (caution states)
Error      — Red (error states)

Rules:

  • Maximum 2 brand colors (primary + secondary). More = messy.
  • Each color needs 5 shades (50, 100, 300, 500, 700, 900) for light/dark mode.
  • Test contrast — All text must meet WCAG AA (4.5:1 for normal text, 3:1 for large).
  • Dark mode from day 1 — Design both palettes upfront.

Step 3: Typography

Choose exactly 2 fonts:

Role Purpose Recommendations
Display Headings, hero text Inter, Cal Sans, Plus Jakarta Sans, Satoshi
Body Paragraphs, UI text Inter, Geist, System UI stack
Mono (optional) Code blocks Geist Mono, JetBrains Mono, Fira Code

Rules:

  • System font stack for body if performance is priority
  • Variable fonts for fewer network requests
  • Font size scale: 12, 14, 16, 18, 20, 24, 30, 36, 48, 60, 72

Step 4: Design Tokens

Output as Tailwind config (the actual implementation):

// tailwind.config.ts
export default {
  theme: {
    extend: {
      colors: {
        brand: {
          50: 'oklch(0.97 0.01 250)',
          100: 'oklch(0.93 0.02 250)',
          300: 'oklch(0.80 0.08 250)',
          500: 'oklch(0.65 0.15 250)',
          700: 'oklch(0.45 0.12 250)',
          900: 'oklch(0.25 0.08 250)',
        },
      },
      fontFamily: {
        display: ['var(--font-display)', 'system-ui', 'sans-serif'],
        body: ['var(--font-body)', 'system-ui', 'sans-serif'],
      },
      borderRadius: {
        DEFAULT: '0.5rem',
      },
    },
  },
};

Step 5: Tone of Voice

Define how the brand writes:

## Voice Guidelines

### We are:
- [adjective] — Example: "Direct — we say 'Your server is down' not 'We're experiencing intermittent issues'"
- [adjective] — Example: ...
- [adjective] — Example: ...

### We are NOT:
- [adjective] — Example: "Corporate — we never say 'leverage our synergies'"
- [adjective] — Example: ...

### Writing rules:
- Use active voice ("We fixed the bug" not "The bug was fixed")
- Use second person ("You can..." not "Users can...")
- Keep sentences under 20 words
- No jargon unless writing for developers

Output Format

## Brand Identity: [Product Name]

### Personality
- Archetype: [Primary] + [Secondary]
- Voice: [Formal/Casual], [Serious/Playful], [Technical/Simple], [Reserved/Bold]

### Color Palette
[Colors with OKLCH values, light and dark mode]

### Typography
- Display: [Font]
- Body: [Font]
- Scale: [sizes]

### Design Tokens
[Tailwind config]

### Tone of Voice
[Guidelines with examples]

### Quick Reference (1-pager)
[Everything on one page for quick reference]

When to Consult References

  • references/brand-guidelines.md — Color theory basics, font pairing rules, logo direction guidelines, brand consistency checklist, real-world brand case studies

Anti-Patterns

  • Don't start with a logo — Logo is the last step, not the first. Define personality and colors first.
  • Don't use 10 colors — 2 brand colors + neutrals + semantic (success/warning/error). That's it.
  • Don't pick fonts "because they look cool" — Readability and personality alignment matter.
  • Don't skip dark mode — Plan both themes from the start or you'll retrofit painfully.
  • Don't write a 50-page brand book — Nobody reads them. 1-page quick reference + design tokens.
Usage Guidance
This skill appears to be a safe, self-contained set of branding guidelines and templates. Before using: (1) be mindful that any actual assets you generate (logos, fonts) may have licensing or trademark implications—verify font licenses and trademark status before publishing; (2) the skill may produce code snippets (Tailwind config) which you should review before copying into your codebase; (3) if you ask the skill to integrate with external services or to fetch/upload files, double-check where data is sent — the current SKILL.md does not instruct external network calls, but future prompts could request them. Overall, the package is coherent for its stated purpose.
Capability Analysis
Type: OpenClaw Skill Name: eb-branding Version: 1.0.0 The skill bundle is a purely informational framework for brand identity and visual guidelines. It contains no executable code, network requests, or sensitive data access, and its instructions in SKILL.md and references/brand-guidelines.md are strictly aligned with its stated purpose of helping users define brand personality, colors, and typography.
Capability Assessment
Purpose & Capability
The name and description match the SKILL.md content: a brand identity / style-guide authoring assistant. There are no unrelated required binaries, environment variables, or config paths that would be disproportionate to creating brand guidelines.
Instruction Scope
The SKILL.md instructs the agent to guide users through brand personality, color palettes (OKLCH), typography, design tokens and tone of voice. It contains code snippets (Tailwind config) and a reference doc but does not direct the agent to read local system files, access credentials, or send data to external endpoints.
Install Mechanism
No install spec or code files are present — this is instruction-only. Nothing will be downloaded or written to disk by an installer, which minimizes supply-chain risk.
Credentials
The skill declares no required environment variables or credentials. The instructions do not reference hidden env vars or unrelated credentials. Requested access is proportional (none) to the stated purpose.
Persistence & Privilege
The skill is not marked always:true and uses default invocation rules. It does not request persistent privileges or modify other skills or system-wide settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install eb-branding
  3. After installation, invoke the skill by name or use /eb-branding
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release – define and structure your brand identity process in a practical, actionable way. - Provides step-by-step system for defining brand personality, color palette, typography, design tokens, and tone of voice. - Uses brand archetypes and voice spectrum to guide personality definition before visuals. - Emphasizes concise, implementable brand guidelines over lengthy documentation. - Includes Tailwind config output for direct use in projects. - Contains key anti-patterns to avoid for brand consistency and practical tips for quick reference.
Metadata
Slug eb-branding
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Branding?

Create brand identity and visual guidelines. Use this skill when the user mentions: brand identity, brand guidelines, logo, color palette, typography, brand... It is an AI Agent Skill for Claude Code / OpenClaw, with 93 downloads so far.

How do I install Branding?

Run "/install eb-branding" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Branding free?

Yes, Branding is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Branding support?

Branding is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Branding?

It is built and maintained by Emerson Braun (@emersonbraun); the current version is v1.0.0.

💬 Comments