Edit text in Claude
with zero tokens ?edit

Your copywriter doesn’t even need a Claude account to edit copy.

Watch it work

One-time payment · Instant download

0 tokens per edit0 redeploysNext.js 15 / 16 tested
The skill in action

Watch an edit ship itself.

01Unlock. Open any page with ?edit, enter the shared password.
02Click & rewrite. Every marked text is editable in place — caret and all.
03Saved for everyone. Click away. The change is live for every visitor.
The same edit, timed.

Prompt vs. skill.

The old way

By prompting Claude

  1. Write the prompt
  2. Claude re-reads the codebase
  3. Generates the diff
  4. You review & correct
  5. Commit & push
  6. Redeploy & verify
0:00Time
0Claude tokens
The skill

With the ?edit skill

  1. Click the text
  2. Rewrite it
  3. Saved — live for everyone
  4. Done — and you never opened Claude
0:00Time
0Claude tokens
2:11 + 8,600 tokens saved on every single copy change.
Installation

Claude sets it up once.

Install the skill

Unzip into ~/.claude/skills/ — about 60 seconds, one copy-paste.

Say the word

In your project, tell Claude Code: add the copy edit feature. It detects your stack, wires the edit bar, gates it with your password.

Hand over the password

Your copy team opens any page with ?edit and owns the words from then on. You never field a “can you change this text” ticket again.

Runs on your stack

Localhost to Vercel + Upstash KV.

ENV — 01

Local — zero config

On your dev machine, edits save to a JSON file. No accounts, no keys, works offline — the full feature from the first minute.

ENV — 02

Production — Vercel + KV

Deployed on Vercel with Upstash KV (Marketplace Redis), edits publish live to every visitor. Free tiers on both cover typical content sites.

ENV — 03

Portable — any Node host

Upstash's REST API works from anywhere, and the server contract ports to any backend. Vercel is the paved path, not a requirement.

Under the hood

Engineered like a feature, not a hack.

SEC — 01

Server-side gate

The password is checked on the server with a constant-time compare and exchanged for an HMAC-signed, httpOnly cookie. Nothing sensitive ever ships to the browser.

SEC — 02

Fail-open core

Storage down? Credentials revoked? Your site renders its in-code copy as if nothing happened. The edit layer can never blank a page.

ARC — 03

Code stays the source of truth

Edits are a sparse override layer on top of your code. Delete every override and the site still works, word for word.

ARC — 04

No AI at runtime

After install, the feature is plain web engineering: an API route, a signed cookie, a key-value store. Nothing to meter, rate-limit or queue.

OPS — 05

Staged publishing

Edit on staging, review, then publish to production with a dry-run-first script. Backups included — copy ships independently of code.

SEC — 06

One-command rotation

Password leaked, contractor gone? The companion skill rotates the secret and instantly locks out every open session.

Pricing

One price. Every project.

One-time purchase — no subscription
$9.99once, forever

Every copy request you don't relay pays for it. Both skills, all guides and scripts, yours forever.

Instant download by email · Secure checkout by Stripe · Full refund within 7 days unless downloaded

  • The copy-edit-feature skill — full ?edit mode for your app
  • The reset-copy-edit-password skill — rotate the password safely
  • Tested reference implementation for Next.js 15 & 16
  • Adaptation guides for SvelteKit, Nuxt, Astro, Rails & more
  • Staging → production publish, backup and sync scripts
  • Personal license — unlimited personal & client projects
Stay in the loop

New skills, first.

Occasional notes on Claude Code skills we ship — and early pricing when new ones launch.

Launch notes, updates and new skills. No spam, unsubscribe anytime.

Questions

Asked & answered.

What exactly do I get?
Two Claude Code skills as an instant download: copy-edit-feature, which wires the full ?edit mode into your project (floating edit bar, password gate, click-to-edit text, override storage), and reset-copy-edit-password, which rotates the editor password safely later. Plus tested sync scripts and adaptation guides for other stacks.
Does my copywriter need Claude, or any technical setup?
No. Claude Code is used once, by you, to install the feature. After that, your copywriter just opens any page with ?edit, enters the shared password, and clicks the text to rewrite it. A browser is the only tool they need.
Does editing really use zero tokens?
Yes. Claude is only involved once, when it installs the feature into your project. Every edit after that is a plain HTTPS request from the browser to your own site — no AI anywhere in the loop, so there is nothing to meter.
Which frameworks does it work with?
The reference implementation targets Next.js (App Router, tested on Next 15 and 16). The skill also carries adaptation guides for Next.js Pages Router, React SPAs, SvelteKit, Nuxt, Astro, server-rendered apps and non-Node backends — the server contract is portable.
Do edits survive deploys?
Yes. Edits live in a separate override layer (Upstash Redis in production, a JSON file locally), not in your code. Deploy as often as you like — the words your copy team shipped stay live. Blank an edit and the in-code original returns.
Is it safe to put an edit mode on my production site?
The design is fail-open and server-gated: writes require a password-derived, HMAC-signed httpOnly cookie checked on the server; keys are allowlisted and length-capped; and if storage is ever down, your site simply renders its in-code copy. Normal visitors never see any of it.
What does the license cover?
A personal license, one-time purchase, no subscription: use it on unlimited personal and client projects. You may not resell or redistribute the skill files themselves. Full refund within 7 days of purchase unless the file has been downloaded.