This skill is responsible for setting up the logo and brand text, handling fonts, and exporting outlines. 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 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 scope of modification; when an existing project is needed, verify the summary first. Return the actual CLI results, the saved native project, the required derived outputs, and the verification records. Report installation success, command directory existence, and creative task completion separately.
First Use and Public Entry Point
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, execute this skill's installer directly without creating a separate approval process.
Set SKILL_DIR to the directory (absolute path) where the host actually loads this SKILL.md . User-level installations may be located in ~/.agents/skills/vectorcraft-cli-text, project-level ones may be located in .agents/skills/vectorcraft-cli-text, and plugins may be located in their skills/vectorcraft-cli-text or the host cache directory; use the actual loaded 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.
Execution is converged 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 directory (absolute path) where that skill is actually loaded; 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 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 the startup parameters.
Scenario Operations
Verify this scenario's inputs, native project, target object, version, and output boundaries. According to the 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.
commands returns a JSON parameter catalog;run --in <工程> --cmd <id> --params <JSON> ... --export <新工程.vectorcraft>, resolve object IDs within the same batch; convert outputs by extension.
Project text remains editable; outline-text is used only on the specified exchange copy, and the loss of font editability is recorded.
Native composition and source project revisions use the scripts/workflow.pyof the vectorcraft-harness skill; read the workflow contract, and templates are within this skill's examples. Modify only authorized objects, preserve the native project and dependent assets, and for derived format loss read the exchange report。
Verification and Recovery
A non-zero command exit does not count as completion; it is necessary to view the actually saved project, exports, dimensions, and media decoding. Mark timeout 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.
On-Demand References and Handoff
- Actual command evidence: Fixed-version observations, for routing and parameter reference only; real-time results take precedence, disabled items are not executed.
- Workflow Contract: Composite operations, native saving, dependency collection, and revisions.
- Hand installation/diagnostics to vectorcraft-cli-setupwhen needed, hand complete 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 fabricated login interface; local headless does not require a cloud account. Complete GUI, cross-editor fidelity, and creative quality are stated according to actual evidence.
Chinese Text and Point Revisions
This skill comes with Chinese title and independent footer examples, supporting explicit object text.setText original project revisions; see this skill's Chinese Text Guide. Whole-paragraph replacement preserves the first paragraph's style; multi-style rich text merge boundaries must be disclosed.
The current runtime is a maintained build v0.2.0 based on the official 0.2.0-craft.2, published by full-aigc-skills/vectorcraft-skills ; installation records clearly distinguish the maintained build's source. The SVG workflow isolates the artboard 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 's summary is written into the delivery checklist, and this record is verified during rework; native project dates and revision history remain traceable.
Complete Native Command Usage
The current skill comes with parameter descriptions and same-session entrances for the complete catalog, not subject to creative template whitelist restrictions. Read Complete Usage Guide, query 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 entrance, check the real registry and current executable status, retaining return value references and step-by-step receipts; semantic errors or timeouts are not passed off as success. Catalog coverage and direct native use do not equal acceptance of all instructions, GUI, deliverables, or Art orchestration.
See the complete workflow command gateway in Usage Instructions. The fixed CLI's version and artifact summaries are based on the vectorcraft-harness skill's own scripts/runtime.lock.json ; skill package versions are based on the corresponding release tags. Independent installation re-verification and full per-command acceptance are recorded separately; release is not substituted for acceptance.
For native gradients, global palette linkage, multiple fills, and explicit active row scenarios, use this skill'sExecutable Creation/Rework Instructions。
GUI tasks can first use this skill's own 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 can be viewed via 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 , executed according to input checking, template adaptation, native delivery, partial rework, and result verification.
When installation fails, read First-Use Diagnostics, and locate the current skill's own setup entrance according to the receipt; 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, partial rework, and delivery boundaries.
Same-target execution protection
Before invoking a public workflow, read this skill's execution registration and interruption handling. Competing or unknown states must not delete registrations, 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 receipts before use; ordinary workflows and complete command plan formats are handled separately. Hosts that support the invocation policy are by default routed by vectorcraft-use , and specialized skills may invoke it explicitly; other hosts dispatch according to actual capabilities.