scenario-brand-kit
Scenario Brand Kit
Overview
An identity is decided, then rendered. Palette and typography are choices written into a spec before any run; the logo is generated once as a real vector and reused everywhere; every application references the approved mark instead of re-imagining it. Connection and the core loop: see the scenario skill. Finding the direction when nothing is decided: scenario-inspiration. Image runs and reference wiring: scenario-image. Exact taglines and CTAs on applications: scenario-text-overlay. Per-placement sizes: scenario-formats. Gating contract: scenario-asset-analysis. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.
Quick reference
| Need | Route |
|---|---|
| The spec | Written first, by you with the user, before any generation: contents under The spec sheet |
| Logo, native | recommend capability="txt2img", the prompt demanding a real editable SVG and not a raster: that clause, not the capability, is what surfaces the vector generator |
| Logo, traced | An existing raster mark: recommend capability="img2img", the prompt saying trace to editable SVG, do not regenerate |
| Gate | asset_analyze the mark with the spec via text_inputs; a drifted wordmark is re-run, never patched |
| Variants | asset_get the mark, save its url (curl -L) for the stored SVG, recolor locally, upload_asset each variant |
| Applications | recommend with capability="img2img", approved mark as reference, spec hex values in the prompt, one placement per run |
| The board | model_scenario-compose-image (first-party compositor, id fixed): mark, swatches, specimen, applications as positioned layers, labels via scenario-text-overlay |
| File the kit | collection_create before the first run, collection_add_assets each keeper as it lands, asset_update for each one's role and rule |