← ClaudeAtlas

code-path-traced-filmlisted

Make a short animated film in which everything is code the agent writes, including the renderer: a path tracer in one WebGL2 shader (no Blender, no three.js, no meshes, no textures), characters and props as signed distance fields, a meadow of analytic curved grass blades, moon, firefly and window lights with soft shadows, depth of field and motion blur, a variance-guided denoiser, a score synthesized in numpy from the same timeline, captions and an encode. Includes the complete tested film "The Smallest Star" (70 s, 11 shots, two characters) as a starter, a live page that runs the same renderer in the browser, and the speed-ups and traps found while making it. Use when someone asks for a film, short or music piece "made entirely in code", "write your own renderer / ray tracer / path tracer and make a film with it", a storybook or clay-diorama 3D short without Blender, a "no assets, no video model" showcase of what a coding model can do, or a remake of The Smallest Star with another story. Not for a Blender fi
vargHQ/skills · ★ 38 · AI & Automation · score 86
Install: claude install-skill vargHQ/skills
# A film where the renderer is code too Coding models make video by writing programs. Most of those programs drive someone else's renderer (Blender, three.js). This skill goes one step down: the agent writes the path tracer itself, then tells a story with it. The claim a viewer can check is simple and strong: no 3D software, no models, no textures, no video model, no music model. The starter is a finished film made this way in one session. - Film: `scripts/smallest-star/` renders "The Smallest Star", a 70 s fable about a firefly and a lost mouse ([watch it](https://s3.varg.ai/files/194b94d0-58ff-4e8b-91de-4f1959d04013/file_8d3b65611ed8.mp4)). All 1,560 frames at 1280x720 took 1 h 46 min on a MacBook Pro M4 Pro; the whole session, from a one-line prompt to the encoded film, took under three hours (2026-11-10). - Live page: `scripts/smallest-star/live/` bundles the same renderer into one HTML file. Viewers drag the camera and watch the picture converge on their own GPU (28 ms a sample at 960x540 on the same laptop). Post the link with the film: it is the proof. ## Ask first Put these to the person before building. Each one changes hours of work. 1. **Story.** Their own (a moral in one line is enough) or one the agent writes. Two characters and three places is the ceiling for one session. 2. **Length.** 30, 60 or 90 s. Render time grows with length: the 60 s film took about two hours of GPU at 1280x720 on one laptop. Offer 30 s when they want it today. 3. **