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 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; before release, use the local companion plugin, and do not treat this installation command as proof of release.
Execution Steps
- Clarify the brand text and usage size, and first construct a concise geometric relationship.
- Use boolean operations to form the main outline and clean up excess nodes.
- Create horizontal, vertical, monochrome, and reversed versions, and keep editable copies of the text.
- Check legibility at small sizes and against light and dark backgrounds.
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. Queried commands must be available on the current backend. Choose a new output path before saving and preserve the input. When the required algorithm, format, or command does not exist, state the gap, and do not pass off a similar name as a substitute.
Result Checking
- Paths are closed, with no excess fragments and no unexpected holes.
- Thin lines and negative space remain distinguishable at the minimum size.
- Deliver the source file and SVG/PNG variants; save the font-outlined version separately.
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 entire page; for time-based media, inspect 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 description: what was modified, 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 later requests rework, read this source project and make local modifications, preserving the accepted content.