characterlisted

# /character — persistent, consistent characters A character is a small folder of reference images plus a locked description. Made once (~$0.06–0.12), reused forever: every future generation that names the character passes its real reference files and its exact description, which is what keeps faces, outfits, and proportions stable across an entire project. Characters live in `<workspace>/refs/characters/<slug>/`: ``` refs/characters/rex/ ├── character.json the registry entry (below) ├── sheet_turnaround.png front / side / back / three-quarter grid └── sheet_expressions.png optional second sheet ``` `character.json`: ```json { "schema": 1, "name": "Rex", "slug": "rex", "token_description": "Rex, a stocky red panda mascot with a cream belly, round amber eyes, wearing a tiny blue engineer's cap", "sheets": ["sheet_turnaround.png"], "source": "generated", "created": "2026-08-04T00:00:00Z", "notes": "brand mascot for NoMoreHigs demos" } ``` The `token_description` is the consistency contract: it is reused **verbatim, word for word** in every prompt that features the character. Never paraphrase it ("amber eyes" must not become "orange eyes"). ## Creating a character 1. **Establish the design** in conversation: species/person type, build, face, outfit, palette, vibe. Distill it into one tight token_description (≤ 40 words, concrete nouns, stable adjectives). 2. **Generate the turnaround sheet** through the generate pipeline (quote → gate → run