Develop Timeline Studio Plugin
Design, evaluate, implement, or review image and video generation connectors for...
Install
npx skills add MartinDelophy/ai-video-editor --skill develop-timeline-studio-plugin -g -a claude-code -y- Repository
- MartinDelophy/ai-video-editor928
- Category
- Design
- Updated
- 5d ago
- License
- MIT
- Context cost
- Lightabout 884 tokens
- Runs scripts
- No, instructions only
What it does
Design, evaluate, implement, or review image and video generation connectors for Timeline Studio. Use when adding a provider plugin, extracting the generation plugin host or registry, or checking a connector against Timeline Studio's authentication, output, localization, and My assets contract. Do not use for ordinary video editing or Codex plugin packaging.
Develop Timeline Studio generation plugins
Build a source-integrated generation connector that remains isolated from Timeline Studio's editing core and returns real downloadable media to My assets.
Start with the contract
Read ../../docs/generation-plugin-development.md completely before designing or changing a connector. Treat it as the source of truth for provider eligibility, runtime classes, manifest and adapter shapes, security, localization, output normalization, and completion criteria.
Also read the repository's AGENTS.md and inspect the current implementations in:
src/components/GenerationPlugins.jsxsrc/hooks/useGenerationPlugins.js
Do not assume that an external installable plugin runtime already exists. Current plugins are reviewed source integrations. If the shared registry and host described by the contract are absent, make only the bounded extraction required for the requested provider and preserve existing provider behavior.
Decide before implementing
Use the provider's current official documentation to establish:
- a stable task/result API or owned browser SDK;
- automatic retrieval of every generated image or video;
- authentication and credential ownership;
- browser and CORS requirements;
- real job, progress, error, and cancellation semantics;
- temporary-output lifetime, cost, region, and account constraints.
Reject a generic embed or manual result-URL workflow. Stop when the provider requires a developer secret in browser code or lacks a safe automatic output route. State the exact missing capability rather than simulating it.
