← ClaudeAtlas

photoshoplisted

Adobe Photoshop via MCP (uvx photoshop-mcp-server). Use when the user needs PSD edits, layers, exports, or Photoshop automation from the agent. Requires mcp/photoshop wired and Photoshop desktop installed/running.
rogue-dev-studio/ai-agents-rogue · ★ 2 · AI & Automation · score 68
Install: claude install-skill rogue-dev-studio/ai-agents-rogue
# photoshop **Level: max.** Runtime package: `mcp/photoshop` (not skill-text alone). ## Summary Drive **Adobe Photoshop** from the AI host through a public MCP runtime (`photoshop-mcp-server` via `uvx`). Rogue owns the playbook + wiring under `ai-agents-rogue/mcp/photoshop/` and this skill. ## When to use - User asks for Photoshop / PSD / layer edits / export via agent - `TEAM.yaml` or chat names `photoshop` - MCP entry `photoshop` is configured ## When not to use - Vector-first work → prefer `illustrator` - Simple batch image ops without Photoshop → `imagemagick` - Generative raster pipelines → `comfyui` when appropriate ## Prerequisites 1. Adobe Photoshop desktop installed (version matched to `PS_VERSION`, default `2024`) 2. `uv` / `uvx` on PATH 3. Wire MCP: ```powershell .\ai-agents-rogue\scripts\install-mcp.ps1 -Target . -Mcp photoshop ``` See `mcp/photoshop/README.md`. ## Procedure 1. **Context** — Confirm project / `WORKMODE.md`; read `mcp/photoshop/README.md`. 2. **Tooling** — Photoshop running; MCP `photoshop` connected; adjust `PS_VERSION` if needed. 3. **Plan** — Inputs (PSD/assets), outputs (export paths), risks (license, COM/API, long ops). 4. **Execute** — Use MCP tools for document/layer/session ops; save exports under `project/{id}/artifacts/images/` (or `design/` if vector-from-PS workflow). Create project if missing. 5. **Verify** — Open/export check or explicit blocker if MCP cannot reach Photoshop. 6. **Handoff** — Paths under `artifacts/`, PS