Riscrivi nel tuo tono

# VOICE RULES (Tallybook, fictional)
R1. Talk to the reader as "you". Never call readers "users".
R2. No exclamation marks.
R3. Keep every sentence under 20 words.
R4. Never use the words "just", "simply" or "thrilled".
R5. Say "sign in", never "log in".
R6. Legal disclaimers must be kept word for word.

# DRAFT
Hi users! We're thrilled to announce that Tallybook now lets you export your reports as PDF!! Simply log in, open any report and click Export. It's just one click. Users who want to schedule a weekly export can also do that, which many of our customers have been asking for and which we've built in a way that doesn't need any extra setup at all. Tallybook is not a financial advisor and figures shown are for information only and may not reflect your final tax position, so please consult a qualified professional before relying on them.

# On-voice rewrite

## Rewritten text
Hi there. Tallybook now lets you export your reports as PDF. Sign in, open any report and click Export. It's one click. You can also schedule a weekly export. Many of our customers asked for it. It needs no extra setup. Tallybook is not a financial advisor and figures shown are for information only and may not reflect your final tax position, so please consult a qualified professional before relying on them.

## Change list
| # | Original | New | Rule |
|---|---|---|---|
| 1 | Hi users! | Hi there. | R1, R2 |
| 2 | We're thrilled to announce that Tallybook now lets you export your reports as PDF!! | Tallybook now lets you export your reports as PDF. | R2, R4 |
| 3 | Simply log in, open any report and click Export. | Sign in, open any report and click Export. | R4, R5 |
| 4 | It's just one click. | It's one click. | R4 |
| 5 | Users who want to schedule a weekly export can also do that, which many of our customers have been asking for and which we've built in a way that doesn't need any extra setup at all. | You can also schedule a weekly export. Many of our customers asked for it. It needs no extra setup. | R1, R3 |

## Conflicts (your call)
- R3 vs R6: the disclaimer sentence has 31 words, over the 20-word limit in R3, but R6 says to keep it word for word. Left unchanged. Options: exempt disclaimers from R3 (my suggestion to confirm), or approve a shortened wording from your legal contact.

## Left unchanged
- The disclaimer sentence (see Conflicts).
- "many of our customers": R1 covers how the reader is addressed, so third-person "customers" is fine. Tell me if you read R1 more strictly.

---
name: brand-voice-guard
description: Rewrites a draft so it follows a voice rules file the user supplies, then lists every change with the rule behind it and flags rules that conflict instead of guessing. Use when a draft must match a written brand or style guide.
---
# Brand Voice Guard
A draft and a voice rules file in, an on-voice rewrite and a change list out.

## When to use
- You have written voice or style rules and a draft that may break them.
- You want to see exactly what changed and why, and to be told when rules clash.

## Inputs
- The voice rules file (numbered rules are best) and the draft text. Ask for either if missing.
- Optional: which rule wins when two clash. If not given, never decide it yourself.

## Steps
1. Number the rules as R1, R2 ... in the order given. Do not add rules of your own.
2. Split the draft into sentences and check each sentence against every rule. Count words for any length rule.
3. Rewrite only what breaks a rule. Keep the meaning, facts, names and numbers of the draft unchanged.
4. When two rules cannot both be met for the same text, or a rule is ambiguous, leave that text as it is and record it under "Conflicts".
5. Re-check the rewrite against every rule, then list unchanged text that already passed.
6. Build the change list: one row per change with original, new text and the rule number.

## Output
Write `on-voice.md` with: `## Rewritten text`, `## Change list` (table: #, original, new, rule), `## Conflicts (your call)`, `## Left unchanged`.

## Rules
- Never invent facts, claims, numbers or quotes while rewriting. Dropping a filler word is fine, adding meaning is not.
- Flag rule conflicts and ambiguity instead of guessing; state the options and wait for the user.
- Quoted legal or compliance text stays word for word unless the user says otherwise.
- Ask before assuming which rule takes priority.
- Write results to a new file, never overwrite the draft or the rules file.
- Keep private data local. Legal, medical, tax and financial wording is out of scope: flag it for a professional and do not advise.