InDesign

Controls Adobe InDesign from a shell environment through Flue, a local bridge that connects command-line agents to desktop creative applications without requiring an MCP server. A coding agent pipes ExtendScript into a bridge script (indesign_bridge.py) and receives structured JSON back, following the flow agent shell -> indesign_bridge.py -> ExtendScript -> JSON result. This makes it possible for a CLI agent to inspect and edit an open InDesign document even though it cannot otherwise act inside the desktop application.

Use it when work needs to happen inside InDesign itself: inspecting the open document, spreads, pages, frames, text flows, and styles, making bounded edits, or running small ExtendScript steps. The recommended workflow starts by reading FLUE.md in the skill directory, which explains how Flue works, the bridge contract, a worked ExtendScript example, and safety expectations. If Flue is already installed, additional operational detail lives in the flue SKILL.md and the InDesign adapter's APP.md. If Flue is not installed, the agent should tell the user; installation is done with pip install flue && flue setup, and it should not proceed without explicit approval in the current session.

Beyond InDesign, the same stdin/stdout contract drives Photoshop, Illustrator, Premiere, After Effects, Audition, Blender, Houdini, 3ds Max, Unity, and Microsoft Office, so a single install covers all adapters. Because Flue operates inside professional desktop software, the guidance emphasizes treating the human as the driver, preferring small inspectable steps, and avoiding destructive actions unless explicitly requested. Flue is MIT-licensed and reviewable on GitHub and PyPI before use.