Task starting point
First read the material and confirm the delivery purpose, target size or duration, scope of modification, and required format. Directly adopt reasonable defaults for details that can be determined from the task and material; only ask about missing conditions that would change the result.
When a visible editor is needed, hand it to the photocraft-editor skill. Standalone installation:npx skills add full-aigc-skills/photocraft-skills --skill photocraft-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
- Distinguish hard-edged products, hair, and glass; choose paths or selection masks based on the edges.
- First build a subject mask, preserving holes, thin lines, and internal transparent areas.
- Check the edges on both black and white temporary backgrounds, shrink or feather locally; do not use global blur to hide jagged edges.
- Create a separate contact shadow layer, keep the light direction consistent, and output a transparent version and a white-background version required by the platform.
Tool implementation
Use doc_open/doc_new to open or create, doc_inspect to view layers; command_list to query actual commands, command_run to execute; doc_save to save .pcraft, doc_export to export.
First read the actual tool schema, then fill in the parameters; use the returned 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. If the required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as the real thing.
Result check
- Check whether details are missing and whether the edges retain the original background color.
- For transparent PNG, check the alpha; for the white-background version, the background sampling should meet platform requirements.
- Save the editable mask and the separate shadow layer.
Check the actual content against the user's goals, not just the process exit code. For local edits, check local details; for layout tasks, check the entire 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, the actual derived files, and a brief description: 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 source project and modify it locally, preserving the accepted content.