Motion Studio

Implement the user's choreography using a coherent Three.js motion language. Start from the supplied mechanisms, not a fresh approximation of the lighting/void. The default is a small runnable starter; V15 is a detailed reference, not a mandatory sequence. Preserve user paths, image order, focal framing and accepted entrances. Ask about genuinely unresolved scene direction before replacing it.

Update before every use

Read updates.md before execution. Check the public upstream, preserve local work, integrate safe fast-forwards, and announce the changes actually integrated since the previous successful sync. First use identifies its starting version; unchanged use says no updates were found. Refresh copied skill files after updating. No Averlo account or access key is required.

Start with a concrete motion brief

Read the supplied reference and existing implementation. Identify the requested journey for each scene: start relative to camera, readable position, destination relative to the dark field, focus, visible overlap, and any intentional pause. Ask one narrow question at a time only where the answer changes the work; continue independent implementation while awaiting the answer. Do not re-ask settled choices or substitute style adjectives for trajectory decisions.

When the user has not chosen a motion direction, ask a short creative-choice question: “What kind of animation would you like: a directional pass, a receding fan, a surface wave, curved ribbons, a pivoting/orbiting arrangement, an illuminated reveal, your own idea, or should I choose?” Offer a few relevant options, not a mandatory complete questionnaire. If the user delegates the choice (“surprise me”, “you choose”), proceed without asking again. Do not turn these options into a fixed sequence.

For an open or delegated creative brief, read composition.md before choosing choreography. It supplies spatial ideas, handoff mechanisms and selection rules. For a complete showcase, compose distinct scenes with their own purpose, artwork allocation and animation—not just successive poses of the same cards. Write the scene map before paths; the minimal starter is technical scaffolding, not a single-gesture creative default.

Examples teach mechanisms, not compositions to reproduce. For an open creative brief, choose a distinct spatial idea before consulting the closest reference for its timing, lighting or handoff. Do not automatically combine the same bands, grid and logo because the example did. The overlapping-handoff reference demonstrates how two scenes can share screen space; its exact arrangement is optional.

For a new project, read starter.md, then run scripts/create_project.py with the provided artwork. Use the minimal example by default. The script creates an isolated project; install its pinned dependencies, inspect a rendered frame, then render the video. Read implementation.md before changing materials, field or shadow code. Do not assume a CLI build proves the shader or image loading works.