---
name: illustrator-vector-art
description: Plan or build an editable Illustrator illustration from a supplied raster. Staged Image Trace and semantic bundle construction require a separately available Python/JSX runtime; the local Illustrator MCP alone supports direct native paths, shapes, layers and export for simpler work. Use for staged vectorization, screen-recorded assembly, or separately editable boundaries when the required execution path is verified. Exclude layout changes, translation, export-only work and demonstrations requiring manual Pen drawing.
---

# Visible vector illustration in Illustrator

Build the requested illustration from the supplied source, preserving its composition and observed contacts. Use native Image Trace for appearance and constructed boundaries when separate material or shape edits are required. Tracing can simplify paint and fine detail; named layers alone do not establish accurate geometry or useful editability.

## Local MCP capability gate

The installed Illustrator package serves this entry through `ai_get_skill`; it does not bundle the Python builders or execute Image Trace. Read `ai_guide`, `ai_catalog`, and `ai_document_info` before editing. Query `ai_catalog({operation:"<name>"})` for exact arguments and call only listed operations through `ai_do({operation:"<name>", args:{...}})`. `ai_preview` can help verify the current artboard. A registered tool or loaded skill does not prove Illustrator is connected; confirm an actual document read.

The current native catalog can create/open documents, add editable shapes and Bézier paths, manage layers/items, save an AI file to a NEW path, and export SVG/PNG. It has no Image Trace, raster region preparation, arbitrary JSX/AppleScript execution, or Python helper runner. Those steps require the separately verified runtime described below. If the task is a simple vector rebuild with observable boundaries, the direct `ai_do` path operations may suffice: derive coordinates from the current source, build a small representative region, inspect it, then continue only if the result meets the requested editability and appearance. Do not label that route an Image Trace or a staged reveal. Complex source-faithful tracing remains pending without the helper runtime or another observed Illustrator control path.

## Inputs and scope

Use the source image, intended edits, recording preferences and output location already provided. Ask for an unavailable source or a decision that materially changes the result. Otherwise choose a project output folder and a meaningful stage count. User-specified stage counts and pauses override defaults; do not split an object arbitrarily to inflate the demonstration.

The staged-trace and semantic-bundle branches require Adobe Illustrator, an authorized application-control mechanism and a compatible existing automation runtime. This Markdown package does not bundle executable helpers. Before preparing those artifacts, read [Runtime and recovery](references/runtime.md) to verify the selected runtime and its dependencies. An unavailable runtime permits planning or a limited direct native build where suitable, not a claim that the staged or semantic automation ran.

Create a new document and output directory, preserving sources and unrelated documents. Complete only the requested illustration or batch. Skill review alone does not authorize an illustration demonstration. For a script-only request, prepare the requested task bundle without launching Illustrator and state that native execution remains unverified.

## Select and prepare the workflow

Choose staged trace when the purpose is a sequential reveal of source regions into named vector layers. Read [Staged trace](references/staged-trace.md) only for that branch. Choose semantic construction when the requested result needs independently selectable materials, coordinated boundaries or controlled overlap. Read [Semantic construction](references/semantic-construction.md) only for that branch. Both branches require the external runtime. A simple direct native build is a separate limited route, not evidence that either branch executed. A request requiring manual Pen operations needs a different construction method; do not present tracing as that demonstration.

Inspect the source at full view and in critical crops before planning geometry. Preserve visible object counts, thin connections and foreground contacts. Derive contours from the current source rather than reusing a previous illustration's coordinates. When extending semantic construction to an unfamiliar complex scene, validate a representative difficult crop before assembling the whole image; a crop result does not certify the rest of the composition.

## Execute and complete

Prepare the selected branch, inspect its intermediate geometry, and run the verified native bundle visibly using the runtime reference when it is available. For a limited direct `ai_do` build, inspect the actual item and layer structure after each meaningful stage. Only one operator controls Illustrator at a time. Show meaningful construction changes with requested pauses only when the selected control path can do so; distinguish preparation, tracing, redraw, saving and verification when reporting progress or timing.

Before claiming completion, read [Verification and delivery](references/verification.md). Reopen the saved native AI, inspect its actual structure and full composition, and test the requested edits on copies. Deliver the AI and relevant geometry or proof artifacts with a concise statement of verified behavior and remaining limitations. Keep historical test results outside this reusable skill and never treat a previous run as verification of the current output.