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 assets and confirm the delivery purpose, target size or duration, modification scope, and required format. 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 designcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/designcraft-skills --skill designcraft-editor. The currently added skill is a local candidate; before publishing, use the local companion plugin and do not treat this installation command as proof of publication.
Execution steps
- Confirm the finished product's millimeter dimensions, placement method, and reading distance; collect all event facts, the confirmed registration URL, and the key visual, keeping missing information as pending confirmation.
- Create a new A3 document, separately create text frames for the title, theme, details, entry point, and notes, and apply editable styles according to the actual returned story IDs.
- Place the key visual into the specified frame while preserving aspect ratio; set up a clickable entry point and a native QR code using the same URL, preserving white background clearance.
- Save and reopen, check the full text of the five stories, overflow, image links, and effective PPI; independently verify the PDF finished size and click targets.
- Actually decode the exported PNG and PDF render image, verify the payload matches the confirmed URL, and check the reading effect at the finished product's aspect ratio; only package separately after passing.
Tool implementation
Use open_document/new_document to manage documents, inspect_document and get_story to verify content; execute to run commands, save_document to save, and render_page to check page by page.
Read the actual tool schema first, then fill in parameters; use 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 a required algorithm, format, or command does not exist, state the gap; do not substitute a similar name.
Result checking
- Time and location are complete and easy to read.
- The QR code comes from real input and can be scanned; do not draw a fake QR code.
- Bleed and safe margins are set according to the print shop's requirements.
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 full 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, actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what needs 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 accepted content.