Before executing the specific method, read Craft scene 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, confirm the delivery purpose, target size or duration, scope of modification, and required format. Details that can be determined from the task and assets should directly adopt reasonable defaults; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off 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
- Check the horizon, distortion, and highlights, and determine the crop first.
- Adjust overall exposure and white balance, then distinguish sky and ground.
- Use gradients or local adjustments to balance light and dark, and control clarity.
- Check depth layering and edge halos, then export.
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, then check the library; output is exported through the browser and written back to the workspace.
First read the actual tool schema, then fill in parameters; use return 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, explain the gap; do not pass off a similar name as the real thing.
Result Checking
- The sky gradient has no obvious banding.
- There are no unnatural halos on ridges and building edges.
- Preserve true color relationships and editable parameters.
Check the actual content against the user's goals, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the full page; for time-based media, inspect the start, end, and key segments. For abnormal results, check the current project first to avoid repeating 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 user judgment. List only files that actually exist and have been checked. If the user subsequently requests rework, read this source project and make local modifications, preserving accepted content.