Before executing the specific method, read Craft scene commands and parameters, and execute according to the object selection, session, input replacement, and result checking within.
Task starting point
First read the assets, confirm the delivery purpose, target size or duration, modification scope, and required format. Details that can be determined from the task and assets should directly adopt reasonable defaults; only ask about missing conditions that would change the result.
When a visible editor is needed, hand it over 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 loop duration and platform ratio, and design repeatable actions.
- Make the start and end states consistent, and check speed continuity.
- Control the colors and number of elements, balancing readability at small sizes.
- Export a loop preview and play it continuously multiple times.
Tool implementation
Use command_list to read the current Web engine commands; the id and params of command_run correspond to the actual execute interface; inspect checks the frame, save_project saves the new project path, and save_file retrieves the generated virtual file.
First read the actual tool schema, then fill in the parameters; use the return values for object or document IDs. The queried commands must be available on the current backend. Before saving, choose a new output path and keep the input. If the required algorithm, format, or command does not exist, explain the gap, and do not pass off a similar name as the real thing.
Result checking
- No flicker or jump at the seam, and no extra pause at the start or end.
- File size and color performance meet the target format.
- Keep the project and loop parameters.
Check the actual content against the user's goal, not just the process exit code. For local edits, check local details; for layout tasks, check the entire page; for time-based media, check the start, end, and key segments. For abnormal results, first check the current project to avoid repeatedly performing irreversible operations.
Delivery
Return the editable project, the actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what requires the user's judgment. List only files that actually exist and have been checked. If the user subsequently reworks it, read this source project and make local modifications, preserving the content that has already been accepted.