ByVideo Controlcalled after the user explicitly selects the CapCut route. episode.output_target=jianying. First readCapCut Output RulesandAsset Contract。
Draft Folder Pre-check: Before calling, you must first confirm that the CapCut draft folder path has been configured. If the user has never filled in the CapCut draft folder location (hvp jianying-config is empty), you must first ask for and obtain the absolute path of the user's CapCut draft folder and save it; you must not directly generate or deliver a draft when the draft folder location is not configured.
Pre-production Design
Read by shot ST numberStoryboard Asset Preparation Directoryand the corresponding documents, and verify the images, transparent PNGs, frame sequences, or videos actually required by the native configuration. After confirmation, deliver specific prompts, actual reference images, and return requirements for generatable missing assets; real screen recordings, factual data, and original files need to be collected. Unsupported complex implementations must not be falsely reported as the user lacking assets, and must not be automatically replaced with pre-rendering.
By default, only ST-001–004 are used, and each shot's specific configuration is checked: basic images, original-speed videos, transparent PNGs, limited frame sequences, editable text/subtitles, and adapted keyframes can be native. The numbers 1–4 themselves do not mean that arbitrary environmental effects, regular motion, rotation, or complex masks are supported.
Tracks are organized by editable objects: background images, each sprite, text, and sound on separate tracks. The looped or non-looped image frame sequence of the same sprite is placed on one character track; do not create a separate track for each frame; different sprites remain independent. Full-image limited frames are also arranged on the same main picture track. Only adjacent main pictures that require native transitions share a track; characters and text must not be merged into it; other backgrounds are independent by shot. Deliver editing-map.json and track descriptions, indicating the positions of background, characters, text, and subtitles shot by shot.
Picture Book Production
Image prompts and image generation followHand-drawn Image Generation Rules. When an image type is specified, generate a complete illustrated text page; do not arbitrarily require wordless illustrations just for editable text; in this case the text within the image is fixed, do not repeatedly overlay the same copy, and CapCut can still handle the actual subtitles independently.
When the user requests a picture book, you must readPicture Book Production Guide. Multiple ST-001 shots each serve as story pages, natively organizing a paper-colored background, a centered complete illustration, a short sentence below, and an optional small title, delivering actual illustration assets + an editable text draft. The illustration does not need to fill the screen, nor does it require the user to generate an entire video. Use adapted position/scale/opacity keyframes to create slight camera movement; use retrieved CapCut native transitions across pages. Centered text must calculate the region according to the actual font width; do not assume a generic align field exists; check that the illustration, story short sentence, and shared subtitles do not obscure one another. Paper texture images, rounded edges, or effects are added only when suitable assets/native implementations are available. Browser raindrops, watercolor reveals, and complex masks cannot be directly written as native capabilities; explain the differences and produce according to confirmed effects, without substituting your own pre-rendering.
Design actions and editing based on Jianying's native capabilities; do not write JS first and then insert it into the draft. Configure transition_out, effects, and filters in each shot's jianying field using the actual names, resource_id, or effect_id that have been retrieved; on export, automatically write the native materials and references. Transitions go on the preceding segment and use the same track as the adjacent main picture; ST-003 is background transition only, and characters/text do not transition along with it. If a complex multi-layer transition for an entire shot has not been adapted, report it explicitly. Whether effect resources are available on this machine, and the actual visuals and export, are verified separately.
Thresholds and exceptions
Share the plan confirmation, full material review, Flow return, voiceover, and subtitle processes with the master control. Before production, check with export-plan; if unsupported, report the specific shots and reasons.
Volcano voiceover uses the same packageVolcano Voice Skilland hvp tts; the client is provided with the package, and the account is stored in local configuration outside the repository; do not read an external local CLI. The actual voice and subtitles enter Jianying's audio track and subtitle track as independent materials.
By default, browser pre-rendering is not invoked. If ST-005–007 or JS-environment effects are truly needed, first explain the specific shots, the source of the time cost, that the picture will be merged into video, and the loss of editability, and obtain the user's genuine consent; after updating and confirming the plan that includes this route, use output_backends.record_prerender_approval to record the reply and shot numbers. render_backend=web or auto does not equal user authorization; when the plan is revised, the old authorization becomes invalid.
Without consent, adjust to native-capable effects or submit a browser-route plan; do not silently change the visuals. For shots explicitly with render_backend=jianying that are unsupported, still block them; do not use authorization to override their native requirements.
Delivery
ExecutionShot review and delivery verification: Check the actual exported track IDs, character frame sequences, and layer order, and provide a track comparison. Clearly distinguish preview material cards, layout diagrams, and the actual Jianying picture. After modification, generate a unique new-version draft and delivery package, and verify the preview and installation paths; for original-image/full-page reuse, explain the editability limitations of the text within the image. If the software or webpage has not actually been reviewed, mark it as unverified; do not assert that the picture is correct based only on structure.
Output the draft package through the master control hvp export/build; full-film render/mix is prohibited. Only process pre-rendered shots agreed to by the user; keep other layers native. The package contains the draft, actual materials, manifest, installation tool, and Chinese instructions. The user opens it in Jianying 10.9 and exports manually; app opening, actual export, audio and font checks, and user aesthetic acceptance are registered separately. Passing the draft structure cannot be called passing the actual Jianying export.
Save the draft folder location with hvp jianying-config --draft-dir "absolute path"; view it by passing no parameters. The configuration is stored in the local user directory outside the repository; updating the repository and syncing the Skill will not overwrite it. hvp jianying-install <package> reads the saved location by default; --draft-dir only temporarily overrides it and does not modify the saved value. If it is not set, the directory is invalid, or the configuration is corrupted, report an explicit error and do not automatically switch paths. User configuration is not delivered with the draft package.
Locally absorb the draft and inspection methods of the two projects; seeIntegration Notes. Do not depend on external reference project directories, external Skill installation, or generation services. Package a consistent copy of the new-version draft_info.json and draft_content.json, the actual playback materials, editing-map.json, the offline checker, the installation tool, and the license. During generation, check the actual structure and hashes; if it fails, it must not be marked as passed; installation first verifies integrity, then checks after rebinding to the new directory, and only publishes after passing. Overwrite self-repair of user projects is prohibited.
Before delivery, run hvp jianying-check <package>. After installation, check the new draft directory again. Use hvp jianying-resources for resource lookup; do not guess resource IDs. Query commands are not automatically selected; the transitions/effects/filters selected by the plan will be written into the draft. intro/outro are currently query-only. The Jianying application, local fonts, and effect resources still need to be available on the local machine; passing the write structure does not equal passing the software's final rendering.