The loop you're already running
You open a record in HubSpot. Copy the body. Paste it into Claude. Ask for a tighter rewrite, a tone pass, a meta description. Copy what Claude gives back. Paste it into HubSpot. Hit save. Open the next record.
That's fine for three records. It is not fine for three hundred. The work isn't the writing; Claude does that in seconds. The work is the swivel between two windows and the cost of every small mistake landing live the moment you paste.
What Scratch does to the middle
Scratch pulls your CMS into a folder on your machine. One JSON file per record. Prose fields (bodies, descriptions, alt text) sit alongside structured fields (IDs, tags, slugs, dates, metafields) in the same file. HubSpot, WordPress, Shopify, Notion, the rest.
Now Claude has something it's actually good at: files. Point the Claude desktop app at the Scratch folder and Claude reads, edits, and writes the changes back to the same files. Scratch shows you every diff, per record, in the desktop app. You approve the ones you like. Scratch pushes those, and only those, back to the CMS.
No window swivel. No paste-by-paste. Same Claude.
Three tabs, same files
The Claude desktop app has three tabs across the top. All three operate on the same files on disk; pick the one that fits the job.
Chat. Best for a handful of records, an exploratory rewrite, or feeling out a prompt before scaling it. Drag a Scratch file or folder into the chat. Give Claude the instruction. Ask it to return the edited files. Save the response over the originals in your Scratch project folder. Scratch shows the diff.
Cowork. Best when you want Claude to take a multi-step job and run it end to end without you babysitting prompts. Give Cowork access to your Scratch project folder, describe the outcome, and walk away. Cowork uses the same agentic architecture as Claude Code, exposed inside the desktop app instead of the terminal. You come back to edited files; Scratch shows you every change before any of it goes live.
Code. Best for power users who want the Claude Code engine without leaving the desktop app. Same file-editing loop as the CLI, same skills library, same diff surface in Scratch. If you live in a terminal already, /with/claude-code/ is the page you want instead.
Same files on disk. Same review surface. Pick the tab that fits the size of the job.
What stays safe
Files are local. Claude reads and writes files; it never touches your CMS. Nothing leaves your machine until you click publish in Scratch, per record.
Validators (optional) are AI-authored Python rules that fail length-cap and formatting regressions before a diff ever reaches your eyes. Per-row approve. Per-row rollback. The original version sits next to the dirty one until you decide.
Bring-your-own-Claude. Scratch holds no Claude credentials and runs no model. You sign into the Claude desktop app the way you already do.
What this is not
Not an MCP server. Not a Claude plugin. Not a "Claude-for-CMS" wrapper that pushes through an API on Claude's behalf. Scratch is the file substrate; Claude is the AI you brought. The shape (pull, edit, diff, ship) survives whichever Claude model you're on this quarter.
Browse the skills below for prompts that work end-to-end with Claude.