This skill is responsible for modifying brand colors, fill and stroke, transparency, and appearance variants. It hands off to skills in the same package by name, can be installed and used on its own, and does not read sibling directories. It invokes the fixed official vectorcraft-cli and preserves the native editing project.
Inputs and deliverables
The inputs are the user-confirmed task, assets, project or object, output directory, and modification scope; when an existing project is required, 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-time use and public entry point
Locate the real directory of the current SKILL.md. Currently supports macOS arm64, Python 3.11+; the fixed CLI installs to the user data directory. When an existing task authorization covers the necessary dependencies, run this skill's installer directly and do not create a separate approval process.
Set SKILL_DIR to the directory (absolute path) of the actual SKILL.md loaded by the host. User-level installations may be located in ~/.agents/skills/vectorcraft-cli-appearance, project-level installations may be located in .agents/skills/vectorcraft-cli-appearance, and plugins may be located in their skills/vectorcraft-cli-appearance or the host cache directory; use the actual loaded path as the basis, 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 user data installation directory are two independent locations.
Execution 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 the actual loaded directory of that skill (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
CLI argv after -- , the native subcommand must come first. Install 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 describes startup 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 output 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.
Change colors by stable object/palette ID; preserve unrelated objects and distinguish format differences between RGB/CMYK and visual effects.
Native composition and source project revisions use the vectorcraft-harness skill's scripts/workflow.py; read the workflow contract, and the template is in this skill's examples. Modify only authorized objects, preserve the native project and dependent assets, and for derived format losses read the exchange report。
Verification and recovery
A non-zero command exit does not count as completion; you need 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 revision; 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 priority, and disabled items are not executed.
- Workflow Contract:Combined operations, native saving, dependency collection, and revisions.
- When installation/diagnostics are needed, hand off to vectorcraft-cli-setup, full task routing is handed off to vectorcraft-use; when a skill is 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 according to actual evidence.
Brand color tokens
Use the native global color palette to associate the Logo, wordmark, and artboard variants, then update with swatch.edit ; generate a Save As revision based on the actual palette receipt names and original project summary. Read the brand token guidewithin this skill; examples are examples/brand-token-assets.json。
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 ; installation records clearly distinguish 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 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 to 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 parameter descriptions for the complete catalog and a same-session entry point, and is not restricted by the creative template whitelist. Read the complete usage guide, and consult the command referenceas needed; 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 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 commands, GUI, delivery, or Art orchestration have been accepted.
For the complete workflow command gateway, see usage instructions. The version and artifact digest of the fixed 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 is not a substitute for acceptance.
For native gradients, global palette linkage, multiple fills, and explicit active row scenarios, use this skill'sexecutable creation/rework instructions。
For GUI tasks, you may first use the fixed desktop installationincluded with this skill; 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 can be viewed through this skill's commands.py describe ; 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.
If installation fails, read the first-use diagnostics, and locate the setup entry point of the current skill itself based on the receipt; 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.
Same-target execution protection
Before invoking the public workflow, read this skill's execution registration and interruption handling. In a contention or unknown state, 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 contracton demand. The examples referenced by the contract are divided into creation and rework; bind the current source project and real receipt before use; handle the ordinary workflow and the full command plan format separately. A host that supports the invocation policy is by default routed by vectorcraft-use ; specialized skills may invoke it explicitly; other hosts dispatch according to actual capabilities.