shared/references/design-preflight.md

# Design Preflight

Run this before image generation or final layout execution

Do not use preflight to make every design conventional

Use it to catch unresolved decisions that a generator would turn into attractive noise

## Gate A: Communication

Pass only when

- one primary message exists
- supporting information is subordinate
- desired action is clear when the asset needs an action
- the visual idea can be described in one plain sentence
- the idea still exists after style adjectives are removed

## Gate B: Hierarchy

Pass only when

- one dominant focal event is defined
- secondary and tertiary roles are clear
- contrast is intentionally distributed
- hero, copy, logo, and CTA are not all competing at maximum weight

## Gate C: Structure

Pass only when

- a grid or explicit alignment-anchor logic exists
- related elements are grouped intentionally
- the eye path matches the reading direction and message order
- negative space has a job
- crop and edge behavior are intentional
- text and hero zones do not collide

## Gate D: Typography

When text applies, pass only when

- exact copy is locked
- type roles are defined
- line breaks serve meaning
- alignment matches the composition and language
- Arabic shaping and direction are treated natively
- text/background contrast has a verification plan

## Gate E: Color

Pass only when

- color roles are clear
- value hierarchy survives without hue
- accents are limited enough to remain accents
- brand color is used intentionally
- color is not the sole carrier of critical meaning

## Gate F: Brand and product

When supplied assets exist, pass only when

- official rules are separated from inference
- logo and product geometry are locked
- treatment does not distort the supplied identity
- brand specificity extends beyond logo placement when enough evidence exists

## Gate G: Physical coherence

For photographic, product, or manipulation work, pass only when the plan has a coherent

- camera relationship
- perspective
- key light
- contact behavior
- cast shadow
- reflection/material behavior
- depth model

## Gate H: Anti-slop

Pass only when

- effects have jobs
- style families are controlled
- decorative UI and microcopy are justified or absent
- concept survives effect subtraction
- the visual is not relying on generic category shorthand

## Exception rule

A heuristic may be broken when the Art Direction Spec records

- which heuristic is being broken
- why
- what communication benefit the exception creates
- what check will confirm the exception still reads clearly

Hard gates cannot be waived merely for aesthetics