Branding·Updated April 30, 2026

Logo System Spec Writer

Turn a chosen logo direction into production-ready logo system specs: lockups, spacing, sizing, color, and usage rules.

Use Case

Documenting a selected logo concept into enforceable brand rules for teams and implementation.

Prompt

Act as a lead brand designer creating a production logo specification.

I have a chosen logo direction and need a full logo system spec.

Brand + logo inputs:
- Brand name: [name]
- Chosen direction summary: [short description]
- Logo type: [wordmark / symbol / combination mark]
- Core geometry traits: [e.g., rounded, geometric, high contrast]
- Primary colors: [hex values]
- Background contexts: [light, dark, photography, gradient]
- Primary channels: [web app, mobile app icon, social, slides, docs]

Generate a complete logo system with:
1. Core Marks
   - Primary lockup
   - Secondary lockup
   - Icon-only mark
   - Monochrome versions
2. Clear Space and Sizing
   - Clear-space formula
   - Minimum size rules (digital + print)
3. Color Rules
   - Approved colorways
   - Contrast requirements
   - Do/Don't usage on backgrounds
4. Responsive Use
   - When to use full lockup vs icon-only
   - Small-screen and favicon guidance
5. File/Export Requirements
   - SVG, PDF, PNG sizes
   - Naming conventions
6. Misuse Examples
   - Stretching, recoloring, effects, crowding, low-contrast misuse
7. Implementation Checklist
   - Website header
   - App icon
   - Social avatar
   - Brand deck

Output in a practical spec format that can be pasted into brand guidelines.

How to use

1Paste your finalized logo direction and color values before running the prompt.
2Request channel-specific overrides if your brand appears in many contexts (product UI, social, print).
3Copy the output into your brand guidelines and convert key rules into design QA checklists.

Pro Tips

• Ask for minimum-size recommendations with exact pixel values for app and favicon contexts.
• Add accessibility constraints to improve contrast and legibility across dark/light surfaces.
• Use this after concept selection, not before, to avoid over-specifying too early.