One engine, many doors
The engine is plain TypeScript with no UI. The editor, scripts, plugins and agents all drive it through the same commands, so nothing has a private back door.
The pieces
| Package | Job |
|---|---|
@solomotion/core | The document (MotionDocument), its schema, evaluation per frame, keyframes and easing, physics, rigs, tracking, text, export plans. No DOM. |
@solomotion/web | The editor: stage, panels, timeline, renderers. A Next.js app. |
@solomotion/ui, @solomotion/theme | The parts kit and the theme engine the editor and this site wear. |
@solomotion/platform | Ports for files, clipboard and windows, with web and desktop adapters. |
@solomotion/lipsync | The viseme engine that turns a voice into mouth shapes. |
@solomotion/templates | The built-in templates, each a script that builds a project. |
@solomotion/agent, @solomotion/skill | The built-in agent and the skill that teaches any agent the studio. |
@solomotion/mcp | The MCP server that links an agent to a studio tab. |
@solomotion/plugin-sdk | Types and validation for plugins. |
The flow of an edit
- Something asks for a change: a click, a script line, a plugin call, an agent tool.
- It becomes a command from one registry, with a schema. Invalid input changes nothing.
- The command writes the document and records one history step, labelled with its author.
- The editor re-evaluates the frames it shows. Everything is a function of the document and the time.
Evaluated, never baked
A frame is computed from the document at a time: keys, expressions, behaviors, physics, rigs. Physics re-runs only when what it starts from changes, and every frame reads the same result whether you scrub, loop or export. That is why the preview and the export always agree.
Files
A project is a .motion bundle: the document as JSON plus its media. The document is validated against the core schema on the way in, so an old or hand-edited file either opens correctly or names the field that is wrong.
Read the code
The repository is solocreates/solomotion. Start in packages/core/src for the model and apps/web/src/editor for the editor. Logic that does not need a browser lives in a package, with tests beside it.