← Files DesignlyARCHIVED FILE
shared/references/brand-intelligence.md
2.23 KB · Sep 30, 2026 · 23:14 UTC
# Brand Intelligence Read supplied brand evidence before creative invention ## Extract brand invariants Identify what should remain stable across executions - logo geometry and approved variants - core colors - type character - distinctive shapes or motifs - photography treatment - product presentation - spacing/density character - composition habits - tone and cultural behavior ## Extract degrees of freedom Identify what the brand changes comfortably - crop - environment - accent color - type scale - illustration/photography mix - campaign motif - layout density This prevents false consistency where every asset becomes the same template ## Evidence labels Every decision is one of ### BRAND RULE Explicitly stated in guidelines or supplied as a hard instruction ### OBSERVED PATTERN Repeated across supplied examples but not stated as formal policy ### INFERRED CHOICE A recommendation made for the current job Never upgrade an observation or inference into an official rule ## Distinctive asset test Ask what remains recognizably specific when the logo is temporarily hidden Potential distinctive assets include - palette relationships - type proportions - image behavior - crop - framing - shape language - recurring motif - product staging - whitespace behavior Do not force all of them into every asset Use enough to create continuity without visual repetition ## Logo handling Preserve - aspect ratio - orientation - approved color variant - clear-space behavior when known - readable size - clean edges Do not create fake alternate marks or turn the logo into texture, reflection, embossing, object material, or decorative pattern without explicit permission ## Product brand handling Lock distinctive geometry, label, color, finish, cap/closure, logo placement, and pack count when a supplied packshot is evidence Do not let generative styling redesign the product ## Sparse evidence If only a logo is supplied, treat only logo facts as known Build the rest as an explicitly inferred visual direction ## Conflict handling When official supplied rules conflict, follow the more specific rule for the current asset if scope is clear If scope cannot be resolved and the choice materially changes the output, ask one targeted question
SHA-256: b942a534975ae948258d328e863be60b8ae97b9c52fe40ca3a1755a289fe10eb