Template project → video

Scope and shared execution

Turn the selected editable template into the requested draft, editable project or finished video, preserving its agreed structure, motion and style. This is the implemented template route, including direct Skill selection. Read shared context once and apply only dependencies needed by this scope; reuse complete bodies and completed operations. Continue here without returning to production/start. MCP-only clients use resources/read motion://workflow/template/start, which returns this same file with status: "ready".

Changes to existing content use the shared edit workflow, including required related changes and preserved content. Missing instructions and target sources must finish returning to the model before a later call applies a template, imports, writes or exports. Entering this Skill again does not create another copy, apply the template again or repeat a completed export.

The accepted installation experience follows first-run defaults: use the exact template ID and unchanged sample content offered and accepted in this conversation, with that template's own duration. A single-template yes accepts it; a three-candidate yes needs clarification. Resume an existing experience project or create one independent copy once. Open its editable preview; export only if requested. Do not restart the template/assets questionnaire or substitute a fixed default. Initial installation reply rules and few-shots come from docs/install.md, section “Installation-success reply”; this Skill resumes creation after consent.

Open the supplied project

A template is a complete native HyperFrames project, not necessarily a catalog entry. For a supplied folder or ZIP, inspect/unpack it and make a working copy when editing or rendering is needed; resume that copy on later turns. Read index.html, native configuration and TEMPLATE.md (older templates may have EDITING.md/REPLICA.md instead) for changes or a fresh render. An unchanged request needs only the editable preview handoff below. Preserve source, assets and hidden Studio manifests. Do not require template.json, a local template ID or catalog registration.

If the user selected a gallery/catalog item instead, read its exact source/guide and ID, then follow catalog capabilities. Bundled projects use motion_create_project with projectType=template, templateId, requestId, title and requirements only when the selected project has not already been created. Editable registry sources are inspected and adapted from their real source and assets; builtin and Prism catalog templates can create a project with projectType=template. For discovery call motion_list_templates, read or grep/jq the returned local JSONL index, and call motion_get_template for the chosen ID. Known IDs can go directly to motion_get_template. Preserve the instructions and review limitations in TEMPLATE.md. An external reference video is not an editable template: ordinary video recreation uses motion-recreate; a request to produce a reusable template uses motion-video-to-template. Correct the route once, carrying the selected source and scope, rather than substituting an unrelated example.

See the portable project contract for the handoff layout. HTML/CSS/JS is authoritative; metadata and editable variables are aids, not modification limits.

For a plugin-managed artifact, use the runtime adapter: confirm projectId/session ownership with motion_get_project, use motion_import_assets for supported local media, then read the current revision/version and save through motion_edit_project with projectId, requestId, expectedRevision and expectedVersionId. A real conflict requires reading the newer source and forming the edit again; preserve Studio changes and never bypass the guard or replay an old full file. For an independent folder/ZIP, work on its actual source/copy and record before-edit file evidence; a revision from an unrelated active MCP artifact cannot protect this directory. The MCP has no general folder/ZIP adoption or binary/font import Tool; use host capabilities for independent portable projects and report unavailable steps honestly.