← ClaudeAtlas

psd-jsx-builderlisted

Programmatically build layered Photoshop PSD files from code (ExtendScript/jsx) and render-verify them without manual clicking. Use this skill whenever the user wants to generate, batch-produce, or script Photoshop documents — slide decks, portfolio pages, posters, certificates, repeated layouts, data-driven graphics — especially when they mention .psd files, Photoshop automation, jsx/ExtendScript, "build slides in Photoshop", 4K artboards, or want a reproducible image pipeline they can re-run after edits. Also use it when they need to edit text or swap images in an existing PSD without losing manual layer edits, or to verify a generated PSD by rendering it to PNG. macOS + Adobe Photoshop required.
sungsu8055/claude-photoshop-skill · ★ 0 · Web & Frontend · score 72
Install: claude install-skill sungsu8055/claude-photoshop-skill
# PSD jsx Builder Build Photoshop PSD files from code instead of by hand. You write an ExtendScript (`.jsx`) that describes the document — background, placed images, text layers — then run it through Photoshop headlessly from the terminal, then render the result to a PNG to verify it. The whole loop is scriptable, so you can build → check → tweak → rebuild dozens of times without ever clicking in Photoshop. This is the right approach when a layout repeats (a deck where every slide shares a grid), when content is data-driven, or when the user wants a pipeline they can re-run after changing an asset. For a one-off image with no structure, a normal design tool is faster. ## Why this exists / the core insight Photoshop's UI is slow to drive and impossible to reproduce exactly. ExtendScript can build a document deterministically, but the official "run a script file" entry points are flaky across versions. The reliable path discovered through production use: **Pass the jsx *text* to Photoshop inline via macOS `osascript … do javascript`** — not as a file alias. This sidesteps file-dialog issues, version incompatibilities (`do javascript file … as alias` is broken in some builds), and grayed-out script-browser bugs entirely. You never touch a dialog. Then verify by rendering the saved `.psd` with **`psd-tools` → PIL** in a normal Python environment, so you can look at the result programmatically. ## Step 0 — set up the project first (especially for non-experts) Before writin