Before executing the specific method, read Craft Scenario Commands and Parameters, and execute according to object selection, session, input replacement, and result checking described therein.
Task Starting Point
First read the materials, confirm the delivery purpose, target size or duration, scope of modification, and required formats. For details that can be determined from the task and materials, adopt reasonable defaults directly; 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 companion plugin and do not treat this installation command as proof of release.
Execution Steps
- Organize the confirmed SKU, name, specification, price currency, and image correspondence table; leave missing data pending confirmation.
- Create a separate image frame for each product, place the corresponding file according to the actual returned ID, and maintain image proportions.
- Create editable text for the same SKU, explicitly select the full story, and apply the product paragraph style.
- Query the full story and the frame using the material link item by item, and check for price/image mismatches, effective resolution, and text overflow.
- Save the native project, IDML, and PDF proof, package linked materials, and verify reopening after detaching from the original path.
The example is one page with two products; it does not automatically generate master pages, CSV merging, or catalog page numbers. When the actual number of products increases, first adjust the page count and category grouping, then expand the corresponding records; do not copy prices or guess product parameters.
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.
First read the actual tool schema, then fill in the parameters; use returned values for object or document IDs. Queried commands must be available in the current backend. Before saving, choose a new output path 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 a substitute.
Result Checking
- Spot-check that each category of data matches the original table.
- Images and prices must not be mismatched; missing information must be clearly left blank.
- Unify units, currencies, and decimal formats.
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 repeatedly executing 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 content requires user judgment. List only files that actually exist and have been checked. If the user subsequently requests rework, read this session's source project and make local modifications, preserving accepted content.