Brand-voice kit for agents and editors.
The voice teams
don't rewrite.
Tone rules, banned phrases, fact checks, SEO briefs, handoffs: six years of edits, committed. VOICE.md and a dozen playbooks load before your first prompt, and two review bots let the agent proof its own draft.
The blank page
alone costs you days.
Every single time.
This is the part nobody quotes for and everybody rebuilds. Days gone before the real writing starts.
HOURS LOST PER LAUNCH 4 FULL DAYS
DAY 01-8 HRS
VOICE DOC FROM SCRATCH-3
BANNED-WORD LIST-3
SAMPLE LIBRARY, AGAIN-3
DAY 02-8 HRS
BRIEF TEMPLATES + REVIEW FLOW-4
EDITOR CHECKLISTS NOBODY USES-4
DAY 03-8 HRS
SEO BRIEFS, META, SCHEMA-3
LINK MAPS, REDIRECTS, ALT TEXT-3
FACT-CHECK SPREADSHEET-3
DAY 04-8 HRS
AGENT REWRITES THE HANDOFF-8
001 / AGENT-NATIVE, FROM LINE ONE
VOICE.md sits at the root with a dozen playbooks. Briefs, rewrites, headlines, fact checks: each one a short file the agent reads before it types a word. Two review bots mark every draft against the rules and send it back.
002 / A VOICE AS A SYSTEM
Tone dials, banned phrases, house analogies, sentence rhythm. One source of truth for every writer and every model, so the fortieth post sounds like the first. You never describe the voice from memory again.
003 / BRIEFS THAT TRAVEL
Audience, angle, proof, keyword, call to action: seven fields, always in the same order. Hand a brief to a freelancer or an agent and the draft comes back the right shape.
004 / THE HARD PARTS, ALREADY DONE
The three jobs nobody gets right the first time. A claims register that links every number to a source. A headline lab with scoring. A rewrite ladder from rough note to publishable page. Tested on real launches.
005 / FACT CHECK, SOLVED
Every statistic carries a source and a date. Stale claims get flagged on a schedule, quotes are matched against recordings, and nothing unverified slips into a draft at midnight.
006 / A DESK EDITORS ACTUALLY USE
Drafts sit where editors expect them. Comments stay in the margin, approved copy gets locked, nobody hunts for the latest version. Clients stop emailing to ask where the homepage text lives.
007 / SEO, DONE NOT DEFERRED
Per-page title and description from the brief, internal link map, schema snippets, alt text and a redirect sheet. Nothing bolted on the week before launch.
008 / READY TO SHIP FROM DAY ONE
Approval flow, legal flags, accessibility checks, a plain-language pass, analytics tags. The plumbing you rebuild for every client, already wired.
009 / SET UP, NOT JUST COPIED
An interactive setup script writes your voice card, imports old posts to learn from, connects the review bots and fills in the config. Migration scripts back up your archive and move it between tools. The first run is handled, not documented.
# Copy Foundry
## What ships
## Quick start
## Rules the agent follows
The work that gets remembered.
Real sites, written with Copy Foundry. With the plumbing already handled, the effort goes where it shows. The work here has been recognised by Awwwards, FWA and CSSDA, and picked up across studio feeds.
HEAD OF CONTENT, FENNEL
EDITOR, STUDIO NORTH
Two editions. One foundry. Lifetime updates.
- 001NOTION WORKSPACE + REPO
- 002UNLIMITED CLIENT BRANDS
- 003LIFETIME UPDATES
- 004AGENT-READY: VOICE.md, PLAYBOOKS, BOTS
- 005DIRECT SUPPORT FROM THE MAINTAINER
14-day refund. Pay once, keep it.
Before you buy
Two editions, one foundry. The Notion edition runs on a Notion workspace plus a Git repo of playbooks; the Docs edition uses Google Docs templates and the same repo. Both share the voice card, the twelve playbooks and the two review bots, written in TypeScript and plain Markdown.
Yes. VOICE.md and AGENTS.md sit at the root, so any agent that reads project files picks the voice up before its first prompt.
No. Everything is plain files you own. Rename a playbook, delete a bot, swap a tone dial. Updates arrive as diffs you choose to merge.
Yes, each edition is a separate one-time licence. Many studios take both and use Docs for clients who live there.
Basic Git helps, but the setup script handles the first run and the handoff pack explains the rest.
The writing side needs no code at all. A developer is only needed once, to connect the bots to your editor of choice.
Yes. One licence covers unlimited client brands. You can't resell the kit itself or share the repo outside your team.