This skill is responsible for creating and modifying text layers, fonts, paragraphs, and layouts. It hands off to skills in the same package by name, can be used when installed standalone, and does not read sibling directories. It invokes the fixed maintained version photocraft-cli, preserving the native editing project.
Inputs and deliverables
Inputs are the user-confirmed task, materials, project or objects, output directory, and modification scope; when an existing project is needed, first verify the summary. Return the actual CLI results, the saved native project, the required derived outputs, and the verification record. Report installation success, command directory existence, and completion of the creation task separately.
First-time use and public entry point
Converge execution on 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 directory where that skill is actually loaded (absolute path); this skill's SKILL_DIR is used only 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 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) containing the actual SKILL.md loaded by the host. User-level installations may be located in ~/.agents/skills/photocraft-cli-text, project-level ones may be located in .agents/skills/photocraft-cli-text, and plugins may be located in their skills/photocraft-cli-text or the host cache directory; use the actual loaded path, do not guess based on the current working directory, and do not search and then arbitrarily select 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
CLI argv is after -- , and the native subcommand must be placed 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 objects, version, and output boundaries. According to scenario guide , select the current command, save an independent checkpoint, and then execute; after completion, reopen the native project and check the actual output 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 text as independent layers; verify fonts, line breaks, overflow, and glyphs, and report substitutions for missing fonts.
Use the built-in photocraft-harness skill's scripts/workflow.pyfor native composition and source project revisions; read workflow contract, templates are within this skill's examples. Only modify authorized objects, preserve the native project and dependency materials, and for derived format loss read exchange report。
Verification and recovery
A non-zero command exit does not count as completion; the actual saved project, exports, dimensions, and media decoding need to be inspected. Mark timeout results as unknown, first check the original task/project, and do not automatically replay edits. Existing native workflows support saving revisions; refuse to overwrite when the corresponding project summary does not match.
On-demand references and handoff
- actual command evidence: Fixed-version observations, for routing and parameter reference only; real-time results take precedence, and disabled items are not executed.
- Workflow Contract: composite operations, native saving, dependency collection, and revision.
- Hand off to photocraft-cli-setupwhen installation/diagnostics require it, 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, different from cloud login. Full GUI, cross-editor fidelity, and creative quality are stated based on actual evidence.
Local modifications to the source project may declare protectedRegions, and before publishing and delivery, check pixels in non-target areas; see this skill'sprotected area contract. When no area is declared, do not automatically infer the protected scope.
Complete native command usage
The current skill includes the parameter descriptions for the complete catalog and the same-session entry point, and is not subject to the creative template whitelist. Read complete usage guide, and consult as needed command reference; each instruction has a skill route, prerequisite observations, 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 the current executable status, retain return value references and step-by-step receipts; semantic errors or timeouts must not be passed off as success. Catalog coverage and direct native use do not mean that all instructions, GUI, delivery, or Art orchestration have been accepted.
For the complete workflow command gateway, see usage instructions. For the fixed CLI's 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; release does not replace acceptance.
For editable local adjustments and source rework, see mask adjustment usage instructions; paired plans are 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.
Complete attribution commands are listed by command family in categorized usage list, and each item can be viewed through this skill's commands.py describe to see parameters; the general CLI list also retains all commands not assigned to specialized skills.
Business tasks start from scenario operation manual , and are executed through input checking, template adaptation, native delivery, local rework, and result verification.
When installation fails, read first-use diagnostics, and use the receipt to locate the current skill's own setup entry point; installation failures and native invocation failures are handled separately.
For product local filter, background blur, and output sharpening tasks, read filter scenarios, distinguish editable filters from baked pixels, and verify selections, layers, and non-target content.
Same-target execution protection
Before invoking public workflows, read this skill's execution registration and interruption handling. For competing or unknown states, do not delete registrations, 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 completeness checklist; read-only checks do not require installing a runtime.
Scenario Contract and Routing
According to Scenario Contract , verify inputs, targets and protection scope, recovery, and acceptance. For a complete task, select the shortest skill chain by name; when a 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 features; observed loss/degradation and unknown necessary items will prevent 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 retention of the source of externally generated assets, 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 substitute instance to replay.