AI Video Editing with Timeline Studio

Turn the user's exact editorial request and media into reversible Timeline Studio edits. Keep the editable timeline as the source of truth; never replace it with an opaque one-shot render.

Choose the execution path

1. On first local use after installation, read references/host-environment.md. If Node.js is unavailable, start with the zero-dependency Shell or PowerShell bootstrap; otherwise run node scripts/setup-host.mjs --check. Agent-driven Chinese and mixed Chinese/English voiceover uses Timeline Studio's owned browser-local Hojo TTS Light 80M two-voice bundle and does not require a separate Python voiceover capability. If language runtimes or dependencies are missing, show the exact installation plan and obtain explicit user approval before install mode; never treat Skill installation as permission to modify the host or download models.
2. Treat local project-file processing as the default for deterministic editing: inspect media locally, modify the portable .timeline through the command layer or local archive services, render locally, and verify decoded output locally. Do not open a browser merely because the editor has a UI.
3. Treat https://video-editor.ai-creator.top/ as the canonical hosted editor only when the user explicitly asks to use the website, provides no local repository or project path, or requires a hosted-only capability.
4. When this repository is available, prefer its Agent command layer and local media tools. Start the local server and browser only for a verified UI-only operation that the local project pipeline cannot express and the user has not required a local-only workflow. Read the actual server URL from process output; never assume port 5173.
5. Prefer the bundled Timeline Studio MCP tools when the host exposes them. Read references/mcp-integration.md, inspect the project, and always call timeline_project_diff before timeline_project_apply with the same revision and operations. The MCP server is a transport over the repository command runner, not a separate editing implementation.
6. When MCP is unavailable, inspect package.json for an Agent command script. Do not use npm run ... --if-present as capability detection because it can succeed silently. If the command runner exists, read references/command-contract.md, inspect the project, build a versioned plan, run the structural validator, and use project.diff as the authoritative semantic dry run before project.run.
7. If a required operation is missing from the local contract, state the exact gap. For repository-development work, implement the smallest shared local operation and renderer support before falling back to UI. Otherwise ask before switching to the browser workflow.
8. Do not claim deterministic or idempotent execution when only UI automation was available. State the limitation and preserve an editable project archive when the UI supports it.

Workflow

1. Inspect before editing