jianying-transitions

JianYing Transitions

Transitions are the semantic connections between adjacent segments. Verify the boundaries and assets first, then decide whether to use them.

When to use

• The user explicitly requests the CapCut capability corresponding to this skill's title and accepts handling it through the unified Rust jianying CLI.
• The user needs auditable planning, execution, or verification evidence, not just a conceptual answer.
• When requirements are not yet clear, first hand off to jianying-use routing; this skill should not be used for other editors, general video knowledge Q&A, or speculative execution lacking the necessary assets.

Capability boundaries

• ✅ Can do: Generate deterministic plans based on real paths and probe results; perform operations in this domain when capability is supported ; output the evidence level actually achieved.
• ⚠️ Requires conditions: Writes must use isolated copies; fees, external services, and native application actions must have precise approval; playback or export conclusions must have corresponding runtime evidence.
• ❌ Out of scope: Do not automatically install or upgrade the CLI, do not generate Python draft scripts, do not call external headless checkout, do not overwrite source drafts, and do not fabricate asset IDs, media facts, or success statuses.

Step 1 — Establish a factual baseline

Record the user's goal, absolute paths, host platform, target deliverable, and allowed side effects; when information is insufficient, first provide a read-only diagnostic plan and list the missing facts item by item.

Step 2 — Handshake capabilities

Run version, doctor, and capabilities checks. A satisfying version does not mean the capability is available;partial、external_dependency or a missing status must enter the degraded path.

Step 3 — Validate input

Probe media, drafts, configuration, or task status; reject nonexistent paths, out-of-range times, unknown schemas, mismatched hashes, and approvals that cannot be bound to a target.

Step 4 — Form a deterministic plan

Write the operations, parameters, output paths, risk levels, confirmation points, and expected evidence into the plan. Order multiple tasks as "read-only facts → reversible writes → external/native actions".

Step 5 — Execute or stop before the gate

Only execute steps that are supported and authorized. When output is ambiguous, times out, or is partially successful, retain the task ID, audit log, and artifacts, and do not automatically retry.

Step 6 — Verify and deliver

Run structural validation, then append cold reopen, playback, or native export evidence according to the target; report the actual level, failed fields, recoverable actions, and unverified items.

Rules

• The asset durations, dimensions, streams, hashes, and draft versions in the plan must come from tool output.
• Approval must be bound to the command, parameters, target, validity period, and budget; if any field changes, reconfirm.
• User data is processed only within local target paths and the declared external Provider boundaries; unrelated credentials must not be collected, uploaded, or recorded.
• When current evidence is insufficient, use UNVERIFIED、BLOCKED or AMBIGUOUS; it is forbidden to fill in results with inference.

Gotchas

1. Treating version as capability: Always check the specific capability; do not execute directly just because the CLI version is new enough.
2. Treating structural validation as final acceptance: project verify It only proves the structural layer; playback and native export require independent evidence.
3. Directly modifying the source draft: First create an isolated copy and record the input hash; any in-place overwrite request must stop and be changed to a new output.
4. For ambiguous, automatically retry: first query the task, audit, and external artifacts; only after confirming that no side effect occurred may the user approve a retry.
5. Filling in resources or times from memory: resource IDs come from the catalog, and times come from probe/ASR/project data; when they cannot be obtained, block explicitly.
6. Vaguely asking for more information: first give an executable read-only plan, then explicitly list the gaps such as paths, delivery levels, or authorization.

Verification Checklist

• CLI identity, version, and capability have been recorded.
• All input paths, media facts, and hashes are verifiable.
• Write targets are isolated from source drafts, and confirmation points are precisely bound.
• Failure and ambiguous paths retain the task ID, logs, and recovery recommendations.
• The final wording is consistent with the actual evidence level.

Runtime Contract

• Trigger conditions: the user requests transitions, shot matching, beat sync, or queries available transition resources.
• Required capability:timeline.transition、media.catalogue。
• Minimum CLI version:1.6.0; when transition is partial, only generate the plan and diagnostics.
• Default risk:reversible_write。
• Input facts: adjacent clip IDs, duration/handles, beats or chapter boundaries, resource catalog status, and authorization.
• Confirmation points: confirm before using member/restricted resources, writing to an existing draft, or performing native playback.
• Success evidence:playback; a catalog hit or the presence of a wire field is not perceptual acceptance.
• Prohibited actions: do not generate Python draft scripts, do not call external headless checkout, do not add transitions to the final segment, do not abuse every cut point, and do not treat cache existence as authorization.

Workflow

1. Use media catalog to retrieve names; do not fabricate resource IDs from memory.
2. Check the adjacency relationship, duration, and available handles of the preceding and following segments.
3. Transitions are attached to the outgoing segment, and their duration must not exceed the available window on both sides.
4. When the capability is not supported, output a suggested plan and do not write to the draft.
5. After it is supported, write to an isolated copy and check pacing, black frames, and missing resources through a cold reopen and playback.

For boundary policy and recovery, see references/workflow.md. For isolated editing jobs, see examples/minimal-job.json。

Progressive Materials

• On first execution, load Normal Path to obtain the end-to-end sequence.
• When encountering failure or an unknown state, load Failure Recovery and Error Recovery Table。
• When the user requests privilege escalation, overwriting, or automatic retry, load Boundary Refusal。
• Before delivery, complete Verification Checklistitem by item; do not claim completion based only on a plan or the existence of files.