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 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 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; use the local companion plugin before release, and do not treat this installation command as proof of publication.
Execution steps
- In the original project, perform a read-only inventory of fonts, links, effective PPI, full text, and frame boundaries, and record all issues.
- According to the approved plan, use actual asset IDs to fix missing links/low PPI, only expand confirmed text frames while preserving font size, full text, and non-target objects.
- Set the confirmed bleed and recheck using the same thresholds; stop export if errors or target issues remain unresolved.
- Separately export a normal PDF with bleed using explicit parameters, and verify the actual page boxes, page count, and text and images; preserve the native project and linked package.
The CLI must be divided into three stages: inspect, repair, and export; export only after checking the recheck report. A zero-error preflight does not equal PDF/X or print certification.
Tool implementation
Use open_document/new_document to manage documents, inspect_document and get_story to verify content; execute runs commands, save_document saves, render_page checks page by page.
First read the actual tool schema, then fill in parameters; use return 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. 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
- Do not claim a normal PDF is compliant PDF/X.
- Reopen the exported file to confirm page boxes and page count.
- List spot colors, overprinting, and color conversions that have not yet been verified.
Check the actual content against user goals, not just process exit codes. For local edits, inspect local details; for layout tasks, inspect the whole 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 derivative 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 reworks it, read this source project and make local modifications, preserving accepted content.