This skill is responsible for building geometric shapes and combining and transforming brand graphics. It hands off to skills in the same package by name and can be used when installed alone, without reading sibling directories. It invokes the pinned official vectorcraft-cli and preserves native editable projects.
Inputs and Deliverables
Inputs are the user-confirmed task, assets, project or objects, 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 creation task completion separately.
First Use and Common Entry Points
Locate the real directory of the current SKILL.md. Currently supported: macOS arm64, Python 3.11+; the pinned CLI installs into the user data directory. When 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) containing the actual SKILL.md loaded by the host. User-level installations may be located in ~/.agents/skills/vectorcraft-cli-shapes, project-level may be located in .agents/skills/vectorcraft-cli-shapes, and plugins may be located in their skills/vectorcraft-cli-shapes or the host cache directory; rely on the actual loaded path, do not guess based on the current working directory, and do not search and arbitrarily pick a duplicate version. The skill directory and the CLI's user data installation directory are two independent locations.
Execution implementation is consolidated in 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 the skill's actual 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
For CLI argv after -- , the native subcommand must come first. Installation parameters go before the separator;--runtime-home can isolate the cache. Stop when pinning 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 describes launch parameters.
Scenario Operations
Verify this scenario's inputs, native project, target objects, version, and output boundaries. According to the scenario guide , select the current command, save an independent checkpoint, then execute; after completion, reopen the native project and check the actual output and non-target content.
commands returns the JSON parameter catalog;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, parse object IDs within the same batch; convert outputs according to the extension.
Transformations keep units and center points explicit; preserve editable objects and do not automatically expand all appearances.
Native combinations and source project revisions use the vectorcraft-harness skill's scripts/workflow.py; read the workflow contract, templates are in this skill's examples. Modify only 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 completion; you need to inspect the actually 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 saving revisions; refuse to overwrite when the corresponding project summary does not match.
On-Demand References and Handoff
- Actual command evidence: pinned version observations, used only as routing and parameter references; live results take precedence, and disabled items are not executed.
- Workflow Contract: composite operations, native saving, dependency collection, and revision.
- Hand installation/diagnostics to vectorcraft-cli-setupwhen needed, and 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 via adjacent file paths.
This skill does not provide a fictitious login interface; local headless does not require a cloud account. Full GUI, cross-editor fidelity, and creative quality are stated based on actual evidence.
The current runtime is the maintained build 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 maintained build source. The SVG workflow isolates artboards according to native drawing boundaries, conservatively preserving groups, clipping, and unknown-scope dependencies.
The PDF workflow is bound 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 into the delivery checklist, and this record is verified during rework; native project dates and revision history remain traceable.
Full native commands use
The current skill includes the parameter descriptions and same-session entry points for the complete catalog, and is not subject to the creative template allowlist. Read the complete usage guide, and consult the command referenceas needed; each instruction has a skill route, prior observations, and an 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, and 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. The version and artifact digest of the pinned CLI are based on 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 does not replace 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 pinned desktop installation; installation, startup, and actual GUI editing are verified separately.
The complete attribution commands are listed by command family in the categorized usage list, and each item can be viewed through this skill's commands.py describe for parameters; the general CLI list also retains all commands not assigned to specialized skills.
Business tasks start from the scenario operation manual and are executed according to input checks, 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 related creative tasks, read 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 invoking a public workflow, read this skill's execution registration and interruption handling. In cases 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, precondition state, side effects, results, recovery and acceptance contractas needed. The examples referenced by the contract are divided into creation and rework; before use, bind the current source project and the real receipt; the normal workflow and the full command plan format are handled separately. The host that supports invoking the policy is by default routed by vectorcraft-use ; specialized skills may invoke it explicitly; other hosts dispatch according to actual capabilities.