Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement and result checking therein.
Task starting point
First read the materials, and confirm the delivery purpose, target size or duration, modification scope and necessary 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 over to the lightcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/lightcraft-skills --skill lightcraft-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
- Group by lighting and camera, and select representative photos.
- Determine the white balance, tone and color baseline on the sample images.
- Synchronize parameters suitable for sharing, and correct exposure and cropping photo by photo.
- View the contact sheet and check for abnormal photos.
Tool implementation
Use command_run to call the actual LightCraft command interface, and inspect to query library.info. The current Web version has no real-time command_list; only call verified version commands. open_file requests import, and then check the library; output is written back to the workspace via browser export.
First read the actual tool schema, then fill in the parameters; use the return values for object or document IDs. Queried commands must be available on the current backend. Before saving, choose a new output path and keep the input. If the required algorithm, format or command does not exist, explain the gap, and do not pass off a similar name as a substitute.
Result checking
- Do not force the same white balance onto photos with different lighting.
- The style is consistent but without excessive loss of detail.
- Keep individual adjustments and the batch baseline.
Check the actual content against the user's goal, not just the process exit code. For local edits, view local details; for layout tasks, view the whole page; for time-based media, view the start and end and key segments. For abnormal results, first check the current project 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 subsequently requests rework, read this source project and modify locally, preserving the accepted content.