К основному содержанию
скилл CX Codex

diorama — скилл для Claude Code: что делает и как установить

Скилл diorama для Claude Code собирает вращаемые 3D-диорамы на Three.js. Регулирует стили графики, кинематику персонажей и отсекает навязчивые обучающие панели в повествовательных сценах.

MIT ★ 702 обновлён 2026-11-16

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add sloemo01/diorama --skill diorama -a claude-code
Открыть на GitHub

Что делает diorama

Скилл задаёт правила построения трёхмерных сцен на Three.js с круговым обзором камеры. Сначала он фиксирует визуальный стиль (pixel, stroked-toon или pixel-stroke), а затем режим подбора моделей (internet-full, hybrid или authored-only). По умолчанию диорама строится как повествовательная сцена: без обучающих панелей V8, шагов урока и плавающих подписей, пока пользователь прямо их не потребует.

Внутрь заложен расчёт занятого пространства и коллизий на базе скриптов templates/action-clearance.mjs и templates/pose-bounds.mjs. Механизм проверяет соприкосновение моделей по фазам движения: подход к креслу, выравнивание, посадка с упором и подъём. Персонажи не проваливаются сквозь сиденья, а подвижные части скелетов тестируются через капсулы коллизий на протяжении всего цикла анимации.

Какие задачи решает

  • построить вращаемую сцену на Three.js в пиксельном или мультяшном стиле
  • предотвратить пересечение геометрии персонажей и сидений при анимации
  • собрать сцену из гибридных источников без лишнего обучающего интерфейса
  • настроить образовательный режим с разбором узлов по прямому запросу

Примеры запросов агенту

  • Собери диораму парка аттракционов в стиле pixel с гибридным импортом моделей
  • Создай интерактивную диораму таверны на Three.js без обучающего интерфейса
  • Объясни устройство колеса обозрения в образовательном режиме с разбором механизмов

Как установить diorama

1Через Skills CLI (Vercel)

npx skills add sloemo01/diorama --skill diorama -a claude-code

2Вручную: положить файлы

~/.claude/skills/diorama/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/diorama/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о diorama

Как установить diorama в Claude Code?

Выполните команду npx skills add sloemo01/diorama --skill diorama -a claude-code в терминале.

Что делает скилл diorama?

Он направляет агента при разработке интерактивных 3D-диорам на Three.js. Скилл определяет рендеринг, структуру сцены, правила импорта ассетов и коллизии анимаций.

Какие визуальные стили поддерживает diorama?

Предусмотрены три стиля: pixel для классического пиксель-арта, stroked-toon с обводкой контуров и совмещённый вариант pixel-stroke.

Исходный текст

SKILL.md · MIT
---
name: diorama
description: "Full long-form guide for detailed rotatable Three.js dioramas. Narrative scenes are scene-first with no educational UI unless requested. Classic pixel, stroked-toon and pixel+stroke are rendering choices, not educational modes. Explanatory commissions use the separate educational contract. Includes composition, cast, animation, craft, sourcing and construction."
version: 5.7.0
author: Nehal Kanak (sloemo)
license: MIT
platforms: [linux, macos, windows]
---

# Diorama

## Current intake contract (5.7.0 — authoritative)

For a new commission, ask **look first, model sourcing second**, using the two gates below. These gates override older three-preset lists, automatic internet-first instructions and one-prompt assumptions elsewhere in this long guide and its references. Do not ask setup questions when merely editing the skill. Explicit answers in the brief skip the corresponding question; existing-project repairs retain recorded choices. An unanswered question is pending, not consent. Rendering and sourcing are independent of narrative/educational purpose.

Three looks are available: `pixel` (Classic Pixel Art; recommended), `stroked-toon`, `pixel-stroke`. Generic “pixel art”, “classic”, “old pixel style” and explicit delegation (“you choose”) resolve to `pixel`. All looks preserve free orbit. An unanswered style gate waits.

Three sourcing modes are available: `internet-full`, `hybrid` (recommended), `authored-only`. Generic “use internet models” resolves to `hybrid` unless the user requests downloaded models throughout. Older `internet-first` records map to `hybrid` on repairs. Sourcing requirements below apply only to modes that acquire external assets; authored-only skips model acquisition, not subject research, quality or geometry/contact checks.

## Profile boundary and retained additions (5.0 — read first)

This is the **restored full-length guide**, not the compact 4.x replacement. Keep its detailed composition, subject recipes, scene furniture, cast, animation, service/queue, vehicle, effects, framing and craft guidance. The following profile/sourcing updates override older wording only where explicitly stated.

### Scene purpose is independent of rendering

**Default `sceneProfile: narrative`.** A place, landscape, amusement park, town, fantasy scene or interactive scene is not an educational mechanism. Pixel, stroked-toon and pixel+stroke choose the renderer, NOT the profile. Asset choice, a working ride or click interactions do not make a scene educational. Choose `educational` when the user asks to explain/teach how something works, its anatomy or causal sequence. If intent is genuinely mixed, ask once; otherwise infer and record it without another forced setup question.

**Narrative has no educational UI by default.** Do not import or instantiate `education-v8.css`, `education-dock.mjs`, an Explore/How it works panel, lesson steps, part picker, explanatory dashboard, floating callout labels or scattered teaching text for an ordinary diorama. This exclusion applies in ALL three render presets. Leave the scene/page visually clean. Free orbit and discreet functional pause/reset/accessibility controls remain permitted; diegetic park signs and shop names are scene geometry, not a teaching overlay. Optional title/readout furniture mentioned later is opt-in, not a toon/hybrid default. No debug panel in delivery.

**Educational only:** canonical V8 right card/mobile dock, causal lessons, part inspection and connected explanatory callouts apply to explanatory commissions, not to all scenes. Explicit UI-free requests still override the panel default: explanation can be delivered through the requested scene behavior and accompanying prose. Narrative scenes with explicitly requested ride/part inspection get the requested scoped interaction, not an automatic lesson dashboard. Explicit requested informational labels are allowed, but do not add unrelated teaching surfaces. Record `uiMode: none | minimal-controls | requested-inspection | educational` and why; never satisfy a UI test by adding unwanted UI.

Regression examples: “amusement park in pixel + stroked toon” → narrative + pixel-stroke + no education UI. “Interactive amusement park” → narrative; interaction alone adds no lessons. “Explain a roller coaster's operation” → educational, chosen style independently. “Amusement park with inspectable rides” → narrative + requested inspection only. A scene with no educational intent must not fail QA for lacking V8, lessons, labels or a card column.

### Default occupied-space pass: actions, seating and scenery

Prevent intersections before adding detail or spawning copies, for people, animals, imported rigs, buildings, props and rides in BOTH profiles/all presets. Use `references/action-clearance.md`, `templates/action-clearance.mjs` and `templates/pose-bounds.mjs` with the actual production evaluator; this adds no educational UI.

1. **Reserve full space, not origins:** building/awning/door parcels, open access paths, actor swept widths and reach, tails/wings/horns, carried items and neighbouring actors. Reuse fitted rigs/clips from internet assets, but reject an asset/clip that cannot fit the required seat/action without distortion. Split accessible structures into actual wall/door/roof pieces; an enclosing hollow-building AABB is only a broad-phase candidate, not solid occupancy. Use deterministic lanes, queue slots, crossing priorities and seat reservations, not random nudges after overlap.
2. **Solve real contact/action frames:** approach → align → bend/lower → supported sit → stand/exit; pelvis, knees, feet and hands follow real seat/ground/handle frames. Don't sit by dropping a standing model through the chair. Ride occupants inherit the seat's moving frame once. Permit only exact named intended body↔support/joint contacts, with action window and bounded depth; never exempt an entire actor, chair, species or same-owner subtree. Check support gaps separately—an allowed collision contact does not prove the person isn't floating.
3. **Check the live pose across the whole action:** refresh skeleton/morph vertices and world frames, then use measured conservative body-region capsules/boxes plus structural pieces. Bind-pose bounds/root-point distances miss moving limbs; undersized colliders and omitted tails/carry props are failures. Broad-screen nearby pairs; refine loose bounds instead of deleting objects to lower candidate counts. Production audits supply independently specified `requiredIds`; missing actors/proxies or unverified coverage cannot pass. Test nonadjacent self-parts too, while explicitly declaring valid anatomical/structural joints. Proxy overlap is not automatically actual mesh penetration.
4. **Test critical times and fixes:** sample full cycles, loop seam, approach/contact/departure, largest reach, sitting/standing, crossings and door swing. Include exact events and refine using relative tip motion/clearance, not only endpoints or an attractive frame. `sampledOnly:true` is bounded sampled evidence, not continuous collision freedom. Move a real wrist/tail/knee into an obstacle, overlap building parcels and synchronize a crossing; the SAME production predicate must flag the fault and pass after repair. Review worst-contact side/back/top crops plus an action strip. Never hide bodies, shrink proxies, fade through walls or freeze the requested action to claim a pass. One source-driven QA runner, cached static obstacles, nearby-pair broad phase and worst-few reporting keep this practical.

### Default asset workflow: search, acquire and USE fitting models

Ask the Model Sourcing Gate after the look is resolved, for BOTH profiles. Follow the recorded `internet-full`, `hybrid` or `authored-only` choice; do not silently impose internet-first. In the first two modes, reuse valid local assets but still search for missing major roles. The acquisition requirements in this section apply to those two modes; authored-only intentionally builds geometry and does not need a failed model search to justify it.

**A search is not the deliverable.** Before detailed hand-modelling, find candidates for the hero and major supporting roles, review the actual per-asset terms and appearance, download the chosen permitted model/dependencies, inspect an actual import, and USE it in the scene when it fits. A fitting, licensed asset must not be ignored in favour of primitive-only reconstruction merely because hand-building is familiar. Nor does importing one token tree satisfy sourcing a park's otherwise hand-built rides/buildings/cast. Record decisions for the main roles in the existing SOURCES/CREDITS/design ledger.

**Fit means diorama-quality, not merely downloadable:** correct subject/representation and silhouette, coherent kit/palette/proportions, adequate construction detail, usable parts/rig/clips for the requested motion or inspection, viable triangle/draw-call/texture budget, and compatibility with the chosen pixel/toon/hybrid rendering. Judge the real model from more than a thumbnail. Normalize scale/axes/origin, adapt colours/materials without losing important markings, preserve rigs/part identity, fit to the scene and review a rendered close-up. A realistic/PBR asset is not automatically disallowed if it can be adapted well; an unrelated low-poly substitute is not automatically suitable. Follow the original long-form craft, composition and motion standards after importing.

**Rights remain mandatory:** prefer FREE assets whose explicit terms permit commercial use, modifications and redistribution/embedding in the delivered scene. Read original asset/license evidence; retain credits/license/change notices where required. NC, ND, editorial, personal/educational-only and missing rights do not pass. Custom/ShareAlike/other terms require compatibility review, not a fake CC0 label. No purchases, subscriptions or paid downloads without explicit user approval. Check separately licensed dependencies. Commercial permission is not scientific accuracy or trademark/other-rights clearance.

**Source order:** use the user's Polyfork-first sweep for narrative kits/props, then the relevant original-author/model-library sources in this guide; if Polyfork misses, continue to appropriate alternatives rather than declare that the internet has none. Educational subjects use their bounded exact-subject search and extra accuracy/structure gate. Reuse a compatible kit for coherence. Do not crawl every provider indiscriminately or repeatedly search the same noun. Actual search/download/import evidence stays on disk; never fabricate searches, licenses or successful loads.

**Hand-model only the justified gap:** necessary missing/custom geometry, unsuitable candidates after source/fit checks, or interfaces/animation adaptations not supplied by an imported model. Selection or movement alone is NOT a reason to reject an asset: use real part/pivot wrappers where feasible. Retain an all-authored approach when the user explicitly asks for it. If browsing/downloads are unavailable, disclose the limitation and fallback; never say the search found nothing when it never ran. A quality mismatch, unclear license or lack of useful motion is a documented reason to reject, not a reason to force a bad download.

**Proof before completion:** for each major role record search/source, chosen asset or rejection/fallback reason, license evidence, actual downloaded file/path/hash and import/style/motion result. A compliant matching candidate found → acquired and used; no suitable candidate → honest specific fallback. Verify the chosen asset actually exists in the final scene, not just in assets/. Offline/standalone delivery packages every permitted dependency and is tested without network; a warm cache or CDN loader is not self-contained. Sourcing adds NO education panels, callouts or other UI to narrative scenes.

### Preserve the approved 4.x additions without shortening this guide

- **Representation:** actual subject by default, not a classroom surrogate. Follow `references/representation.md`: Earth means a planet, not a globe on a stand. Ask real subject / physical teaching model / explanatory abstraction / you choose only if materially ambiguous; preserve explicit choices. Keep representation, render preset, purpose, scene/object context and Inside independent. Natural subjects do not acquire invented platforms, frames or machinery merely because this guide contains mechanical examples.
- **Narrative sourcing:** preserve the user's Polyfork-first catalogue sweep, kits/matching, source decisions and scale/palette integration in `references/external-models.md`. This extends the older model-library section; do not fall back to primitive-only scenery without checking suitable assets.
- **Educational sourcing:** the named teaching object/parts may be verified external geometry. Use the bounded candidate search and accuracy/import wrapper in `references/educational-models.md`, not a narrative full-catalogue crawl. Add authored semantic IDs, interfaces, pivots and explanation where needed.
- **Rights:** all downloaded assets must permit commercial use, modification and redistribution in the delivered scene. Free download is not permission. Use `templates/educational-asset-gate.mjs` with reviewed evidence/credits and actual file hashes; CC0/CC-BY can pass, unknown/custom terms require review, NC/ND/editorial/incompatible terms do not pass. Verify dependencies and offline bundling; a remote CDN load is not an offline standalone artifact. This rights gate overrides older library summaries, including casually accepted restrictive licenses.
- **Construction:** retain `templates/construction-kit.js` and `templates/interface-checks.js`; reserve working pockets, derive contact stacks from shared datums, check actual geometry and repeats. Keep the original detailed construction/selection chapters. Material/selection/annotation checks apply only to implemented/requested features; no forced annotation system to satisfy QA. AABB overlap is a candidate, not certified penetration. Use scoped real mutations, not bespoke injected-object detectors. Available helpers are supplemental, not proof of a whole scene.
- **Maintenance:** do not mutate the installed skill after each scene automatically. An explicit maintenance request and filesystem approval are required. Preserve original/current backups. Historical changelogs document prior versions; they do not override this release.

A diorama is a tiny staged scene with a resettable three-quarter hero camera and
free user orbit. The default pixel preset uses a white cut-out, palette-snapped
pixel grid and ink contour; the other presets follow their own presentation
contracts. Narrative scenes retain the slab and toy-scale animated cast;
educational scenes use the exception below.

Classic Pixel Art is the recommended new-project look. **Stroked toon / illustrated miniature**
(`stroked-toon`) and the **pixel + stroke hybrid** (`pixel-stroke`) are optional
rendering presets for any subject, not a coffee-machine genre. **Ask which of the
three to build in at the start of every project** — see `Render Preset Gate` —
because the look changes presentation only, never the subject, story, research
requirements, choreography or construction standard, and nobody should have it
chosen silently on their behalf.

**Profile precedence (read first):** For an educational explanation, read
`Educational Mechanism Profile` before the narrative defaults. One mechanism and
one causal sequence replace ALL mandatory cast/ritual/multiple-system/story-prop
quotas throughout this guide. Clean off-white and the single V8 right card/mobile dock replace empty
paper or decorative figure UI (explicit placement requests remain supported). Construction and mechanical correctness are never
waived. For EVERY preset, free user orbit is mandatory; fixed/hero views below
refer to deterministic QA/reset poses, not a locked interaction camera.

**This file restores the full guide.** The supplemental references named in the 5.0 additions carry later approved sourcing/representation rules; copy-in modules and the detailed design sheet remain in `templates/`.

**Execution index — do not read every genre recipe first.** Resolve the preset
and profile, then use the fast-path table. Read `Research Before You Model` and
`The Detail Bar` (including whole-object completeness) for every build. Narrative
builds additionally use `One Prompt, One Build`, `The Animation Bar` and their
chosen rendering recipe; educational builds go directly to the canonical UI/
inspection and construction contracts. `The Look Contract` is pixel-only.

| Before advancing | One source of truth / required evidence |
| --- | --- |
| First mesh | Filled `templates/DESIGN.md`: complete object, essential parts, source provenance and shared mating frames |
| Repeated assembly | `Construction regression gates`: every instance, actual axes/bores and end-plane separation; not one good sample |
| Requested selection | `Canonical educational UI and inspection contract`: reuse selection behavior only as requested; no narrative education card/lessons/labels. Verify visible emphasis, keyboard equivalent and exact restoration |
| Claimed pass | `Verification`: nonempty actual geometry, expected counts, negative injections and fresh build hash tied to the report |

This table indexes existing acceptance rules; detailed tests live only in the
sections named here. Read other subject recipes only when the build uses them.

## Render Preset Gate (ask once, every project)

Before the first mesh or presentation work, ask using the structured-choice tool when available. Keep labels and one-sentence consequences visible:

> **Which look should I build this in?**
>
> 1. **Classic Pixel Art (Recommended)** — The original finer palette-snapped miniature look with ink contours and ordered dither.
> 2. **Stroked Toon / Illustrated Miniature** — Smooth bevelled parts, stepped shading and fine charcoal outlines.
> 3. **Pixel + Stroke** — Toon shading and outlines on a low-resolution pixel grid.

Map answers respectively to `pixel`, `stroked-toon`, `pixel-stroke`. Generic “pixel art”, explicit classic and explicit delegation select `pixel`; silence waits. A reference image alone does not settle a materially ambiguous request. Do not repeat the question per material or repair. Record the answer verbatim in DESIGN, including the preset ID and renderer implementation. Every preset supports free orbit and deterministic hero reset; no second orbit question. After the look answer, ask the sourcing question next unless already answered. While either is pending, inspect local files and research the subject, but do not start detailed geometry, model downloads or a presentation implementation that commits the unanswered choice.

## Model Sourcing Gate (ask next, once per project)

> **How should I create the models?**
>
> 1. **Hybrid — source + custom-build (Recommended)** — Search for commercially usable models, download and use the ones that fit, then model missing or scene-specific pieces myself.
> 2. **Internet models throughout** — Search for and use commercially usable downloaded models for all major roles; focus my work on assembly, styling, rigging and animation.
> 3. **Fully agent-modeled** — Build all scene geometry myself for a unified custom look, without downloading third-party models.

This is a separate question after style, not a hidden assumption or a confused “pixel hybrid” choice. Use stable question ID `asset-strategy`, single-select, and map answers to `hybrid`, `internet-full`, `authored-only`. Record exact user wording. Explicit delegation selects hybrid; silence waits. Explicit requests for original/procedural geometry answer authored-only; an offline deliverable alone does NOT mean authored-only (permitted assets can be packaged locally).

- **Hybrid:** actually search for every missing major role and use fitting licensed candidates; fill documented gaps with authored geometry. A token imported prop does not satisfy sourcing the hero/cast/buildings. Do not search and then hand-build suitable assets out of habit.
- **Internet models throughout:** source the hero and all major supporting roles. Scale/material changes, pivots, adapters, collision proxies and simple joining/support geometry are allowed; quietly hand-building a missing hero is not. If no fitting licensed major asset exists, report the specific gap and offer a subject substitute or permission to switch that role to hybrid. Do not guarantee a full matching library before searching, and do not force an unsuitable model just to fill a quota.
- **Fully agent-modeled:** author all visible model geometry, including hero and supporting roles. Subject/photo/motion references and coding/rendering libraries remain allowed; this choice does not mean “no internet research”. Do not download model packs, use an imported model as a hidden starting point, or downgrade the detail/animation/contact bar. User-provided models require an explicit exception if this mode is selected.
- **Commercially usable, not merely commercially available:** in BOTH internet modes verify the actual per-asset license permits commercial use, modification and redistribution/embedding in the delivered scene. Prefer free CC0/compatible CC-BY; preserve required credits, modifications and license notices, check dependencies and package offline. Unknown rights, NC, ND, editorial/personal-only and incompatible licenses fail. Availability for sale is not a rights check. No purchases or subscriptions without separate explicit approval. Explain this briefly with the question; do not overwhelm it with legal boilerplate.
- **Honest exceptions:** unavailable search/download access is not “nothing suitable found”. Disclose the limitation and ask before changing a selected sourcing mode. New choices do not waive subject accuracy or mandatory verification and add no educational UI.

**Pre-build decision receipt:** after both answers, state one short line such as “Classic Pixel Art · hybrid sourcing · narrative · minimal controls”, then record the choices in DESIGN. Before delivery reconcile each major role against its chosen source mode and record native render dimensions, scaling and style crops. Missing answers, unsupported render-preset claims or unapproved sourcing switches cannot pass QA.

### Fast path by scene

| If the commission is... | Read next, in this order |
| --- | --- |
| explicit explanation / guided how-it-works (not a machine or cutaway view alone) | Educational Mechanism Profile → Universal Inspection Controls → chosen render preset → Machine Grammar → Verification (profile-aware) |
| market, food truck, bakery, cafe, shop, laundromat | Cast → Clothed Cast: Heads, Layers, Hands → Service And Queue → Machine Grammar → Carrying, Loading And Mounting → Verification |
| heist, defence, combat | Detail Bar → Tool/Tower recipes → System And Combat Animation → Combat Readability → Verification |
| creature battle, game scene, anime/movie fight | Research Before You Model → Field Notes: Two-Creature Combat → Creature Anatomy → System And Combat Animation → Combat Readability → Verification |
| aquarium, pool, harbour | Cast → base rig → Water templates → Vehicles (boat) → Effects → Verification |
| station, airport, hotel, transit | Service And Queue → Vehicles → Crowd Variation → Verification |
| stage, festival, parade | Cast → Secondary Motion → Crowd Variation → System Grammar → Verification |
| farm, garden, nature | Creature Anatomy → Ambient Loops → Effects → Verification |

The narrative shape is place + repeated ritual + interruption + consequence.
Educational scenes instead use mechanism + causal sequence + observable result;
do not add a fictional interruption or cast. The fast path selects the relevant
reference notes, not extra narrative requirements.

## 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.

## Research Before You Model

Four lookups come before the first mesh: the subject by frames, the asset
libraries, the motion itself, and the capture loop. Skipping them is how a build
ends up with a plausible silhouette that matches nothing and animation that reads
as generic. Budget for them, they are usually faster than the modelling they save.

| Question the research answers | Where it lands |
| --- | --- |
| what does it look like, exactly | `refs/<subject>/*.png` contact sheets |
| what does it do, in what order, how fast | `refs/SOURCES.md` + the beat table |
| does a rig or clip already exist | `CREDITS.md` + `assets/` |
| is it actually right on screen | `qa/` captures, compared to the sheets |

### 1. The subject, by frames

Find the real thing moving, not stills. For games, anime, sport or machinery the
footage *is* the specification: it settles what the shape is, where the motion
starts, how long each stage lasts and what colour it is at each step.

```bash
yt-dlp --flat-playlist --print "%(id)s | %(title)s | %(duration)s" "ytsearch6:<subject> animation"
yt-dlp --extractor-args "youtube:player_client=ios,android" -f 18 -o "refs/clip.%(ext)s" <id>
ffmpeg -i refs/clip.mp4 -vf "fps=8,scale=300:-1,tile=6x4" refs/sheet-%02d.png
```

Read the contact sheets with vision, then write the grammar down in words before
touching geometry: *ball leaves the hand on an arc, opens with a white burst, the
creature springs out at full size, the ball snaps shut and returns*. A paragraph
like that is the acceptance test for the effect you are about to build.

Rules that come out of doing this repeatedly:

- Prefer **game footage** over fan animation for game subjects; the game is the
  canonical grammar, and fan cuts are already an interpretation.
- Prefer **one clean clip sampled densely** over ten clips sampled sparsely.
  Twelve frames a second on a 4 second send-out shows the whole sequence.
- Keep the sheets in `refs/<subject>/` next to the build so the next person can
  see what you were matching, and so QA has an image to compare against.

### 2. Model sourcing: check the libraries before you build

Internet-first sourcing applies to ALL major scene roles, not only creatures. Acquire and use fitting commercially licensed models by default; hand-build only a documented gap or explicit original-geometry request. Hand-building a creature from primitives is the *last* option, not the first. A
rigged download with real deformation and usable clips beats four hundred lines
of spheres the moment the camera comes within a metre. Search first, and keep a
record of what you searched.

**The ladder. Every hero asset walks down it in order.**

1. **Already on disk.** The user's folder often ships a `tools/`, `assets/` or
   `model/` directory with GLBs in it. List it before anything else.
2. **A CC0 pack covers it.** Import it. No attribution, no negotiation.
3. **A CC-BY model covers it** and the page can carry a credit line. Import it,
   credit it, done.
4. **Nothing fits the silhouette** and the shape has to be exact. Hand-build it
   against the reference frames, and say in the log that you searched.
5. **Never:** ripped game assets, Models Resource / Spriters Resource downloads
   used as geometry, "editorial use only", NC, ND, or anything with no stated
   licence. Those are hard stops; ask the user instead of guessing.

**Creatures, characters and rigs**

| Source | Licence | What is actually there | How to search |
| --- | --- | --- | --- |
| [Quaternius](https://quaternius.com) | CC0 | hundreds of low-poly creatures, characters, nature, buildings; the Universal Animation Library is 120+ clips | browse `quaternius.com/packs`, grab the pack GLB |
| [KayKit / Kay Lousberg](https://kaylousberg.itch.io) | CC0 | adventurers, skeletons, dungeon and RPG packs, rigged and animated | itch page, per-pack zip |
| [Poly Pizza](https://poly.pizza) | CC0 or CC-BY | 10,000+ low-poly props, creatures, vehicles; GLB/OBJ, no login | search by noun, read the badge on each card |
| [Kenney](https://kenney.nl/assets) | CC0 | kits for props, vehicles, characters, UI, audio | category browse |
| [Sketchfab](https://sketchfab.com/3d-models) | per model | the long tail: specific machines, animals, buildings | filter **Downloadable** + **CC0**/**CC-BY** before looking at anything |
| [Smithsonian 3D](https://3d.si.edu) | CC0 | scanned real objects, fossils, artefacts, vehicles | search, check the licence note under the download |
| [NASA 3D Resources](https://nasa3d.arc.nasa.gov) | public domain | spacecraft, rovers, terrain, helmets | browse by category |
| [glTF Sample Assets](https://github.com/KhronosGroup/glTF-Sample-Assets) | per model, mostly CC-BY 4.0 | canonical rigged test models (CesiumMan, Fox, BrainStem) | read `LICENSES/` before use |
| [Objaverse]...

© Nehal Kanak (sloemo) · MIT · sloemo01/diorama

Похожие скиллы

Все скиллы по теме «Геймдев и 3D: Unity, Unreal, Godot, Blender» →
ascii-diorama JDhruv14 Скилл ascii-diorama для Claude Code создаёт анимированные 3D-миниатюры, отрисованные цветными ASCII-символами. Включается по запросу на ASCII-сцену, текстовый 3D-рендерер или эффект tilt-shift. CX Codex +1 ★ 111звёзд репо title-sequence-3d charlie947 Скилл title-sequence-3d для Claude Code собирает кинематографичный 3D-опенер на Three.js в одном HTML-файле. Генерирует яркую заставку с неоновыми вывесками и логотипами для видеоролика или рассылки. CX Codex +1 3 400установок threejs-landscape MengTo Скилл threejs-landscape собирает живой ландшафт на Three.js: холмы, трава, камни, небо и смена времени суток. Годится для hero-фонов и сцен, где объект должен стоять в месте, а не висеть на градиенте. CX Codex +1 1 600установок build-wireframe-scan-reveal MengTo Скилл build-wireframe-scan-reveal раскрывает Three.js-модель волной, которая ведёт проволочный каркас, а следом наращивает твёрдую поверхность. Каркас сгорает в финале. CX Codex +1 1 500установок three boraoztunc Держит Three.js-сцену в HyperFrames синхронной со временем ролика: адаптер шлёт hf-seek, а сцена рисует запрошенный кадр. CX Codex +1 209установок threejs-skills sickn33 Скилл threejs-skills для создания 3D-сцен, интерактивных опытов и визуальных эффектов на Three.js. Подключите, когда нужно рендерить 3D-графику, WebGL-сцены, анимации или визуализировать данные в трёхмерном пространстве. CX Codex +1 3установок

Спонсоры проекта

Компании, которые помогают держать аналитику открытой