Before executing the specific method, read Craft scenario commands and parameters, and execute according to its object selection, session, input replacement, and result checking.
Task starting point
First read the assets, and confirm the delivery purpose, target size or duration, modification scope, and required formats. 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 vectorcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/vectorcraft-skills --skill vectorcraft-editor. The currently added skill is a local candidate; use the local companion plugin before release, and do not treat this installation command as proof of publication.
Execution steps
- Determine whether it is suitable for vectorization; do not force complex photos into large numbers of paths.
- Build shapes by color separation based on high-contrast contours, prioritizing a small number of smooth curves.
- Clean up isolated nodes, overlapping shapes, and unnecessary clipping.
- Check contour errors and detail trade-offs by scaling.
Tool implementation
Use open_file/run_command to manage graphics, and inspect_document to check objects; edit with draw_shape or run_command, save with save_file, and view with screenshot.
Read the actual tool schema first, then fill in parameters; use returned values for object or document IDs. Queried commands must be available in 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
- Do not keep auto-trace noise as fragmented paths.
- Compare key proportions and text against the original image.
- Note the redrawn and simplified parts.
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 whole page; for time-based media, inspect the start/end and key segments. For abnormal results, check the current project first to avoid repeating 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 requests rework, read this session's source project and make local modifications, preserving the accepted content.