This workflow comes from Nolen Jonker’s walkthrough on XDA Developers (May 14, 2026), where they connected Claude to Affinity and handed it the fiddly, repetitive parts of a design file. This is our take on why it’s worth setting up, not a step-by-step reproduction, Jonker’s own walkthrough already covers that in full. We haven’t run it hands-on ourselves.

The core idea is simple. Affinity exposes your open documents to Claude through an MCP connector, so instead of giving you advice about a file, Claude can actually reach in and change it. Jonker’s main point is that this beats Affinity’s older Macros feature, which can’t do conditional logic or take variable inputs.

The shape of the workflow

Setup is two switches: turn on the Affinity MCP option in Affinity’s own settings, then add Affinity as a connector from Claude for Desktop’s connector directory. Jonker notes that network and file-system access are off by default in the permissions panel, worth checking yourself before your first real request. From there, the actual use is straightforward: point Claude at the tedious jobs, renaming layers to a consistent convention, swapping colors across a whole document, tidying spacing across multiple pages, being specific about the exact pattern or values rather than describing them loosely.

We’d add two habits Jonker doesn’t mention: work on a duplicate of the file rather than the original, and start with a read-only request (ask Claude to list and describe the layers first) so you can confirm the connection actually understood the document before you let it change anything.

The real payoff is the last step in Jonker’s piece: once a request works, ask Claude to save it as a script. A one-off edit saves you time once, a script you can read, adjust, and rerun on the next client file keeps saving it, and it doesn’t need Claude or a network connection to run again. Affinity 3.3’s new Scripting Studio workspace (added after Jonker’s piece was published) makes those scripts easier to open and actually read before you trust them.

Jonker walks through every step in detail, including the exact panels and settings involved, in the original piece: I connected Claude to Affinity, and now I batch-edit my designs without touching a single layer.

Why it matters for designers

Handoff prep is where a lot of design time quietly disappears: renaming “Rectangle 47” layers, applying a last-minute palette change across forty pages, making sure every export frame follows the same naming scheme. None of it is hard, and all of it is slow, and turning the repeatable parts of it into a script you can rerun is a bigger win than any single AI edit.

What to watch out for

Since Jonker’s piece was published, Affinity 3.3 has formalized scripting. CG Channel reports that 3.3 scripts are intended for automating repetitive tasks and can’t add new tools or change how existing tools behave. If you’re hoping Claude can build you a missing feature, it can’t.

The connector only covers Affinity itself. Jonker notes it can’t reach Canva’s AI features unless those are separately enabled, so don’t expect generative fill or background removal through it.

Check colors and contrast yourself. Claude will apply a color swap exactly as asked, including one that leaves text unreadable on its background.

And again, this is someone else’s documented workflow, not one we’ve tested. Treat the sidebar as unverified and try it on a throwaway file first.