This skill is the VectorCraft skill suite'ssole execution implementation: first-time installation, native command invocation, workflow orchestration, desktop bridging, and delivery verification all converge in this directory scripts/ .vectorcraft-use、vectorcraft-cli and the various domain skills are thin documentation skills—they provide scenario guidance, plan examples, and reference contracts, while actual execution always goes through this skill's entry points.Before executing any VectorCraft script, first set HARNESS_DIR to the directory where this SKILL.md resides (the absolute path actually loaded by the host); do not assume the current working directory is the skill directory. A user-level installation may be located at ~/.agents/skills/vectorcraft-harness, a project-level one may be located at .agents/skills/vectorcraft-harness, and a plugin may be located in its skills/vectorcraft-harness or the host cache directory; the path actually loaded by the host prevails. In domain skill documentation, SKILL_DIR refers to the domain skill's own directory (used to read its examples/、references/), which is a different location from this harness.
Entry points
| Entry point | Purpose |
|---|---|
scripts/bootstrap.py |
First-use installer: uses only the standard library to install the pinned official CLI (runtime.lock.json fixed version and digest), returns JSON executable。 |
scripts/cli.py |
Public CLI channel: invokes the pinned binary by argv;-- is followed by native subcommands. |
scripts/commands.py |
Native command single-skill entry:list / describe / run, parameter descriptions, real-time pre-checks, same-session invocation, and failure receipts. |
scripts/workflow.py |
Native vector operation assistant: independent session, restricted read/write directories, and immutable revision delivery; multi-artboard export and targeted recoloring. |
scripts/desktop.py |
Desktop bridge: installs the desktop app from the pinned official DMG and executes desktop plans; separate from the CLI cache. |
The remaining scripts/ files are internal dependencies of the above entry points (security boundary, session, and contract modules) and are not invoked separately.
Usage
Scenario guidance, plans, and example files are taken from the corresponding domain skill directory (SKILL_DIR/examples/、SKILL_DIR/references/); execution paths always use this directory HARNESS_DIR/scripts/。
First-time installation (when no CLI is preinstalled; the installation scope is the user data directory and does not require sudo):
python3 -I -B "$HARNESS_DIR/scripts/bootstrap.py"
The installer returns JSON executable, which is subsequently used as the first element of argv. The currently pinned platform is macOS arm64; unsupported platforms return unsupported_platform; do not install artifacts for other platforms. The default installation location is ~/.local/share/craft-runtimes, and it can be specified with --runtime-home or CRAFT_RUNTIME_HOME ;--archive accepts an already-downloaded pinned ZIP, but does not skip the digest check.
Direct native command connection and command catalog query (cli.py's native subcommands must be placed after -- ; commands.py output is always JSON):
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- --version
python3 -I -B "$HARNESS_DIR/scripts/cli.py" -- commands
python3 -I -B "$HARNESS_DIR/scripts/commands.py" list --filter QUERY
python3 -I -B "$HARNESS_DIR/scripts/commands.py" describe COMMAND_ID
If using MCP, explicitly select mcp --headlessto avoid automatically connecting by default to the desktop document currently in use. For desktop installation and GUI plans, see the domain skill's [Pinned Desktop Installation] reference; the entry point is scripts/desktop.py。
Relationship between domain skills and this harness
vectorcraft-use: complete task routing and delivery contract; execution still goes through this harness.vectorcraft-cliWith each scenario skill (setup/project/paths/shapes/boolean/text/appearance/artboards/assets/export/selection): scenario knowledge and parameter contracts; execution still goes through this harness.- When domain skill documents reference scripts, they are always written as
$HARNESS_DIR/scripts/<入口>；references/The execution contract JSON (command-coverage, native-command-snapshot) in this skill remains byte-identical withvectorcraft-use, and each domain skill retains its own scenario reference. - Before delivery, reopen the project and verify each artboard and export scope; read-only checks do not require installing a runtime.
Current scope
The version and artifact digest of the pinned CLI are based on this 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, and release is not used as a substitute for acceptance. Directory coverage and direct native use do not mean that all instructions, GUI, delivery, or Art orchestration have been accepted.