Produce a graphic-design brief for a single visual asset — social posts, thumbnails, banners, OOH, OG cards, hero illustrations. Pulls brand tokens, generates concepts, writes platform-aware specs + image-gen prompt or designer-handoff spec. Does NOT render — rendering is downstream. Not for brand identity (use create-brand), whole-page redesigns (use brief-landing-page), or the copy that goes IN the asset (use write-copy).
설치
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Produce a graphic-design brief for a single visual asset — social posts, thumbnails, banners, OOH, OG cards, hero illustrations. Pulls brand tokens, generates concepts, writes platform-aware specs + image-gen prompt or designer-handoff spec. Does NOT render — rendering is downstream. Not for brand identity (use create-brand), whole-page redesigns (use brief-landing-page), or the copy that goes IN the asset (use write-copy).
argument-hint
[asset description, e.g. 'instagram carousel about pricing tiers']
allowed-tools
Read Edit Grep Glob Bash WebSearch WebFetch
metadata
{"version":"1.0.1","budget":"standard","estimated-cost":"$1-2","status":"done","notes":"Re-scoped from design-create (brief-only, no rendering). platform-modules.md is fully populated — all 18 modules (tranche 1 core-digital + tranche 2 paid-ad-chrome + physical: linkedin-event-banner, facebook-feed/story-ad, youtube-banner, email-hero, ooh-billboard, transit-poster, print-magazine-spread) carry practitioner-grade specs. Volatile platform fields (ad-chrome geometry, file caps) carry [verify YYYY-MM] flags and per-vendor physical specs instruct the operator to confirm the vendor/publication media kit — verified against current sources where confirmable, never fabricated. Re-verify [verify] fields on a cadence (Meta/LinkedIn ad-chrome drifts fastest)."}
Design Brief — Orchestrator
Produce a graphic-design brief for a single visual asset — social posts, thumbnails, banners, OG cards, hero illustrations, OOH, ad creative. Emits an image-gen prompt or designer-handoff spec; does NOT render (not for user flow / wireframe — use map-user-flow). Capability metadata: routing.yaml. Agents + 4 downstream routes + 8-dim rubric: references/agent-manifest.md. Methodology: references/playbook.md.
Core question: Could a designer or image-gen tool execute this asset on-brand and on-platform without follow-up questions?
Critical Gates — load first
Do NOT render. Brief only — spec + reference direction + image-gen prompt. Rendering happens downstream.
Do NOT proceed without brand anchors. Missing brand/BRAND.md or brand/DESIGN.md → NEEDS_CONTEXT, recommend create-brand. Hard gate fires BEFORE Cold Start (survives --fast).
Do NOT invent tokens, fonts, or motion specs. Every visual decision traces to DESIGN.md. Gap → flag, don't guess.
Reference realized surfaces, not just tokens. Before writing reference direction, pull ≥1 realized surface (live page screenshot · shipped HTML · approved exploration · existing exemplar) and design the concept against it — tokens are the floor, the realized surface is the taste. No surface available → record the explicit token-only fallback line. Silent token-only design fails the rubric. Contract: references/_shared/realized-surface-grounding.md.
Do NOT use stock-AI defaults. No purple-blue gradients, centered-on-white, faux-3D bevels, glassmorphism — unless DESIGN.md specifies. 13-pattern detector scores explicitly.
Do NOT skip the brief approval gate. Brief is a candidate, not a delivery — user reviews before rendering.
Platform spec mandatory. Every brief includes aspect ratio, safe zones, mobile readability, file format, file-size cap.
DONE_WITH_CONCERNS — approved with flagged issues in frontmatter (e.g. a brief drew a [verify]-flagged platform field that wasn't confirmed against a current source, or a per-vendor physical spec the operator hasn't confirmed).
BLOCKED — user rejected at a gate, or external dependency missing.
NEEDS_CONTEXT — BRAND.md or DESIGN.md missing.
Execution
At brief-binding, bind the image target tool (recorded as target_tool frontmatter on image-gen routes) — inherit tool_targets or ask once per references/_shared/tool-target.md; the image-gen prompt tunes to it, tool-agnostic stays the default.
Offer the registry-gated fork (category image) — Brief-only: hand the approved brief to the renderer named by downstream_route (→ produce-asset → evaluate-asset); Assisted/Direct: render via a verified engine, you approve at the gate. See execution-fork.md; record execution_mode. On render dissatisfaction, re-invoke — pipeline lifecycle overwrites. When picking Assisted/Direct, batch-check the render surface first (all blockers at once + named fallback) — see capability-preflight.md.
