Documentation

Installation & user manual

From download to a live, password-protected ?edit mode — about 60 seconds to install, 10–15 minutes for Claude to wire a typical project.

What you’ll get out of this manual:

• Install both skills so they work in every project on your machine
• Run the skill once and hand your copy team a working edit mode
• Take it live on Vercel so edits publish for every visitor
• Rotate the editor password safely when you need to

What’s in the box

Two Claude Code skills, ready to install:

• copy-edit-feature/ — teaches Claude to add the ?edit mode to a project: the floating edit bar, the password gate, click-to-edit text, and the override store. Inside it, references/ holds the implementation guides and assets/ holds ready-made sync scripts — keep the folder intact.
• reset-copy-edit-password/ — teaches Claude to rotate the editor password later: one command, every open editor session locked out, no copy lost.

Plus LICENSE.txt — your personal license (unlimited personal and client projects).

Install the skills (about 60 seconds)

Copy both skill folders into your personal skills directory. That’s the whole install.

macOS / Linux

cp -R copy-edit-feature reset-copy-edit-password ~/.claude/skills/

Windows (PowerShell)

Copy-Item -Recurse copy-edit-feature,reset-copy-edit-password $HOME\.claude\skills\

Prefer to scope them to a single project? Copy the folders into that project’s .claude/skills/ directory instead.

Then restart Claude Code (or start a new session) so it picks up the new skills. To confirm: ask Claude “when would you use the copy-edit-feature skill?” — it should quote the skill’s description back.

Your first run

1. Open your web project in Claude Code.
2. Say “add the copy edit feature” (or run /copy-edit-feature).
3. Claude detects your framework and asks you to choose the editor password — the one your copy team will use. Save it; it’s shown once.
4. Claude wires everything up and finishes with a verification checklist, reporting anything it intentionally skipped.
5. Open any page with ?edit at the end of the URL, enter the password, rewrite a headline, click away, reload — it stuck.

The editing workflow (share with your copy team)

• Open any page with ?edit added to the URL — a small bar appears at the bottom.
• Enter the password once; the bar follows you across pages for 8 hours.
• Press Edit — editable text shows a dashed outline on hover.
• Click text to place your caret. Rewrite it. Click away to save. Enter saves too; Escape cancels; paste is always plain text.
• Clear a text completely to restore the original wording.
• Pause turns outlines off while you browse; Lock signs you out.

While editing, links and buttons don’t navigate — click them to edit their labels instead.

Going live on Vercel

Locally, edits save to a JSON file with zero configuration. To share edits with real visitors, the skill deploys the same feature on Vercel with an Upstash Redis store (both have free tiers — you pay those providers directly).

Tell Claude “deploy the copy edit feature to production” and it walks the provisioning. From then on:

• Edits made on the live site publish instantly to every visitor.
• Edits made locally stage in a separate namespace — publish with npm run copy:push (dry-run first, always).
• npm run copy:backup snapshots production copy before big pushes.

Changing the password

Run /reset-copy-edit-password (or say “rotate the copy edit password”). Claude updates your local env, updates Vercel, redeploys — and every previously unlocked editor is locked out the moment the new password is live. Copy is untouched. Rotate whenever someone leaves the team or the password may have leaked.

Troubleshooting

The skill doesn’t trigger when I ask.
Restart Claude Code, then check the folders sit directly inside ~/.claude/skills/ (SKILL.md at ~/.claude/skills/copy-edit-feature/SKILL.md).

The bar doesn’t appear with ?edit.
Restart the dev server; if it persists, tell Claude “the edit bar doesn’t appear on [page]” — the skill includes a troubleshooting guide it will follow.

The password won’t unlock.
Check COPY_EDIT_SECRET is set where the site runs (.env.local locally, env vars on Vercel), then restart/redeploy.

Edits don’t show for normal visitors in production.
Page caching — tell Claude “production copy edits aren’t visible to visitors” and it will fix the rendering mode.

Support

Questions, trouble installing, or a fresh download link: claudeskills@underdog.ae — include your order reference if you have it.