This skill is responsible for organizing products, backgrounds, text, and layer groups, and adjusting blending and hierarchy. It hands off to skills in the same package by name, can be used when installed on its own, and does not read sibling directories. It calls the fixed maintenance build photocraft-cli and preserves native editing projects.
Inputs and Deliverables
The inputs are the user-confirmed task, materials, project or object, output directory, and modification scope; when an existing project is needed, verify the summary first. Return the actual CLI results, the saved native project, any required derived outputs, and verification records. Report installation success, command directory existence, and completion of the creative task separately.
First-Time Use and Public Entry Points
Execution is implemented and consolidated in the built-in photocraft-harness skill (installed bundled with the plugin; for standalone installation use npx skills add full-aigc-skills/photocraft-skills --skill photocraft-harness). Set HARNESS_DIR to the actual loading directory of that skill (absolute path); this skill's SKILL_DIR is only used to read its own examples/ and references/。
Locate the real directory of the current SKILL.md. Currently supports macOS arm64, Python 3.11+; the fixed CLI is installed to the user data directory. When an existing task authorization covers the necessary dependencies, directly execute this skill's installer and do not create a separate approval process.
Set SKILL_DIR to the directory (absolute path) where the host actually loaded this SKILL.md . User-level installations may be located at ~/.agents/skills/photocraft-cli-layers, project-level ones may be located at .agents/skills/photocraft-cli-layers, and plugin ones may be located in its skills/photocraft-cli-layers or the host cache directory; use the actual loading path as the standard, do not guess based on the current working directory, and do not search and then arbitrarily choose a duplicate version. The skill directory and the CLI's user data installation directory are two independent locations.
: "${SKILL_DIR:?请先设置为本 SKILL.md 的实际所在目录}"
python3 -I -B "$HARNESS_DIR/scripts/bootstrap.py"
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- --version
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- commands --json
In CLI argv, after -- , the native subcommand must come first. Installation parameters go before the separator;--runtime-home can isolate the cache. Stop when locking the artifact digest fails, the installation is corrupted, or the platform is unsupported; do not modify PATH and do not perform floating upgrades. The native help entry point is help; the launcher's own --help only explains startup parameters.
Scenario Operations
Verify this scenario's inputs, native project, target object, version, and output boundaries. According to Scenario Guide , select the current command, save an independent checkpoint, then execute; after completion, reopen the native project and check the actual outputs and non-target content.
Read params from commands --json --filter <关键词> ;run <工程> --cmd <id> --params <JSON> ... --out <新工程.pcraft>, each --params belongs to the preceding --cmd; serve/MCP can maintain a single session.
Keep products, text, and backgrounds separately editable; do not flatten the original project in advance for export.
Native composition and source project revisions use the built-in photocraft-harness skill's scripts/workflow.py; read workflow contract, and the templates are within this skill's examples. Modify only authorized objects, preserve native projects and dependency materials, and for derived format loss read exchange report。
Verification and Recovery
A non-zero command exit does not count as completion; it is necessary to inspect the actual saved project, exports, dimensions, and media decoding. Mark timed-out results as unknown, check the original task/project first, and do not automatically replay edits. Existing native workflows support save-as revisions; refuse to overwrite when the corresponding project summary does not match.
Reference and Handoff as Needed
- Actual command evidence: Fixed-version observation, for routing and parameter reference only; real-time results take priority, and disabled items are not executed.
- Workflow Contract: Composite operations, native saving, dependency collection, and revision.
- When installation/diagnostics are needed, hand off to photocraft-cli-setup, and hand off full task routing to photocraft-use; when a skill is missing, use
npx skills add full-aigc-skills/photocraft-skills --skill <skill-name>. Do not load other skills via adjacent file paths.
This skill does not provide a fictitious login interface; local headless does not require a cloud account. The PhotoCraft bridge's control-token is local application access control, which is different from cloud login. Full GUI, cross-editor fidelity, and creative quality are stated according to actual evidence.
Full Native Command Usage
The current skill comes with complete parameter descriptions of the catalog and same-session entry points, and is not restricted by the creative template whitelist. Read Complete Usage Guide, and consult Command Referenceas needed; each instruction has skill routing, prerequisite observation, and acceptance status.
python3 -I -B "$HARNESS_DIR/scripts/commands.py" list --filter QUERY
python3 -I -B "$HARNESS_DIR/scripts/commands.py" describe COMMAND_ID
python3 -I -B "$HARNESS_DIR/scripts/commands.py" run "$SKILL_DIR/examples/commands-advanced.json" --output /absolute/new-command-result
Before executing a new entry point, check the real registry and current executable status, retain return value references and step-by-step receipts; do not pass off semantic errors or timeouts as success. Catalog coverage and direct native use do not mean that all instructions, GUI, delivery, or Art orchestration have been accepted.
For the full workflow command gateway, see Usage Instructions. For the fixed CLI version and artifact digest, refer to the built-in photocraft-harness skill's scripts/runtime.lock.json ; the skill package version is based on the corresponding release tag. Independent installation re-verification and full command-by-command acceptance are recorded separately, and release is not a substitute for acceptance.
For editable local adjustments and source rework, see Mask Adjustment Usage Instructions; the paired plan is in this skill's examples, with source candidates and fixed installation evidence kept separate.
For GUI tasks, you may first use this skill's built-in Fixed Desktop Installation; installation, startup, and actual GUI editing are verified separately.
The full attribution commands are listed by command family in Categorized Usage List, and each item's parameters can be viewed through this skill's commands.py describe ; the general CLI list also retains all commands not assigned to dedicated skills.
For business tasks, start from Scenario Operation Manual , and execute according to input checks, template adaptation, native delivery, local rework, and result verification.
If installation fails, read First-Use Diagnostics, and locate the current skill's own setup entry point based on the receipt; handle installation failure and native call failure separately.
For product local filters, background blur, and output sharpening tasks, read Filter Scenarios, distinguish editable filters from baked pixels, and verify selections, layers, and non-target content.
Brush presets and layer view scenarios: see Usage Guide and Full Plan. First verify names and layer context, and clarify the impact of deleting presets within a group.
Same-Target Execution Protection
Before invoking a public workflow, read this skill's Execution Registration and Interruption Handling. In case of contention or unknown status, do not delete the registration, automatically replay, or switch targets to bypass verification.
Before delivery, moving packages, or source project rework, verify all files and exchange identities according to the Delivery Integrity checklist; read-only checks do not require installing a runtime.
Scenario Contract and Routing
Per scenario contract , verify inputs, goals and protection scope, recovery, and acceptance. For a complete task, select the shortest skill chain by name; when the known result is unclear, first verify the original task and do not replay. For explicit intent, you may use the built-in photocraft-harness skill's scripts/route.py INTENT query entry point; this is a contract query and does not prove that host model dispatch has passed.
PSD delivery requires clearly defined necessary properties; observed loss/degradation and unknown necessary items will block success. When the user explicitly accepts, record it according to the same source version and actual observation summary, and do not accept automatically; see this skill'sPSD exchange and acceptance gate。
When flat export requires clearly defined color/ICC/transparency requirements or preservation of externally generated asset provenance, read this skill's flat export and provenance contract。
For runtime/backend identity and capability drift issues, read this skill's capability snapshot and rejection contract。
Continuous tasks and instance reuse
When the same user task is continuously checked, edited, saved, reopened, and reworked, use this skill's task-level session and the built-in photocraft-harness skill's scripts/task_session.py, maintaining the same foreground process and input handle. After failure/unknown, first verify the original receipt and project, and do not start a replacement instance to replay.