scene-3d
Skill5 starsChanged 11 days agoMITView on GitHub
Build a 3D shot for a video - live in the composition with Three.js (engines/three.js) or as a pre-rendered Blender plate (engines/blender). Covers toon, photoreal and neon looks, product and CAD models, camera moves, physics, and keeping every frame deterministic.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- VinayKhandia/no-sloptheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- VinayKhandia/no-slop★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- capture-siteSkill
- character-2dSkill
- make-videoSkill
- new-brandSkill
- pick-engineSkill
- review-deskSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use threeLayer(el, { update(t), background, fov }) from /engines/three.js.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
3D shots
Three.js (live layer)
- Use
threeLayer(el, { update(t), background, fov })from/engines/three.js. Add an import map forthree(seeexamples/engines-demo/index.html). update(t)sets every transform fromt. Camera moves: keyframe with a GSAP tween on a plain object (tl.to(cam, { x: 4, z: 8, duration: 2 }, 3)) and copy it intocamera.positioninupdate.- Models:
GLTFLoaderfromthree/addons/loaders/GLTFLoader.js(add"three/addons/": "/core/node_modules/three/examples/jsm/"to the import map). Wrap the load inStudio.wait(...). Put model files in the brand'sassets/models/or the production'scomposition/. - The look (
looks/README.md) decides the rendering style; the same model can go any of these ways:- Cartoon (
looks/toon-3d):toon(color, { steps })+outline(mesh, { thickness }). Hard light: oneDirectionalLight+ lowAmbientLight. - Realistic (
looks/photoreal):await realistic(renderer, scene)(wrap inStudio.wait: ACES tone mapping, a studio environment for reflections, soft shadows) +pbr(color, { metalness, roughness, clearcoat }). A key light withcastShadow, a cool rim light from behind, aShadowMaterialfloor over a CSS gradient. Keep the camera above grazing angles (glossy faces turn white), move slowly, render the final withStudio.setup({ motionBlur: true }). - Neon (
looks/neon-noir):emissive(color, intensity)+threeLayer(el, { post: bloom({ strength, threshold }) }),scene.fog. Keepthreshold≥ 0.2 and emissive ≤ 2 or everything blooms white.
- Cartoon (
- Animated GLB clips: create an
AnimationMixer, then inupdatecallmixer.setTime(t - start). Nevermixer.update(delta). - HTML tags that follow 3D points: in
update(t), callcamera.updateMatrixWorld()and the parent'supdateMatrixWorld()beforevector.applyMatrix4(obj.matrixWorld).project(camera). Three.js refreshes these only insiderender(), so without it a tag follows the previous frame. Example:productions/bike-logger/REEL-002-engines. - CAD meshes as JSON (vertices + indices):
toNonIndexed()+computeVertexNormals()gives crisp flat facets. Render withthreeLayer(..., { pixelRatio: 2 })for supersampled edges. - Physics: bake it (simulate at a fixed 1/120 s step into an array before the first frame) and look up by
t. - Talking character: load
/engines/lipsync.jsand the line's.visemes.js(fromscripts/lipsync.sh) with classic<script>tags, then inupdate(t):LipSync.paramsAt(cues, t, "mouth", { offset })→{ open, wide, round }(0…1) onto morph targets (mesh.morphTargetInfluences) or a mouth mesh's scale. Seeengines/README.md, Lip sync.
Blender (plate)
- A scene script defines
build(ctx); copyengines/blender/example_scene.py.ctxgivestoon(rgb),key(obj, "location", t, value),size,fps,duration,frames,scene. - Render:
engines/blender/render.sh scene.py composition/plates/<name>.mp4 --size 1080x1920 --duration 4 [--engine EEVEE|CYCLES|WORKBENCH]. Draft at--size 540x960, final at full size. - Backdrop colour: show it to the camera only (Light Path "Is Camera Ray" mix, as in the example), or it lights the scene and flattens toon bands.
- Colour management is set to Standard so brand hex colours come out as typed. For a photoreal plate, switch to
ctx["scene"].view_settings.view_transform = "AgX"inbuild, render with--engine CYCLES, and use area lights and camera depth of field. - Physics and simulations: bake them in the scene script before rendering.
- Talking character:
import lipsync as Lin the scene script (run.pyputsengines/blender/and the script's own folder on the path),cues = L.load("productions/…/audio/vo.visemes.json"), thenL.key_shape_keys(head, cues, ctx, offset=VO_START)keys shape keysopen,wide,roundon every frame (names={"open": "Jaw"}for other names). Anything else:L.params_at(cues, t, offset=…)per frame withctx["key"]. - In the composition:
<video src="plates/<name>.mp4">+Studio.video(el, { start }). Plates have no alpha; put text and characters on top with HTML layers.
Check
Render the key beats as stills and look at them. For Three.js, render one frame twice and compare md5s. Note render times in the production log.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

