Design Brief — Orchestrator

Communication — visual layer. Produces a graphic-design brief for a single visual asset; rendering is downstream.

Core Question: "Could a designer or image-gen tool execute this asset on-brand and on-platform without follow-up questions?"

Critical Gates — Read First

• Do NOT render. This skill produces the brief, not the asset. The brief carries spec + reference direction + image-gen prompt (where applicable). Rendering happens downstream — image-gen (Midjourney / Imagen / DALL·E / Claude Design), vector tooling (Pencil / Figma), or a human designer.
• Do NOT proceed without brand anchors. Missing brand/BRAND.md or brand/DESIGN.md → return NEEDS_CONTEXT, recommend running brand-system first.
• Do NOT invent tokens, fonts, or motion specs. Every visual decision traces to DESIGN.md. If DESIGN.md doesn't cover what's needed (e.g. illustration style), flag it in the brief — don't guess.
• Do NOT use stock-AI defaults. No default purple-blue gradients, centered-isolated-on-white, faux-3D bevels, or glassmorphism unless DESIGN.md specifies. Critic scores generic-AI smell explicitly.
• Do NOT skip the brief approval gate. The brief is a candidate, not a delivery — user reviews before downstream rendering.
• Platform spec is mandatory. Every brief includes aspect ratio, safe zones, mobile readability (type scale, thumb-stop contrast), file format, and file-size limits. See references/platform-modules.md.

Philosophy

A great brief eliminates downstream ambiguity. Render quality is bounded by brief quality — a vague brief produces drift no matter how good the renderer. The brief is the deliverable; every visual decision binds to a brand anchor and a platform constraint.