Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking described therein.
Task Starting Point
First read the assets, confirm the delivery purpose, target size or duration, scope of modification, and required format. Directly adopt reasonable defaults for details that can be determined from the task and assets; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off to the effectcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/effectcraft-skills --skill effectcraft-editor. The currently added skill is a local candidate; before release, use the local companion plugin, and do not treat this installation command as proof of release.
Execution Steps
- Determine the safe area and maximum text length, and do static layout first.
- Layer the background bar, name, and title, and establish a consistent entrance and exit rhythm.
- Verify size and line wrapping with the longest name.
- Generate variants and check the transparent output.
Specific Plan with Backing Plate and Transparent Entrance/Exit
According toLower Third Production ManualandOrdered Command Plan, create an editable backing plate, name, and title, and check the fade-in, hold, and fade-out on the last valid frame. The manual explains the differences between paragraph boxes and point text anchors, trial layout for long names, CLI/MCP invocation, and transparent delivery boundaries; it deepens this scenario without increasing the scenario count.
Tool Implementation
Use command_list to read the current Web engine commands; command_run's id and params correspond to the actual execute interface; inspect checks the frame, save_project saves a new project path, and save_file retrieves generated virtual files.
Read the actual tool schema first, then fill in the parameters; use return values for object or document IDs. Queried commands must be available on the current backend. Choose a new output path before saving, and preserve the input. If the required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as the real thing.
Result Checking
- Text does not overflow, and name and title are not reversed.
- Key text stays on screen long enough.
- Output matches the video frame rate and aspect ratio.
Check the actual content against the user's goal, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the full page; for time-based media, inspect the start, end, and key segments. For abnormal results, check the current project first to avoid repeatedly performing irreversible operations.
Delivery
Return the editable project, actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what requires user judgment. List only files that actually exist and have been checked. If the user subsequently requests rework, read this source project and make local modifications, preserving the content that has already been accepted.