Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking therein.
Task Starting Point
First read the materials, 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 adopt reasonable defaults; only ask about missing conditions that would change the result.
When a visible editor is needed, hand it over to the cadcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/cadcraft-skills --skill cadcraft-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
- Count entity types, layers, and invisible objects, and save a copy first.
- Map layers by purpose such as walls, equipment, and annotations, and keep the original layer mapping table.
- Unify linetypes and colors; only delete entities that have been verified as completely duplicate.
- Restore the full drawing view and check whether hidden layers contain necessary content.
Tool Implementation
Use open/new_drawing to open or create, query_entities to verify geometry; execute to run commands, save to save, render to preview.
First read the actual tool schema, then fill in the parameters; use return values for object or document IDs. Queried commands must be available in the current backend. Before saving, choose a new output path and keep the input. When the required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as the real thing.
Result Checking
- Changes in entity counts have clear reasons.
- Frozen layers and locked layers are not mistakenly deleted, and annotations still point to the correct objects.
- Deliver the organized project and layer correspondence documentation.
Check the actual content against the user's goals, 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, actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what requires user 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 content that has already been accepted.