agentleFS
Sign inStart free
VisualxIntelligenceVisualxIntelligence/motion-tools-and-skills/skills/claude-motion/claude-motion-web-sims/SKILL.md

claude-motion-web-sims

Skill9 starsChanged 22 days agoMITView on GitHub

Build a simulation-style video (agents, particles, 3D machines, fly-throughs) as one HTML page whose render(t) is a pure function of time, then capture it frame by frame to a 60 fps mp4 with sims/capture.mjs. Use when the idea is a simulation or a 3D object rather than motion graphics with text and UI.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read sims/README.md first.

    line 8
  2. Very specific:

    Put every beat in a timeline.json next to the sim (chapters, the hero moment, camera keys).

    line 22
  3. Very specific:

    Start from the closest example: crawlers (agents on DOM text), dossier (the same plus screen-space overlays), engine (three.js object with …

    line 24

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Web sims

Read sims/README.md first; it has the contract and every command.

When to use this instead of Remotion

  • Hundreds of moving things with their own rules (agents, particles, crawlers).
  • A 3D object or machine the camera moves around or flies through.
  • Anything that is easier to write as a three.js or canvas page than as React.

Motion graphics with type, UI and timed reveals stay in Remotion (src/).

Workflow

  1. Agree on the idea, the hero moment and the length with the user. Default format: 1080×1350 layout (4:5), 60 fps, 20–24 s.
  2. Put every beat in a timeline.json next to the sim (chapters, the hero moment, camera keys). Sound scripts read the same file.
  3. Start from the closest example: crawlers (agents on DOM text), dossier (the same plus screen-space overlays), engine (three.js object with cutaway, chapters, fly-through, exploded view, generated sound).
  4. Simulate anything stateful once at load; render(t) only reads it.
  5. Build: node sims/build.mjs <name>.
  6. Review with stills at every beat: node sims/capture.mjs <name> --stills 0,2,5,8,12,16,20 --cols 4 --out out/sims/<name>-review.png. Open the sheet and check it like the review loop says: frame 0 strong, one focal point per frame, nothing blown out by bloom, text readable on a phone, labels never cover the subject. Fix and repeat.
  7. Sound: a music track (--music, the sim gets cfg.beats and should hit the drop), a generated bed (python3 sims/<name>/sound.py like sims/engine/sound.py), or both mixed with ffmpeg first.
  8. Capture: node sims/capture.mjs <name> --size 1080x1350 --out out/sims/<name>.mp4 and look at a sheet of the final file before calling it done.

Lessons from the examples

  • Bloom eats detail: keep emissive and additive layers under ~1.0 and raise them only for the one hero moment.
  • Glossy metal plus a low sun gives white streaks. Use roughness ≥ 0.45 and envMapIntensity ≈ 0.5 on big surfaces.
  • One hero object beats a crowd. If parts hide the subject, move them out of the way or fade them.
  • Chapters + a one-line caption per step + labels with real numbers make a simulation read as an explanation, not just eye candy.
  • A camera that flies through the object is worth more than ten orbits.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free