Used for Jianying "templates" as well as reusable draft templates and text style presets. Template application must produce an independent draft and must not retain a mutable dependency on the source template.
When to use
- Browse, save, copy, or apply draft templates.
- Replace template text/assets and import template tracks.
- Extract and apply text style presets, or search official templates.
Capability boundaries
- ✅ Can do: template inspection, saving, application, copying, content replacement, guides, and text presets.
- ⚠️ Requires conditions: aspect ratio/fps/font/assets must be compatible; official templates require entitlements; output requires a cold restart.
- ❌ Should not use: do not modify the source template, do not silently delete tracks or change fonts, do not treat thumbnails as downloaded templates.
Quick start
You can directly say: "Save this draft as a social media template", "Import the subtitle track from a sub-draft", "Apply the template and then replace the product image and title". On first use, load feature flow. For batch personalized output, load Clone-first contract; each output is verified independently, and the master template remains read-only.
Execution contract
- Trigger conditions: the user requests a template library, applying a template, reusing a draft structure, replacing template content, or text style presets.
- Required capability:
template.library、template.preset、template.duplicate、template.import_track、media.official_resource_apply、project.verify。 - Minimum CLI version:
1.6.19; local template commands are supported, while official online templates remain gated by the download/apply Adapter. - Default risk:
reversible_write。 - Input facts: absolute paths of templates/drafts, aspect ratio/fps, track and material lists, replacement table, purpose, layout, and entitlements.
- Confirmation points: saving to the template library, applying restricted templates, batch replacement, and writing to the formal draft library are confirmed separately.
- Success evidence:
cold_reopen; a successful directory copy does not mean the template assets are usable. - Prohibited actions: must not modify the source template, retain external mutable asset references, ignore aspect ratio conflicts, or treat online template thumbnails as downloaded resources.
Workflow
Step 1 — Inspect the template
template inspect/list Read the template structure and materials, and check the aspect ratio, fps, and missing assets.
Step 2 — Choose an action
According to feature flow , choose save, apply, copy, replace, guide, or preset.
Step 3 — Create an independent output
Transactionally create an independent output and relocate local assets.
Step 4 — Verify
project verify、project diff Then cold-restart and check the layout, fonts, and resources.
Step 5 — Recover
On failure, delete the unregistered output or restore from a snapshot, without modifying the source template.
Rules
- Template output must be independent of the source draft and source asset mutable paths.
- Replacement targets must be uniquely located by name or track/index.
- Aspect ratio, fps, font, and license conflicts must be reported before conversion.
- Template application and draft publishing are approved separately.
- Compound Clip remains
supporteduntil the release binary capability isplan_onlyfor it, and must not be replaced by directly editing JSON or GUI macros.
Gotchas
- Directly editing the source template: Always create an independent output.
- Wrong track selected with the same name: After inspect, use a unique track identity.
- Replacement asset duration mismatch: Probe first and explain the cropping strategy.
- Font fallback breaks layout: Check fonts and line breaks on a cold restart.
- Official template cache invalidated: Entitlements and receipts must correspond to the current use.
Security and Data
Template operations by default only read and write the user-specified local directory and do not upload materials; online templates only save minimal resources and entitlement evidence.
See the minimal Job at examples/minimal-job.json。