Brand Style Guide Rules

A style guide that nobody reads produces no consistency, no matter how thorough it is — the binding constraint on a style guide isn't completeness, it's whether someone under deadline pressure will actually open and follow it. Every section below should earn its place by being something people will genuinely reference, not a section that exists because guides "are supposed to have one."

Logo usage rules

• State the exact minimum clear space around the logo as a multiple of a fixed unit within the mark itself (e.g., "clear space equals the height of the icon on all sides"), not an arbitrary pixel value that breaks when the logo is resized.
• Specify the absolute minimum size for digital and print use, tied to the smallest context the logo must survive (typically a favicon or business-card scale) — state it as a real measurement, not "as small as legible."
• List forbidden distortions explicitly and show each one visually if possible: stretching, skewing, rotating, recoloring outside the approved palette, adding effects (drop shadows, outlines, gradients) not in the original files, placing on a busy or low-contrast background.
• Show the approved lockup variants (horizontal, stacked, icon-only) and state which context each is for — don't leave selection between variants to guesswork.

Color palette with codes and ratios

• List every brand color with its exact values in every format actually needed (HEX for digital, RGB for screen, CMYK and/or Pantone for print) — a color defined only visually ("brand blue") will drift across tools and printers.
• State the usage ratio for primary vs. secondary vs. accent colors (a common default is roughly 60% dominant/neutral, 30% secondary, 10% accent) so a page doesn't end up saturated with the accent color meant for small emphasis moments.
• Name each color by its brand role ("Primary," "Accent," "Surface"), not just its hex or a generic color name — this is what lets the guide's typography and component rules reference colors without ambiguity as the palette evolves.
• Include any reserved semantic colors (error red, success green) explicitly marked as reserved for those states only, so they don't get pulled into general decorative use and lose their signal value.

Typography hierarchy

• Define each type level (display, heading, subheading, body, caption) with its typeface, weight, size, and line-height — not just "use this font," which leaves every actual sizing decision unresolved.
• State the approved font fallback stack for contexts where the primary typeface can't be embedded (email, some third-party platforms) so brand consistency degrades gracefully instead of falling back to whatever default the platform picks.
• Show one worked example of the hierarchy applied to a real content block (a sample heading + subheading + body paragraph) rather than only listing specs in isolation — a live example resolves ambiguity a spec sheet alone can't.

Voice summary

• Include a short voice section (a few bullet points, not a full separate document) that summarizes tone in the same contrast-pair format useful for visual attributes ("confident, not arrogant"; "clear, not clinical") with one example sentence per pair.
• Link out to a full voice-and-tone or messaging guide if one exists rather than duplicating it — the style guide's job is visual consistency; a full copywriting guide belongs in its own document, cross-referenced, not copy-pasted in.

Do/don't examples

• Pair every major rule (logo clear space, color ratio, type hierarchy) with a visual do/don't example side by side — an abstract rule ("maintain clear space") is far more likely to be followed correctly when shown next to a violation than when described in text alone.
• Choose don't examples that reflect realistic mistakes people actually make (logo too small, low contrast, wrong lockup for context), not exaggerated strawman errors nobody would actually commit.

Keeping it usable

• Cap the guide at a length someone can actually skim in one sitting — a 60-page brand bible gets opened once and never again; a tight, well-organized 8–15 page guide gets referenced regularly.
• Put the most frequently needed items (logo files, primary hex codes, minimum size) on the first page or in a single quick-reference section, so a person in a hurry doesn't have to read the whole document to get the one fact they need.
• Version and date the guide, and note what changed since the last version at the top — a guide with no version history creates confusion about whether a downloaded copy is still current.