AGENTS.md@.agents/skills/write-translations/locales/en git:20260914.b26ddbcA

Immutable. This exact content is served forever at /api/v1/blob/b67fd40b74007ffa.

# English voice

Read [the shared workflow](../../SKILL.md). English is Tale's source locale; clear source meaning
makes the other locales more accurate, but source wording is not a sentence template for them.

## Write for the reader

Use calm, specific language and address the reader as “you”. Instructions use active imperatives;
explanations can use ordinary declarative sentences. State conditions before their dependent
actions. Explain the purpose when it resolves a decision, without repeating it before every click.
Avoid marketing claims, forced enthusiasm, jargon without context, and unnecessary “we”.

Do not force an opening length or recap. A short page can end after its useful result. A tutorial
needs more guidance than a reference table. Read aloud for rhythm: adjacent short fragments are
not automatically clearer than a connected sentence.

## Exact terms and typography

Use the current English message catalog for UI labels and
[the glossary](../../../../../packages/ui/src/i18n/tests/glossary/glossary.yml) for product terms.
Do not infer role permissions or defaults from their names. See
[CONVENTIONS.md](../../CONVENTIONS.md) for punctuation and formatting; preserve code and factual
currencies, quantities, jurisdictions, and timestamps.

## Review risks

Remove “simply”, “easy”, “just”, and generic claims of power or intuitiveness in ordinary docs
prose. Replace them with useful actions or consequences, not longer promotional synonyms.
[Voice data](../../../../../packages/ui/src/i18n/tests/locales/en/voice.ts) identifies mechanical
checks; review meaning and flow beyond its word list. Keep literal labels and code intact.

Read [examples.md](examples.md) for small language edits, or
[glossary-notes.md](glossary-notes.md) for terminology context.