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 materials, and confirm the delivery purpose, target size or duration, modification scope, and required format. Details that can be determined from the task and materials should directly use reasonable defaults; only ask about missing conditions that would change the result.
When a visible editor is needed, hand it to the vectorcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/vectorcraft-skills --skill vectorcraft-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
- First confirm the information order and data sources, then choose a process, comparison, or grouping structure.
- Construct unified nodes and connecting lines, and organize the content according to the reading direction.
- Keep numbers and units as editable text, and use color to represent fixed categories.
- Check the connecting lines, labels, and legend before exporting.
Tool implementation
Use open_file/run_command to manage graphics, and inspect_document to check objects; use draw_shape or run_command to edit, save_file to save, and screenshot to view.
First read the actual tool schema, then fill in the parameters; use the returned 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. When a required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as a substitute.
Result checking
- Data encoding does not exaggerate differences.
- Connecting lines do not pass through labels, and arrow directions are consistent with the process.
- Objects in the source file can be edited independently.
Check the actual content against the user's goal, not just the process exit code. For local edits, view local details; for layout tasks, view the entire page; for time-based media, view the start, end, and key segments. For abnormal results, first check the current project to avoid repeatedly executing 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 content requires the user's 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 accepted content.