scenario-identity-library
Scenario Identity Library
Overview
A game or brand runs on named identities: characters and props that must stay recognizable in every image that ships. This skill runs that lifecycle end to end: interview a brief, generate and gate a hero image, file approved shots in a named collection, assemble a sheet, and pull the library back out for new images. The per-image mechanics live in siblings and are not repeated here: connection and the core loop in scenario, holding a look with references in scenario-consistency, pass/fail verdicts in scenario-quality-gate. 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
| Stage | Mechanism | Rule |
|---|---|---|
| Brief | interview, written as the must-not-change enumeration | before anything generates |
| Anchor | hero generation, gated to pass | uploaded art skips generation |
| Library | collection named character: <name> or props: <name> |
gated images only |
| Sheet | Grid Maker assembly of approved shots | rebuild after membership changes |
| Reuse | collections_list prefix match, members via search, references per scenario-consistency |
any later session |
From interview to anchor
Interview before generating: the answers become the baseline enumeration every later image restates (scenario-consistency), so a gap here becomes drift later. Ask what it is, silhouette and proportions, palette by name or hex, two or three signature details that make it recognizable (the cracked headlamp, the brass buckle), the rendering style, and which views the set needs. Non-interactive runs take what the task supplies and flag the rest. A user who already has art skips generation: their drawing or photo is the uploaded anchor, per scenario-consistency.