Playbook and Three.js code kit for detailed dioramas: classic pixel art, stroked toon or pixel + stroke; two intake gates for look and model sourcing; free orbit, palette snap and ink; animated toy-scale cast; per-entity frame QA.
Reference scope
Load only when routed by SKILL.md. The core profile, scale, construction-first and evidence rules take precedence over legacy calibration counts, numerical examples or workflow order here. Subject-specific examples are recipes, not universal requirements. Paths beginning templates/, verify/ or media/ are relative to the skill root.
When to Use
- Educational "how does this work?" mechanisms, cutaways and step-through causal explanations; use the Educational Mechanism Profile, not cast quotas.
- "Make a small diorama / miniature scene / pixel scene of X"
- A clip or still shows a flat cut-out scene with chunky pixels and little people, and the ask is to match that look
- An existing 3D scene needs the pixel-art presentation (palette, dither, ink, reset hero angle plus orbit) rather than a smooth render
- The figures need believable motion: walking, climbing into a car, sitting, swimming, diving, and it has to survive close inspection
- The ask is for a staged diorama, not a model: several systems, a cast, a goal or boss, and a loop that can be frozen at any second
- The user gives only one line ("a bakery at closing", "a lighthouse under siege"); this skill is designed to turn that into a complete commission without an interview
Don't use for photoreal scenes or full-resolution photographic product renders. Every scene MUST support free user orbit by default, including pixel, stroked-toon and pixel-stroke. No separate orbit consent exists. Keep a deterministic hero angle for QA/reset, never auto-spin.