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 materials, confirming the delivery purpose, target size or duration, scope of modification, 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 it 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 release, use the local supporting plugin, and do not treat this installation command as proof of release.
Execution steps
- Confirm the four-page reading plan: cover, product A, product B, next steps; collect the SKU-to-image mapping table and verified product facts.
- Create four pages in a new document, creating each page's title, body, and footer separately, explicitly select the returned story, and then apply paragraph styles.
- Place the two product images according to the actual returned frame IDs, maintaining proportions; verify paths, frames used, and effective PPI.
- Save and reopen, check the full text and overflow of the twelve stories, and view the PDF page by page; fix missing links, low PPI, or layout issues first.
- After the check passes, execute the packaging step separately, delivering the editable project, resources, and proof PDF. Print shop imposition, paper, bleed, and color need to be set separately according to the actual task.
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, render_page to check page by page.
Read the actual tool schema first, then fill in parameters; use return values for object or document IDs. Queried commands must be available in the current backend. Choose a new output path before saving, 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 check
- Body text does not overflow the text frame, and headings are not left alone at the bottom of a page.
- Page numbers, headers, and image captions are consistent.
- The editable project and PDF match in page count and dimensions.
Check the actual content against the user's goal, not just the process exit code. For local edits, inspect local details; for layout tasks, view the full page; for time-based media, check the start, end, and key segments. For abnormal results, check the current project first 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 the user's judgment. List only files that actually exist and have been checked. If the user later requests rework, read this session's source project and make local modifications, preserving the accepted content.