AutoGineer
Generated banner for Adobe Illustrator Integrations
Generated logo for Adobe Illustrator Integrations

Adobe Illustrator Integrations

GitHubOfficialFirst committed by jhaugaDistributed by GitHub

  • Skill
  • Tool integration
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Build, debug, package, and document Adobe Illustrator integrations: CEP extension panels, C++ SDK plug-ins (.aip), the coming UXP plugins, MCP servers that drive Illustrator, computer-use automation, and OS scripts (batch, PowerShell, bash, AppleScript) that run ExtendScript in Illustrator. Use when creating or fixing an Illustrator extension or plug-in, choosing between a script, extension, or plug-in, connecting an AI tool to Illustrator, automating Illustrator from the command line, or writing install and usage docs for an Illustrator tool someone will publish. Pairs with adobe-illustrator-scripting for the ExtendScript DOM.
— the description by jhauga

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides comprehensive guidance for extending Adobe Illustrator. It covers the full lifecycle of integration development, from choosing the right delivery method—such as CEP extension panels, native C++ plug-ins, or external automation via MCP servers and OS scripts—to packaging and documentation. It emphasizes maintaining a clean separation between the user interface and the core ExtendScript logic to ensure future compatibility with emerging technologies like UXP.

What it does

  • Guides the selection of the appropriate integration tier for Illustrator features.
  • Provides patterns for building CEP extension panels and native C++ (.aip) plug-ins.
  • Details methods for running Illustrator scripts from external environments like PowerShell, bash, or Python.
  • Supports the design of MCP servers to enable AI-driven interaction with Illustrator.
  • Outlines best practices for packaging, signing, and documenting Illustrator tools for distribution.
  • Offers strategies for maintaining compatibility across different Illustrator versions and operating systems.

When to use it

  • When you need to create a custom panel or tool for Adobe Illustrator.
  • When automating Illustrator tasks from an external command-line tool or AI agent.
  • When deciding between a script, a CEP extension, or a native C++ plug-in.
  • When preparing documentation for an Illustrator tool or extension you intend to publish.
  • When debugging communication between an external process and the Illustrator host application.

Advantages

  • Promotes a modular architecture that simplifies future migration to UXP.
  • Provides clear, version-aware guidance for managing the transition away from CEP.
  • Standardizes the approach to external automation and parameter passing.
  • Encourages safe development practices like working on document copies and avoiding hardcoded secrets.

Usage examples

“How do I trigger an Illustrator script from a Python script on Windows?”
The agent provides a code snippet using win32com.client to dispatch the Illustrator.Application and execute the script via DoJavaScriptFile.
“What is the recommended folder structure for a new CEP extension?”
The agent outlines the standard directory layout, including CSXS/manifest.xml, index.html, and the required jsx/host.jsx file.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/adobe-illustrator-integrations/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip adobe-illustrator-integrations.zip -d .agents/skills

Documentation by jhauga

Adobe Illustrator Integrations

Guidance for everything that sits around an Illustrator script: the panel a user clicks, the native plug-in that adds a tool, the command line or AI agent that starts Illustrator work from outside, and the documentation that ships with it. For the Illustrator DOM itself (documents, layers, paths, colors, exports), use the adobe-illustrator-scripting skill.

When to Use This Skill

  • Choosing how to deliver an Illustrator feature: a script, a CEP extension, a C++ plug-in, a UXP plugin, an MCP server, or an OS automation script

  • Building or fixing a CEP extension panel (HTML, JavaScript, and an ExtendScript host)

  • Building or fixing a C++ plug-in (.aip) with the Illustrator SDK

  • Running .jsx scripts from batch, PowerShell, bash, Python, or AppleScript, including passing parameters and reading results

  • Building or reviewing an MCP server that lets an AI tool drive Illustrator

  • Working in Illustrator through a computer-use tool when no scripting route exists

  • Writing step-by-step instructions people follow by hand, or install and usage docs for an asset, script, extension, or plug-in someone will publish

  • Organizing the files of an Illustrator project (sources, linked assets, exports, docs) so automation can find them

Script, Extension, or Plug-in

Adobe's own terms:

  • A script is ExtendScript (.jsx), AppleScript, or VBScript run against Illustrator's scripting object model. It has no persistent UI beyond ScriptUI dialogs.

  • An extension is a CEP panel: an HTML and JavaScript UI hosted in Illustrator that calls ExtendScript through CSInterface.evalScript.

  • A plug-in is native code built with the Illustrator C++ SDK (.aip). In apps that already run UXP (Photoshop, InDesign, Premiere Pro), "plugin" also means a UXP plugin; Illustrator UXP plugins are not public yet.

OptionWhat it isUIInstalls toShips asPick it when
Manual instructionsSteps a person followsIllustrator's ownNothingA documentThe task is rare, or needs judgment at every step
ExtendScript script.jsx run in IllustratorOptional ScriptUI dialogPresets/<locale>/Scripts or anywhere (File > Scripts > Other Script).jsx fileOne action, batch work, or a step another tool calls
CEP extensionHTML panel plus ExtendScript hostDockable panelCEP extensions folderSigned .zxpUsers need a persistent panel with controls and previews
C++ plug-inNative .aip from the Illustrator SDKTools, menus, notifiers, native dialogsPlug-ins folder or the Additional Plug-ins Folder.aip per OS and major versionYou need a custom tool, live effects, speed, or events scripts cannot reach
UXP pluginModern JavaScript plugin modelPanels and dialogsThrough Creative Cloud.ccxPlan for it; Illustrator's public beta is due by Spring 2027
MCP serverA process an AI tool calls, which runs scripts in IllustratorThe AI tool's chatThe AI tool's MCP configA package or repoAn agent should create or inspect artwork through tools
OS automationBatch, PowerShell, bash, or AppleScript that starts scriptsNoneAnywhereScript filesIllustrator work is one step of a larger pipeline

Start with the lowest tier that meets the need. A script that works is the core of every higher tier: a CEP panel, an MCP tool, and an OS script all end up calling ExtendScript.

Extensibility Timeline

From Adobe's announcement "Investing in the future of Creative Cloud extensibility" (blog.developer.adobe.com, September 2026):

  • Illustrator UXP plugins: public beta by Spring 2027.

  • CEP in Illustrator, After Effects, and Media Encoder: the Adobe Marketplace stops accepting new CEP submissions in December 2028, and CEP is disabled by default from December 2028.

  • CEP leaves these apps from December 2029, with at least two years between each app's UXP public beta and CEP's removal from new versions.

  • ExtendScript is not affected by the transition.

So a CEP extension built today has a working life of a few years. Keep its logic in plain ExtendScript files the panel calls, which carry over to a UXP plugin or an MCP server unchanged.

Workflow

  1. Scope: what the user does, which Illustrator versions and OSes it must run on, and who installs it.

  2. Pick the tier from the table above.

  3. Write the ExtendScript core first with the adobe-illustrator-scripting skill, as functions that take a plain settings object and return a result string, so any front end can call them.

  4. Add the front end:

  5. Test inside Illustrator on a copy of a real document: run every option, export a PNG of the result, and compare it with the expected output.

  6. Package: a signed ZXP for CEP, a per-OS .aip for plug-ins, a versioned folder or package for scripts and servers.

  7. Document with references/publishing-docs.md: requirements, compatibility, install steps per OS, a walkthrough with screenshots, a GIF, troubleshooting, and a changelog.

Running a Script From Outside Illustrator

PlatformRouteNotes
WindowsCOM Illustrator.ApplicationDoJavaScriptFile(JavaScriptFile, [Arguments], [ExecutionMode]) and DoJavaScript(JavaScriptCode, [Arguments], [ExecutionMode]); ExecutionMode 1 never shows the debugger
macOSAppleScript do javascriptdo javascript "$.evalFile(new File(arguments[0]))" with arguments {scriptPath}, with the path passed to osascript as an argument so it never enters script source; check the exact app name for your version
BothVS Code ExtendScript DebuggerAdobe's extension for running and debugging .jsx against a running app
Windows (legacy)ExtendScript Toolkit -run32-bit, does not run on macOS 10.15 or later; keep only for old pipelines

Pass parameters through a sidecar key=value file (no JSON parser or eval needed in ES3) and have the script write its result to a file, because arguments handling differs between launchers. The patterns are in references/automation-and-mcp.md.

Instructions People Follow by Hand

When the deliverable is a set of steps rather than code (for a complex graphic, or for an asset someone downloads):

  • Name the Illustrator version the steps were checked on, and give menu paths exactly as they appear (Object > Path > Offset Path).

  • One action per step, with the panel and the value to set (Stroke panel: Weight 2 pt, Align Stroke to Inside).

  • Show the expected result after each group of steps, with a screenshot or a small PNG.

  • Mark the steps that differ on Windows and macOS (shortcuts, file dialogs, font paths).

  • Offer the scripted route next to the manual one when a script exists.

Guardrails

  • Work on copies of user documents; never overwrite an original without a backup.

  • Ask before writing into Adobe's install folders, the system CEP folder, or the registry.

  • Development mode (PlayerDebugMode) belongs on development machines only. Ship signed ZXPs to users.

  • Never commit signing certificates, certificate passwords, API keys, or tokens. Read secrets from environment variables.

  • Prefer scripting, COM, or AppleScript over clicking through the UI; use computer use only for what has no scripting route.

  • Never automate around sign-in, licensing, or account dialogs.

  • Fonts from Adobe Fonts cannot be bundled in a plug-in or extension; document them as a requirement instead.

  • Version-specific details (CEP version, SDK version, menu names) change; say which version you checked and point to Adobe's docs.

References

Files

references/publishing-docs.md

Docs for a Published Illustrator Tool

Use this outline for the README, help page, or small documentation site that ships with an Illustrator script, CEP extension, plug-in, MCP server, or downloadable asset. Users read install docs while something is not working, so lead with requirements and keep every step checkable.

Outline

  1. Name and one-line purpose, then a GIF or screenshot of the result.

  2. Requirements: Illustrator versions, OS, and anything else needed (fonts, Node.js for an MCP server). Say which version you tested on.

  3. Compatibility table (below).

  4. Install, one section per OS and per method.

  5. First run: a short walkthrough from opening the tool to the first result, with a screenshot per step that changes the screen.

  6. Options: each setting, its range, and its effect, with small before and after images where it helps.

  7. Troubleshooting: symptom, cause, fix.

  8. Uninstall.

  9. Changelog, newest first.

  10. License and credits for bundled assets.

Compatibility Table

IllustratorWindowsmacOSTested
2026 (30.x)YesYes30.1 on Windows 11
2025 (29.x)YesYesNot tested
2024 (28.x) and earlierNoNon/a

Add a row for the extension technology when it matters: "CEP 12 panel" now, "UXP plugin" once a UXP version exists.

Install Sections by Tool Type

Script (.jsx)

  1. Download acme-grid-tool.jsx.

  2. Run it once from File > Scripts > Other Script, or copy it to Illustrator's Presets/<locale>/Scripts folder and restart Illustrator to list it under File > Scripts.

CEP extension (signed ZXP)

  1. Download acme-grid-tool-1.0.0.zxp.

  2. Install it with Adobe's Unified Plugin Installer Agent, or with the Adobe Marketplace listing if there is one. Give the full UPIA command for Windows and the macOS location (see cep-extensions.md).

  3. Restart Illustrator, then open Window > Extensions > Acme Grid Tool.

CEP extension (development copy)

  1. Copy the extension folder to the per-user CEP extensions folder.

  2. Turn on PlayerDebugMode for the CSXS version (development machines only), then restart Illustrator.

Plug-in (.aip)

  1. Quit Illustrator.

  2. Copy the .aip for your OS into a folder of your choice and set it under Preferences > Plug-ins & Scratch Disks > Additional Plug-ins Folder, or copy it into Illustrator's Plug-ins folder.

  3. Start Illustrator.

MCP server

  1. Requirements (runtime version), install command, and the MCP config snippet for each supported AI tool.

  2. What each tool does, which folders it reads and writes, and what it never does.

Screenshots and GIFs

  • Capture at 100% UI scaling and crop to the panel or the area that changes.

  • Use a demo document with placeholder content (Acme Corp artwork, example.com URLs); never a client file or a real account.

  • A GIF of 3 to 8 frames at 1 to 2 seconds each shows a result better than a long screen recording. Export the frames from Illustrator with a script so they match the docs exactly.

  • Give every image alt text that says what it shows.

Troubleshooting Table

SymptomCauseFix
Menu item missingScript not in the Scripts folder, or Illustrator not restartedMove the file, restart Illustrator
Panel missing or blankVersion outside the supported range, or an unsigned buildCheck the compatibility table; install the signed ZXP
"No document is open"The tool needs an open documentOpen or create a document first

Changelog Format

## 1.1.0 (2026-06-01)
- Added: alternating row patterns.
- Fixed: linked assets lost on documents saved to another folder.

## 1.0.0 (2026-05-01)
- First release.

Data in Docs

Docs are public. Use placeholder people, companies, and paths only: Jane Doe, Acme Corp, [email protected], C:\Users\<user>\... on Windows and ~/... on macOS. Never copy names from real documents, Creative Cloud libraries, or file lists into examples or screenshots.

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server, Needs an API key

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of jhaugajhauga
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/adobe-illustrator-integrations · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
jhauga

AutoGineer is not affiliated with or endorsed by jhauga or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download adobe-illustrator-integrations.zip