7517
Cd
clanker-and-the-dev / files
clanker-and-the-dev / comic / style-guide.md
3.8 KB
1# Clanker and the Dev Comic Style Guide 2 3This guide defines the visual identity and prompt vocabulary for the SDXL image-generation pipeline. 4 5## Overall look 6 7- Format: generated PNG comic panels composed into one panels-only `strip.png`. 8- Mood: 80s terminal, hacker green on black, sparse and readable. 9- Lines: clean neon line-art inspired by `art-reference/`; readable over detailed. The generator post-processes SDXL output back into crisp terminal strokes. 10- Shapes: simple comic geometry and characters, no photorealism, no UI chrome. 11- Background: black or near-black; avoid CRT scanlines, panels, windows, headers, footers, and texture unless explicitly needed. 12- Panel borders: simple green comic frames added by the compositor. 13- Characters must stay visually consistent between strips; auto ControlNet guides are built from `art-reference/` character sprites to enforce this. 14- Dialogue, captions, code snippets, and panel borders are overlaid after image generation. 15 16## Characters 17 18### Dev 19 20A human software engineer drawn as a refined terminal-style stick figure / simple comic character. 21 22Persistent traits: 23 24- Round head. 25- Simple rectangular glasses. 26- Minimal torso and limbs. 27- Usually near a laptop or terminal when coding. 28- Expressive body posture does most of the acting. 29- Drawn in neon green / black terminal style, not photorealistic. 30 31Useful acting words: 32 33- neutral 34- curious 35- thinking 36- excited 37- overwhelmed 38- typing 39- resurrected-typing 40- collapsed 41- dead 42- caffeinated 43 44### Clanker 45 46An AI-powered robot assistant drawn with simple geometric shapes matching the reference sheets. 47 48Persistent traits: 49 50- Boxy robot head with screen eyes. 51- Antenna on top. 52- Rectangular torso. 53- Thin segmented arms and claw hands. 54- More machine than humanoid, but readable/emotive. 55- Drawn in neon green / black terminal style, not photorealistic. 56 57Useful acting words: 58 59- neutral 60- helpful 61- confident 62- watching 63- thinking 64- overclocked 65- concerned 66- error 67- celebratory 68- sleeping 69 70## Effects and props 71 72Use effects sparingly in `artPrompt`: 73 74- terminal cursor line (subtle, not blurry) 75- sparks 76- smoke 77- sweat/panic marks 78- speed lines 79- boot-up cursor 80- laptop as a prop 81- code/output text via `terminalLines`, not a rendered app window 82- token counter / progress meter as a visual prop only 83 84Do not ask the model to render readable text in props. Put readable text in `terminalLines`, `caption`, or `dialogue`. 85 86## Composition guidance 87 88Each panel prompt should usually include: 89 90- where Dev is positioned 91- where Clanker is positioned 92- the main prop, usually a laptop or terminal 93- the emotion/acting of each character 94- empty dark space near the top for speech bubbles 95- black/neon green terminal mood 96 97Example: 98 99```txt 100Dev on the left slumps over a terminal laptop, Clanker on the right stands confidently with one claw raised, pure black sparse background, empty dark upper area for speech bubbles. 101``` 102 103## Text rules 104 105Stable Diffusion should not draw readable text. 106 107The compositor adds: 108 109- speech bubbles 110- captions 111- code/output text 112- simple panel borders 113 114It does not add panel numbers, title cards, headers, footers, credits, or branding inside the PNG. Those belong in Jekyll HTML/CSS. 115 116Keep dialogue short. Up to three dialogue/caption items per panel works best. 117 118## Generation rules for Pi / agents 119 120When generating a comic spec: 121 1221. Output valid JSON only into `comic/specs/<slug>.json`. 1232. Use the image-generation schema in `comic/schema.md`. 1243. Do not write SVG. 1254. Do not create inline-SVG markdown posts. 1265. Do not use the old deterministic renderer or `job.sh`. 1276. If a seed or joke has numbered beats, usually map one beat to one panel. 1287. Put all readable comic lettering in `dialogue`, `caption`, or `terminalLines`, not in `artPrompt`. 1298. Do not request title cards, headers, footers, app/browser chrome, watermarks, or metadata in generated art.