This skill handles creating and reopening vectorcraft, and organizing layers and document properties. Handoff with same-package skills is by name; it can be installed alone and used on its own, without reading sibling directories. It calls the pinned official vectorcraft-cli and preserves the native editing project.
Inputs and Deliverables
The inputs are the user-confirmed task, assets, project or objects, output directory, and scope of modification; 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, the existence of the command directory, and completion of the authoring task separately.
First Use and Common Entry Points
Locate the real directory of the current SKILL.md. Currently supports macOS arm64, Python 3.11+; the pinned CLI installs into the user data directory. When an existing task authorization covers the necessary dependencies, run this skill's installer directly, without creating a separate approval process.
Set SKILL_DIR to the directory (absolute path) of the SKILL.md actually loaded by the host. User-level installs may be located at ~/.agents/skills/vectorcraft-cli-project, project-level ones may be located at .agents/skills/vectorcraft-cli-project, and plugins may be located in their skills/vectorcraft-cli-project or the host cache directory; go by the actually loaded path, do not guess based on the current working directory, and do not search and then arbitrarily pick a duplicate version. The skill directory and the CLI's user data install directory are two separate locations.
Execution of the implementation is consolidated into the built-in vectorcraft-harness skill (installed bundled with the plugin; for standalone installation use npx skills add full-aigc-skills/vectorcraft-skills --skill vectorcraft-harness). Set HARNESS_DIR to that skill's actually loaded directory (absolute path); this skill's SKILL_DIR is only used to read its own examples/ and references/。
: "${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
In the 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 launch parameters.
Scenario Operations
Verify this scenario's inputs, native project, target objects, version, and output boundaries. Select the current command according to the scenario guide , save an independent checkpoint, then execute; after completion, reopen the native project and check the actual outputs and non-target content.
commands returns the JSON parameter catalog;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, parse object IDs in the same batch; convert outputs by extension.
First determine the units, artboard, and color mode; save natively as and reopen with info.
Native composition and source project revisions use the vectorcraft-harness skill's scripts/workflow.py; read the workflow contract, the template is in this skill's examples. Only modify authorized objects; preserve the native project and dependent assets; for derived format loss read the exchange report。
Verification and Recovery
A non-zero command exit does not count as complete; the actually saved project, export, dimensions, and media decoding need to be inspected. Timeout results are marked unknown; check the original task/project first, and do not automatically replay edits. The existing native workflow supports save-as revisions; refuse to overwrite when the corresponding project summary does not match.
On-Demand References and Handoff
- actual command evidence: observations of the pinned version, used only as routing and parameter reference; real-time results take precedence, and disabled items are not executed.
- Workflow contract: composite operations, native save, dependency collection, and revision.
- Hand off to vectorcraft-cli-setupwhen installation/diagnostics are needed, and hand off full task routing to vectorcraft-use; when skills are missing, use
npx skills add full-aigc-skills/vectorcraft-skills --skill <skill-name>. Do not load other skills through adjacent file paths.
This skill does not provide a fictional login interface; local headless does not require a cloud account. Full GUI, cross-editor fidelity, and creative quality are stated according to actual evidence.
The current runtime is a maintained version v0.2.0 based on the official 0.2.0-craft.2, published by full-aigc-skills/vectorcraft-skills ; the installation record clearly distinguishes the source of the maintained version. The SVG workflow isolates artboards according to native drawing boundaries, conservatively preserving groups, clipping, and unknown-scope dependencies.
The PDF workflow binds to the project creation date; when the creation date is missing, the first export date record is retained.pdf-export-date.json The summary is written to the delivery manifest, and this record is verified during rework; native project dates and revision history remain traceable.
Full native commands use
The current skill comes with the complete directory parameter descriptions and same-session entry points, and is not restricted by the creative template allowlist. Read the complete usage guide, and consult the command referenceas needed; each instruction has a skill route, prior 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 the current executable status, and retain return value references and step-by-step receipts; semantic errors or timeouts must not be passed off as success. Directory 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 the usage instructions. For the fixed CLI version and artifact digest, refer to the scripts/runtime.lock.json included with the vectorcraft-harness skill; 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 native gradients, global palette linkage, multiple fills, and clear active-row scenarios, use this skill'sexecutable creation/rework instructions。
For GUI tasks, you may first use this skill's included fixed desktop installation; installation, startup, and actual GUI editing are verified separately.
Complete attribution commands are listed by command family in the 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 specialized skills.
For business tasks, start with the 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 use the receipt to locate the setup entry point of the current skill itself; installation failures and native invocation failures are handled separately.
For related creative tasks, read the object selection and transformation scenarios, and verify native parameters, object context, local rework, and delivery boundaries.
For object layout, state, and path editing, first read this skill's included object operation guide, and verify authorized objects, boundary types, and original project retention requirements.
Same-target execution protection
Before calling public workflows, 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.
Operation Contract and Routing Policy
Read this skill'sinput, prerequisite state, side effects, results, recovery, and acceptance contracton demand. The examples referenced by the contract are divided into creation and rework, and are bound to the current source project and real receipts before use; the ordinary workflow and the full command plan format are handled separately. Hosts that support invoking the policy are routed by vectorcraft-use by default, and specialized skills may be invoked explicitly; other hosts dispatch according to actual capabilities.