Before executing the specific method, read Craft scenario commands and parameters, and follow 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 formats. Directly adopt reasonable defaults for details that can be determined from the task and materials; 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; before release, use the local companion plugin, and do not treat this installation command as proof of release.
Execution steps
- Determine the grid, stroke width, corner radius, and visual size.
- First complete three representative icons, unifying endpoint and corner handling.
- Extend the remaining icons using the same language, with visual compensation for circles and squares.
- Export previews at the target pixel sizes respectively.
Tool implementation
Use open_file/run_command to manage graphics, inspect_document to check objects; draw_shape or run_command to edit, save_file to save, screenshot to view.
First read the actual tool schema, then fill in the parameters; use the 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 a required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as the real thing.
Result checking
- Icons in the same group have consistent visual weight.
- Check for half-pixel blur, stroke clipping, and overly dense details.
- Each icon has its own artboard and standard naming.
Check the actual content against the user's goals, 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, 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 the user needs to decide. List only files that actually exist and have been checked. If the user later requests rework, read this source project and make local modifications, preserving the accepted content.