adobe-cross-app-workflowslisted

# Adobe Cross-App Workflows ## Purpose Orchestrate multi-app Adobe pipelines, define shared guardrails across all app skills, document the MCP architecture for troubleshooting, and manage handoffs between the Creative Director planning layer and the four execution skills. ## When to Use - Coordinating assets across multiple Adobe apps (e.g., Illustrator vectors → After Effects animation) - Troubleshooting MCP proxy connections or plugin errors - Planning the order of operations for a multi-app pipeline - Needing shared guardrails (naming conventions, checkpoint behavior, destructive action safeguards) - Understanding the adb-mcp architecture (proxy, plugin, transport) - Starting a cross-app workflow like the animation pipeline or social media content creation ## Examples **Example 1: Animation pipeline** ``` User: "I have character designs in Illustrator that need to be animated in After Effects and assembled in Premiere" Claude: [Uses adobe-cross-app-workflows] Plans the pipeline: 1. Illustrator: Clean up layers, name groups, save as .ai with "Create PDF Compatible File" ON 2. After Effects: Import .ai as "Composition - Retain Layer Sizes", rig with nulls, animate 3. After Effects: Render to ProRes 422 .mov 4. Premiere: Import rendered .mov, assemble with audio, titles, export Checkpoint: Verify frame rate consistency (24fps) across all apps. "Start with /adobe-illustrator-mcp for asset prep." ``` **Example 2: MCP troubleshooting** ``` User: "The Photoshop