logo-design

name	logo-design
description	Generate logo variants for a brand, producing multiple production-grade marks across different architectures (wordmark, lockup, symbol-only, letterform-as-symbol, monogram) with rationale, application specs, and decision-ready presentation. Distinct from `brand-identity`, which produces the complete system (logo plus color, type, voice, applications). Goes deep on the logo specifically: typographic register, symbol approach, application-context discipline (16px favicon, embroidery, signage, motion), and production specs (SVG-ready, single-color, reverse). Triggers on logo design, design a logo, wordmark, monogram, lockup, mark variants, logo iterations, redesign or refine the logo, logo refresh, letterform-as-symbol, and exploring mark variants for an established brand. Does NOT fire for full brand identity (use `brand-identity`), positioning or strategy (use `brand-discovery`), project-wide creative direction (use `creative-direction`), or one-off illustration.
category	brand
catalog_summary	Logo variants across architectures (wordmark, lockup, monogram, letterform-as-symbol), with rationale and application specs
display_order	5

Logo Design

A logo is a system of marks, not a single drawing. This skill produces multiple production-grade variants exploring different architectural approaches, each with rationale, application specs, and a clear position on what it signals and rejects.

The output is decision material, not a finished logo. The brand owner selects from the variants and the skill produces production refinement on the chosen direction.

---

When to use

• The brand has a name and tonal direction; the deliverable is logo work specifically
• Generating 6 to 12 variants for client review and selection
• Refining a wordmark to production: kerning, optical adjustments, weight selection
• Exploring symbol options to pair with an existing wordmark
• Designing a monogram from a longer name for use in constrained contexts
• Adapting an existing logo across application contexts (small-size, signage, motion, embroidery)
• The brand owner has reviewed a first round and wants iteration on a specific direction

When NOT to use

• Use brand-identity instead when the deliverable is the complete identity system (logo plus color plus type plus voice plus applications). This skill is the logo-specific layer; brand-identity is the system layer.
• Use brand-discovery for brand positioning, audience, and voice work. A logo without strategy is a drawing.
• Use creative-direction for project-wide aesthetic direction. Creative direction calibrates many decisions; logo design produces specific marks.
• One-off illustration, icon, or pictogram work
• Designing brand patterns, textures, or supporting graphics
• Pure typographic exploration unrelated to a brand name

---

Required inputs

• Brand name. Exact spelling. Capitalization and punctuation preferences if any. Whether the name has a category descriptor that travels with it (e.g., "Atlas Coffee" vs just "Atlas").
• Industry or category. Legal firm, consumer goods, B2B SaaS, hospitality, etc. Category implies defaults that can be honored or broken.
• Audience. Who sees the logo, where, in what state of mind. The audience-side perception drives selection more than the founder-side aesthetic.
• Tonal direction. Where on the formal-to-casual axis. Where on the restrained-to-expressive axis. Where on the heritage-to-modern axis.
• Application contexts. Common set: web header, mobile app icon (28px), favicon (16 to 32px), business card, letterhead, email signature, social profile picture, signage (large format), embroidery patch (1.5 inch), single-color print, video motion lockup, merch (apparel, hats, totes).
• Reference logos liked, with a sentence each on what specifically resonates. The reference clarifies which architecture and register fit better than abstract description does.
• Reference logos disliked, with a sentence on what to avoid. Negative space sharpens positive selection.
• Hard constraints. Must include element X. Must avoid color Y due to industry conventions. Must reproduce in single color. Must work as a 16px favicon. Must survive embroidery.
• Optional: existing brand assets if the project is a refresh, not greenfield. Existing wordmark if the work is symbol-only. Existing color palette if it must remain locked.

---

The framework: 5 considerations for logo design

A logo decision sits at the intersection of five considerations. Each one filters subsequent choices.

1. Mark architecture

What IS the logo, structurally?

Architectures:

• Wordmark only. The logo is the brand name set in a chosen typeface, possibly with custom letterforms. Stripe, Google, Pinterest. The discipline is letter-by-letter, with kerning, optical adjustments, sometimes a single distinguishing custom character. Strongest when the name is distinctive enough to own as type.
• Lockup (wordmark plus symbol). Standard architecture for most brands. The wordmark and symbol are positioned in a fixed relationship. Slack, Airbnb, Asana. Variants: symbol left of wordmark, symbol above wordmark, symbol right (rare). Each lockup may also have a stacked alternate for square contexts.
• Symbol only. The mark is a single symbol with no wordmark. Apple, Twitter, Target. Earned over decades through brand recognition. New brands rarely succeed with symbol-only as the primary mark, though most mature brands eventually develop a symbol-only fallback.
• Letterform-as-symbol. A single letter from the name (often the first) becomes the symbol. Beats by Dre's "b", McDonald's "M", Underscore's "_". Cleanest path to symbol when the wordmark is too long for a tight lockup or when the name has a letter that lends itself to visual play.
• Monogram. Multiple letters combined as a symbol. CN (Chanel), GG (Gucci), HBO, MN (a hypothetical Morgan Northrop monogram for an institutional financial firm). Common in legal, financial, hospitality, and heritage brands. Can read as initials or as ligature.

How to choose: What does the brand need to do at small sizes? At 16px, most lockups fail. A favicon-grade mark needs either a strong symbol component or a letterform-as-symbol fallback. Lockups also need stacked alternates for square contexts (social profile pictures, app icons). A pure wordmark works only if the brand has another mark that can stand in at small sizes, often a letterform-as-symbol or monogram.

A common production setup is: primary lockup for most contexts, monogram for square contexts, letterform-as-symbol for favicon and embroidery. All three derive from the same wordmark and share visual DNA.

2. Typographic register

If wordmark or lockup, what typographic family carries the type?

Registers:

• Geometric sans. Futura, Avenir, Avenir Next, Cabinet Grotesk, ITC Avant Garde. Built from circles and verticals. Reads modern, considered, often optimistic. Risks reading cold or generic-tech-startup if not warmed up by color, custom letterform, or context.
• Humanist sans. Gill Sans, Optima, Frutiger, Source Sans, Inter at higher optical sizes. Has serif-like calligraphic gestures without serifs. Reads professional but warm. Excellent neutral choice when the category demands restraint with personality.
• Neo-grotesque sans. Helvetica, Inter, Aktiv Grotesk, Söhne, GT America. The modern professional default. Reads competent and contemporary. Risks reading generic if not paired with strong color or symbol.
• Transitional serif. Source Serif, Charter, Lyon, IBM Plex Serif. Modern serifs with high contrast and readability. Reads editorial, considered, intellectual. Good for legal, publishing, financial, editorial brands.
• Old-style serif. Garamond, Caslon, Sabon, Adobe Garamond. Classical serifs with low contrast and warm shapes. Reads heritage, traditional, institutional. Common in academic, legal, financial, and heritage brands.
• Slab serif. Sentinel, Adelle, Roboto Slab, Tisa. Heavy structural serifs. Reads strong, declarative, sometimes journalistic. Common in editorial and publishing.
• Display custom. A custom-drawn or heavily-modified typeface. Reads distinctive but expensive in time. Justified when the brand needs a wordmark no one else has and the budget supports drawing one.

How to choose: What does the brand reject? Most categories have a default register. Legal firms default to old-style or transitional serif. Tech startups default to geometric or neo-grotesque sans. Choosing within the category default reads as competence; choosing outside reads as positioning. A boutique legal firm in geometric sans signals "modern, accessible". A SaaS startup in old-style serif signals "we take ourselves seriously".

3. Symbol approach

If the architecture includes a symbol (lockup, symbol-only, letterform-as-symbol), what KIND of symbol?

Approaches:

• Literal. The symbol depicts the thing the brand name refers to. A mountain peak for an outdoor brand. A rocket for a rocket company. A leaf for a sustainable brand. Fast recognition, low ambiguity. Risks reading as cliche if the depiction is generic. Saved by distinctive execution: the specific peak, drawn with conviction, in the brand's specific visual register.
• Abstract gesture. The symbol suggests a quality without literal depiction. A rising arc for "growth". A pair of opposing forms for "balance". A continuous loop for "integrity". Slower recognition, higher distinctiveness. Risks reading as arbitrary if the gesture is too abstract. Saved by clear formal logic and consistent visual vocabulary.
• Geometric reduction. The symbol is a formal abstraction with no specific referent. A hexagon, a triangle, a stack of horizontal lines, a circle bisected by a vertical. Reads modern and confident. Risks reading as identical to many other geometric-reduction marks. Saved by specific proportions, considered execution, and pairing with a distinctive wordmark.
• Letterform-derived. The symbol is built from the name's letterforms. The "M" of McDonald's, the "b" of Beats, a custom "A" rendered as a mountain peak for a hypothetical Atlas Coffee. Strong wordmark-symbol coherence. Risks reading as wordmark-only if the letterform isn't emphasized enough. Saved by exaggerated character: the letter must read as both the letter AND the visual metaphor.
• Monogram. Multiple initials combined. The symbol IS the initials, often with ligature treatment, tight kerning, or geometric framing (ring, shield, diamond). Common in legal, financial, hospitality. Risks reading as old-fashioned if the type treatment is too conservative. Saved by modern execution within traditional architecture.

How to choose: What does the brand name already do? Descriptive names (Atlas, Forge, Pulse, Anchor) invite literal symbols and letterform-as-symbol approaches. Abstract names (Stripe, Anthropic, Linear) demand abstract or geometric-reduction symbols. Heritage names (a founder's surname, a place name) often use monograms. The wrong approach disconnects symbol from name.

4. Application context discipline

A logo is not a single drawing. It must work in every context the brand touches.

Contexts and their constraints:

• 16px favicon. The most aggressive small-size test. Lockups usually fail here; the symbol or letterform-as-symbol carries. Plan a fallback mark for this context from the start.
• 28px app icon. Slightly more headroom than favicon. Still demands strong silhouette. Often uses the symbol or monogram, not the lockup.
• 1.5 inch embroidery patch. Limits color count (often 4 to 6 max), demands clean shapes without fine detail. Eliminates gradient and photographic elements. Tests the mark's reproducibility in a tactile medium.
• Single-color reproduction. Etching, foil stamp, single-color print, fax. All gradient and color-dependent decisions must collapse cleanly to one color. Test by converting the design to pure black on white.
• Reverse (light on dark). Many marks fail when reversed. Test on the brand's expected dark backgrounds early. Gradient marks particularly struggle here.
• Large-format signage. Requires sharp vector with no rasterization. Tests construction grid quality. Tests whether thin strokes survive scaling.
• Motion lockup. Tests whether the logo has natural entry and exit animation. Wordmarks reveal letter-by-letter; symbols rotate, scale, or assemble from parts.
• Social profile picture (square). Lockups need a stacked alternate or monogram fallback. Symbol-only works natively.
• Apparel embroidery (thread on fabric). Tighter constraints than patch embroidery. Fine letterforms and detail die here. The mark needs a chunky-friendly variant.
• Foil stamp on paper or leather. Single-color, no gradients, requires substantial line weight to survive the impression.

The discipline: Every variant must pass the application-context test before it's a contender. Generate each variant, then mentally test each context. If a variant fails three or more contexts, it's not a primary mark; it might still serve as a secondary or display lockup but it isn't carrying the brand. Build a fallback hierarchy: primary lockup, secondary monogram, favicon-grade letterform-as-symbol.

5. Restraint discipline

Most logo failure happens through over-design. The discipline is subtractive.

Tests:

• Silhouette test. Squint at the logo. If you cannot identify it from silhouette alone (with type stripped), the silhouette is too generic. Apple, Nike, Twitter pass. Most generic SaaS marks fail.
• Distinctiveness test. Search Google Images for "[your category] logo". If your candidate looks identical to three or more existing logos, it's not distinctive enough. Especially watch out for geometric-reduction marks that have already been done a thousand times.
• Sketchability test. A 7-year-old draws the logo from memory after 30 seconds of looking. If they can't, it's too detailed to live in cultural memory.
• Single-color test. Strip all color. Does it still read? If no, color is doing too much work.
• Reproducibility test. Print at 1 inch on a black-and-white printer. Is it still recognizable? If no, the mark won't survive embroidery, foil stamps, or low-resolution applications.
• The two-second test. Show the logo to someone unfamiliar with the brand for two seconds. Ask what they remember. The features they recall are the ones doing real work; the rest is noise.

The discipline doesn't reject all detail. It rejects detail that doesn't earn its place. Every visual element should pass the question "does this read at the smallest application size?".

---

Workflow

1. Gather inputs. Required inputs above. If the user has reference logos, walk through what specifically resonates in each. The references calibrate which architecture and register actually fit.

2. Establish primary architecture. Wordmark-only? Lockup? Letterform-as-symbol? Monogram? This is the foundational decision; everything else flows from it. For most new brands with a distinctive descriptive name, the right architecture is lockup with literal or letterform-derived symbol, plus a monogram fallback for square contexts.

3. Generate typographic explorations. Produce 3 to 4 wordmark-only variants exploring different typographic registers. Each variant should be a complete, kerned, optically-adjusted wordmark. These serve as both standalone candidates and as the foundation for subsequent symbol pairing.

4. Generate symbol explorations (if architecture includes a symbol). For each typographic exploration, generate 1 to 2 symbol pairings using different symbol approaches (literal, abstract gesture, letterform-derived, monogram). The symbol must visually agree with the wordmark's type weight, optical density, and tonal register. A heavy slab wordmark needs a chunky symbol; a hairline geometric wordmark needs a thin symbol.

5. Test each variant against application contexts. For each candidate, walk through 16px favicon, 1.5 inch embroidery, single-color reproduction, square stacked alternate. Eliminate variants that fail more than two contexts. Document which contexts each variant excels in versus needs a fallback for.

6. Pick top candidates for client review. Typically 6 to 12 final variants. Each variant must be visually distinct from the others. Variants that are too similar dilute the review and frustrate the client (they cannot tell why they should pick one over the other).

7. Document each variant. Per-variant: descriptive name (e.g., "01, Light geometric wordmark, Avenir Next"), architecture, typography, symbol approach if applicable, color tokens, application notes, signals (what it communicates), rejects (what it explicitly is NOT).

8. Provide production specs for the top 3 candidates. SVG-ready construction notes, color hex codes (primary plus single-color black plus single-color white plus reverse), sizing guidelines (minimum sizes per medium), motion entry and exit recommendation, embroidery and foil-stamp adaptations.

9. Provide application mockups. Render each top candidate in 3 to 5 representative contexts: web header, business card, favicon at 16 and 32px, embroidery patch, signage. Mockups can be image-generated or schematic. The point is to show the client how the mark lives across contexts, not to deliver finished marketing material.

10. Hand off. Output is decision material. The brand owner selects a direction. The skill (or a follow-up iteration) then produces production refinement on the chosen path: cleaner construction, refined kerning, color system finalization, application library.

---

Failure patterns

• Designing for the founder's taste, not the audience's perception. The founder sees the logo every day; the audience sees it for 3 seconds in a bad mood. The audience-side test wins.
• Skipping the silhouette test. Logos that fail silhouette die at small sizes and in motion. Test early.
• Ignoring small-size legibility. A favicon test at 16px is the single most overlooked discipline. Most lockups fail here. Plan a fallback symbol or letterform-as-symbol mark from the start.
• Trying to depict everything the brand does. Logos can hold one idea, sometimes two. Three is too many. Symbols stuffed with multiple metaphors read as committee work.
• Picking a typeface for trend. Monoline geometric sans (Cabinet Grotesk, GT Pressura) read as "2024 startup" in a way that ages quickly. Pick for category-fit and longevity, not for design-trend currency.
• Over-customizing letterforms. Custom letterforms should solve a specific problem (a flat-bottomed "g" that conflicts with a descender, an "a" that breaks the rhythm, an "A" that becomes a mountain peak). Custom for novelty's sake reads as gimmicky.
• Lockups that fall apart at certain sizes. Test the lockup at 200%, 100%, 50%, 25%. If proportions break or elements clash at any size, the lockup needs adjustment.
• Color-dependent marks. A logo that requires color to be recognizable cannot survive single-color reproduction. Color is the last layer, not the foundation.
• Letterform-as-symbol marks that fail the silhouette test for the underlying letter. An "A as mountain peak" must read as a mountain peak AND as the letter A. If it reads as only one or only the other, the metaphor isn't earning its place.
• Reviewing too many similar variants. Showing a client 10 wordmark variants in different geometric sans typefaces dilutes the decision. Show 3 architectures, with 2 to 3 typographic options each. The client can see the architectural choice clearly.
• Skipping the embroidery test. Many brands eventually want a hat or a polo. A logo with fine detail or photographic gradients cannot be embroidered cleanly. Test before client signoff.

---

Output format

Default output is a markdown spec with multiple variants, typically saved as logo-variants.md at the project root or in a design/ subdirectory. The spec is paired with rendered images for each variant, saved alongside (typically in design/logo-variants/).

Per-variant structure:

1. Variant name. Descriptive identifier with index (e.g., "01, Light geometric wordmark, Avenir Next" or "07, Mountain peak A lockup, IBM Plex Sans").
2. Architecture. Wordmark / Lockup / Symbol / Letterform-as-symbol / Monogram.
3. Typography. Specific typeface name and weight. Custom letterform notes if any. Tracking and kerning treatments.
4. Symbol description (if applicable). Approach (literal / abstract gesture / geometric reduction / letterform-derived / monogram) and visual description. Construction grid notes if relevant.
5. Color tokens. Hex codes for primary palette, single-color black version, single-color white version, reverse-on-dark treatment.
6. Application notes. Which contexts the variant excels in (e.g., "strong at large signage and letterhead") and which contexts need a fallback mark (e.g., "favicon falls back to letterform-as-symbol at 16px"). Embroidery adaptation notes if relevant.
7. Signals. What this variant communicates about the brand. The features it foregrounds.
8. Rejects. What this variant explicitly is NOT. The negative space the variant creates.
9. Mockups. Rendered in 3 to 5 application contexts. At minimum: web header, business card, favicon. Bonus: embroidery patch, large-format signage, social profile.

The spec is decision material. The next step after delivery is selection plus production refinement on the chosen direction.

---

Reference files

• references/architectures-explained.md. The 5 mark architectures with examples, when each fits, when each fails, and how to combine them in a primary plus fallback hierarchy.
• references/typographic-registers.md. The typographic registers with named typefaces, category-fit notes, and example brands per register.
• references/symbol-approaches.md. The 5 symbol approaches with pattern examples, calibrating the agent's vocabulary for symbol generation.
• references/application-contexts.md. The contexts every logo must pass, with constraint specs (favicon size, embroidery color count, single-color rules, motion entry recommendations).
• references/category-conventions.md. A survey of common conventions across major brand categories, with defaults that work, conventions worth honoring, conventions worth breaking for positioning, and category-specific application contexts.
• references/example-variant-spec.md. A complete example showing all nine per-variant fields filled in for a representative project.
• references/client-package.md. The package format clients expect at delivery: file format matrix, variant matrix, folder structure, naming convention, documentation layer (usage guide plus brand colors plus license), delivery mechanisms, and the failure patterns that send the client back asking for a missing variant.