Voice and tone
Voice and Tone is a plugin for Claude Code that I wrote. You install it in your repository, and it turns a voice guide into rules that an agentAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent. can follow. This page shows the plugin first, then the rules that it made for this site.
A brand voice guide your tooling can prove
Most voice guides say "warm, but professional". Nobody can tell who set that rule, what it rests on, or whether the copy still follows it. Voice and Tone is my open-source plugin for Claude that makes each rule traceable.
It is for teams that publish a lot of copy, often with agents writing part of it.
What it does
- Discovery. It reads the copy you already have, measures it per language and turns what it cannot tell into questions.
- Forced choice. Instead of asking you to rate yourself, it shows two or three rewrites of your own copy and asks which one sounds like you.
- A tone model. Voice stays fixed; tone moves with the context and the reader's state. It stores a few numbers and computes the rest: 80 tone cells from 18 stored rows. Humor is off where a reader is upset.
- Learning with a brake. Your edits become evidence. A rule forms only after two independent confirmations, and you approve it.
- An independent critic. A separate agent reviews each draft without seeing the reasoning that produced it.
Everything lives as Markdown in your repository. No database, no account.
Where it comes from
It is built on Mailchimp's Voice and Tone framework and is not affiliated with Mailchimp. It is not a design-system tool. It shares this site's method: evidence before authority, a confidence level on every rule, and checks in code.
How it follows the patterns
| Pattern | In the plugin |
|---|---|
| Honest gaps | Every rule records its evidence and a confidence level: confirmed, derived, assumed or disputed |
| Report, do not block | A disputed rule is never enforced until a person decides |
| DeterministicGives the same result each time, with no language model. first | Tone is computed. 80 tone cells from 18 stored rows (10 contexts × 8 reader states) Gates are functions in code, not instructions in a document |
| Deterministic first | Humor forced to zero for 3 reader states |
| Evidence, not authority | One critic agent in a fresh context judges the copy. It sees the draft, not the reasoning that produced it |
| Honest gaps | Metrics with no method for Czech show n/a |
"The failure mode of a computed cell must be 'a bit flat', never 'joked at someone whose payment just failed'."
The rules of this site
I made the voice of this site with the plugin. These are its rules, with their confidence levels.
Published on the site. Built on 2026-11-16 with the open-source voice-and-tone plugin (https://github.com/pavolhudran/ai-voice-and-tone), knowledge base kb 0.1.0. The plugin is built on Mailchimp's Voice and Tone framework and is not affiliated with Mailchimp.
Inputs: 3 documents, 7,637 words: the build brief (Part A), the About draft, the Czech talk abstract. Fingerprint measured, not estimated. 4 preference pairs answered by me. Industry terms taken from DTCGThe Design Tokens Community Group and its file format for design tokens, version 2025.10. A Final Community Group Report, not a W3C standard. 2025.10 and published design systems.
Result: 59 rules: 51 confirmed, 2 derived, 6 assumed, 0 disputed. 6 of 80 tone cells authored; the other 74 are computed and can never carry humour.
Confidence: confirmed means I stated it or chose it; derived means the corpus shows it at least 5 times in 2 or more files; assumed means a default nobody has tested yet. A review blocks on confirmed, warns on derived, nits on assumed, and never enforces disputed.
Who is speaking
One person: me, Pavol Hudran, in the first person singular. No "we": there is no company. The reader is a front-end lead, a design-system owner or a design engineer. Write for them without simplifying.
| Id | Voice | Means | Conf |
|---|---|---|---|
| V1 | Evidence first | Every figure carries its base and source in the same sentence. The limit comes before the claim | confirmed |
| V2 | Plain and technical | Short sentences, one fact each. Terms stay technical | confirmed |
| V3 | One person speaking | "I", never "we". No services, no prices, no pitch | confirmed |
| V4 | Honest about gaps | not enforced (gap), n/a, [DOPLNIT] (Czech for "to fill"). Judgments and bets are labelled |
confirmed |
Tone for common situations
Default dials (0 to 4): warmth 2 · humour 0 · directness 4 · detail 3 · urgency 1 · formality 2.
| Situation | Cell | Do | Example | Conf |
|---|---|---|---|---|
| A finding | help-doc / focused | Finding first, then its base, then one copyable example | "A decisionA written choice of the team, with an id, a reason and the check that enforces it. On this site, a row of the register. counts when something checks it. On the B2B car-loan platform, 46 decisions each name their mechanism." | assumed |
| A limit | help-doc / uncertain | Limit before the claim; say what was not checked | "Precision and recall of 1.0 hold on the tuning corpus only. First contact with real files gave about 13% signal." | assumed |
| A prediction | release-notes / curious | Label it "judgment" or "bet"; name its limits in the same paragraph | "Judgment: the rules layer becomes the design system's main product." | assumed |
| A call to action | marketing-page / curious | One sentence of thesis, one action, no pitch | "Find your level. Five yes/no questions. Nothing is stored." | assumed |
| An error message | system-error / confused | Say what happened and what to type next; never blame | "Enter a full email address, for example name@example.com." | assumed |
| An empty list | product-ui / confused | Say why it is empty and the one way to fill it | "No field notes yet. The first one is the industry map, dated 2026-11-16." | assumed |
These six cells stay assumed until I approve them on first real use.
Mechanics
| Id | Rule | Conf |
|---|---|---|
| M01 | No em dash. Use a full stop, a colon, a semicolon or a short hyphen | confirmed |
| M02 | Two related facts are two sentences | confirmed |
| M03 | No exclamation marks | derived |
| M04 | Sentence case for headings and buttons | derived |
| M05 | No contractions | confirmed |
| M06 | No serial comma | confirmed |
| M07 | Figures in digits, base in the same sentence | confirmed |
| M08 | Gap markers literal: not enforced (gap), n/a, [DOPLNIT] (Czech for "to fill") |
confirmed |
| M09 | Dates "20 November 2026" in prose, ISO in tables | confirmed |
| M10 | Code, tokensA named design value, for example a color or a spacing step, kept as data. DTCG 2025.10 gives the file format., files and commands in code |
confirmed |
| M11 | No emoji | confirmed |
| M12 | 24 px is the WCAG 2.2 AA target minimum; 44 px is AAA | confirmed |
Words to use
- The site's own: base · Enforced byThe field of a decision that names the check that proves it, or says "not enforced (gap)". ·
not enforced (gap)· check · judgment · bet · "moving into Claude". - The industry's, one term per concept:
- design token, then token; alias (not "reference"); type; group; composite token (DTCG 2025.10 Format)
- resolverThe part of a token set that selects the values for a context, for example a brand or a mode.; modifierA named choice in the resolver with its options. This site has two modifiers: brand and mode.; context; set; resolution order; permutation (DTCG 2025.10 Resolver). Here: modifiers
brandandmode, 4 permutationsOne combination of the modifier options. This site has four. - primitive, semantic and component tokensA token for one component only. It points at a semantic token. for the three tiers
- foundations; components; patterns; variant; state; governance; contribution; driftA difference between the design system and what was built.
Words to avoid
| Avoid | Write instead |
|---|---|
| we, our team | I |
| W3C standard (for DTCG) | DTCG 2025.10, a Final Community Group Report |
| obsolete, deprecated, shut down (Claude Design) | moving into Claude |
| practically no drift | show where it drifts |
| maturity score, quality score | the level and the first gap |
two-way (for /design-sync) |
an upload from code to the tool |
| LangChain agent layer | skills, hooks, sub-agents and deterministic scripts |
| seamless, powerful, revolutionary | the number and its base |
| core, global, base, option tokens | primitive tokensA token that holds a raw value and no intent, for example a gray of a given lightness. |
| decision, system, purpose tokens | semantic tokensA token that holds an intent, for example the color of a link. It points at a primitive token. ("decision" here means a register row) |
| scoped, override tokens | component tokens |
| theme (as a DTCG term) | permutation, or a modifier's context |
Never say: a 2026 client, employer or tool name; "the design file is dead"; adoption counts for the plugin or Claude Design; "1 in N elements has a defect"; that the early sites still run on their original code.
Before and after
| Before | After | Rules |
|---|---|---|
| We help teams build powerful, AI-ready design systems fast! | I build design systems that AI agents can read and obey. | V3, L10, L17, M03 |
| Most systems already ship an MCPModel Context Protocol. The open protocol that agents use to read tools and data. server. | 20 of 21 open-source design systems ship an MCP server, counting community servers. Field study, July 2026. | V1, M07 |
| Our core and decision tokens drive every theme. | Primitive tokens feed semantic tokens. One resolver with two modifiers gives 4 permutations. | L33, L40, L41, L43 |
| Claude Design is being shut down in December. | The standalone Claude Design site closes on 14 December 2026. It is moving into Claude. | L12, M09 |
| It's never invented, it's proposed, and it's reviewed. | A missing part becomes a proposal. It is never invented. | M02, M05, M06 |
Czech (slides only)
- Address the audience as "vy", formal plural: "V pondělí ráno zkuste tři kroky." (
confirmed) - Technical terms stay English: design token, component, registryA list of the components of a system that a tool or an agent can read., MCP server, pull request, CIContinuous integration: the checks that run on each change of the code.. (
confirmed) - Typography: „ “ quotes, decimal comma, space as thousands separator, non-breaking space after one-letter prepositions.
Not yet decided (queued)
- 74 of 80 tone cells are computed, not authored. Each is authored on first real use.
- The six situation cells above stay
assumeduntil approved. - The plugin's
sources/folder is excluded from the repository by its own.gitignoreand is never published.