---
name: humand-voice
description: Use when writing, reviewing, or auditing Spanish UX copy for Humand — microcopy, errors, success messages, emails, CTAs, tooltips, empty states, modals, banners, push and in-app notifications, or full screen flows. Applies Humand's official voice and tone manual and detects cross-screen inconsistencies.
---

# Humand Voice & Tone

## Operating modes

| Mode | When to use |
|---|---|
| **Write** | Create new copy from a requirement |
| **Audit screen** | Review a single screen |
| **Audit flow** | Review 2+ screens in sequence and detect cross-screen inconsistencies |

---

## Accepted input sources

- Text pasted directly in the chat
- Screen images (screenshots, Figma captures)
- Attached files (JSON of strings, documents)
- Links to flows on the web (fetch the content when in Cowork)
- Verbal description of a screen or flow

---

## Humand personality (the 4 attributes — immutable)

| Attribute | What it is | What it is not |
|---|---|---|
| **Close** | Genuine warmth, direct treatment, person-to-person | Forced corporate friendliness |
| **Clear** | Direct, no detours, respects the reader's time | Simplistic or condescending |
| **Reliable** | Consistent, fact-based, no over-promising | Exaggerated, empty hype |
| **Energetic** | Authentic conviction, confidence | Empty hype, aggressive, exclamation marks as a substitute |

Humand speaks like an expert colleague who genuinely wants to help. Confident without arrogance. Warm without losing professionalism.

---

## Voice rules (never change)

### Person and conjugation
- **Universal tuteo.** "Puedes", "haz", "configura", "revisa". For all markets, Argentina included.
- **Never voseo.** Forbidden: "podés", "hacé", "configurá".
- **Never usted.** Do not use "puede", "haga", "configure".
- **Never third person.** Not "el usuario puede", "el colaborador debe", "Se ha producido un error".
- **Active voice** by default. Valid (and only) exception: when Humand is not the agent and naming it would feel forced. E.g., "Tu contraseña fue actualizada" (by an external admin).
- ❌ Does not apply in snackbars, confirmations, or errors where Humand performs the action.
  - ❌ "Los cambios se guardaron" → ✅ "Guardamos tus cambios"
  - ❌ "No se pudieron guardar los cambios" → ✅ "No pudimos guardar los cambios"

### Gender and neutrality
- Collective nouns: "el equipo", "las personas", "los colaboradores".
- Never slashes (colaborador/a), at-signs, or "x".
- Neutral Latin American Spanish — no regionalisms (see full list in `references/voice.md`).

### Jargon and anglicisms
- No corporate jargon: "sinergia", "apalancar", "end-to-end".
- No unfounded superlatives: "la mejor", "increíble", "innovador", "revolucionario".
- Anglicisms accepted in product: onboarding, dashboard, feedback, checklist, login.
- Anglicisms forbidden: "setear" → configurar, "chequear" → revisar, "linkear" → vincular.

### Diminutives
- Only in onboarding and celebrations.
- **Never** in errors, warnings, or destructive actions.

---

## Tone by context (tone changes; voice does not)

| Context | Tone | What to avoid |
|---|---|---|
| **Onboarding** | Warm, motivating, accompanying | Jargon, superlatives, overwhelming |
| **Successful flow** | Celebratory, genuine, brief | Excessive formality, redundancy |
| **Error** | Empathetic, direct, solution-oriented | Blaming, technical codes, no way out |
| **Empty state** | Guiding, calm, useful | "No hay datos disponibles" |
| **Notification** | Direct, actionable, respectful of time | Ellipses, clickbait |
| **Tooltip / hint** | Clear, concise, informative | Long, redundant phrases |
| **Destructive modal** | Serious, clear, no drama | Ambiguity, diminutives |
| **Loading / waiting** | Calm, brief | Forced humor, complete silence |
| **Offboarding** | Professional, empathetic, no guilt | Drama, diminutives, guilt-based retention |

**Errors always have two parts:** [what happened] + [what to do now]. Never leave the user without a way out.

---

## Punctuation and format

| Element | Period | Case |
|---|---|---|
| Screen / modal titles | ❌ No period | Sentence case |
| Body text / paragraphs | ✅ With period | — |
| Error messages | ✅ With period | — |
| Success messages | ✅ With period | — |
| Labels | ❌ No period | Sentence case |
| Placeholders | ❌ No period | Sentence case |
| Tooltips (short sentence) | ❌ No period | Sentence case |
| Buttons / CTAs | ❌ No period | Sentence case |

**Exclamations:** maximum 1 per screen or text. Only in achievements, celebrations, or welcomes. Never in errors or warnings.

**Capitalization:** only proper nouns and the first letter of a sentence. Product features in lowercase.
✅ "el dashboard", "la solicitud" / ❌ "el Dashboard", "la Solicitud"

**Dates and numbers:**
- Date: `22/ENE/2026` (month uppercase, 3 letters)
- Thousands: period → `1.500` | Decimals: comma → `85,5` | Percentage: no space → `85%` | Currency: attached → `$1.500`

---

## Maximum lengths

| Component | Chars |
|---|---|
| Title / heading | 50 |
| Subtitle | 80 |
| Body text | 150 |
| Tooltip | 80 |
| Push notification (title) | 60 |
| In-app notification | 120 |
| Placeholder | 40 |
| Label | 30 |
| Error | 120 |
| Success message | 100 |
| CTA / button | 20 (≤ 3 words) |
| Loading state | 50 |
| Banner | 150 |
| Onboarding body | 120 |

---

## CTAs and buttons

- **Verb + object** in imperative/infinitive, max 3 words.
- ✅ "Enviar solicitud", "Ver detalle", "Guardar cambios", "Descargar recibo", "Confirmar", "Cancelar", "Eliminar"
- ❌ "Haz clic aquí", "OK", "Sí", "No", "Continuar con el proceso"
- **Emails: one single CTA per email**, in imperative.

---

## ─── MODE: WRITE ───

### Step 1 — Identify component and context
If the component type or situation is missing, ask one brief question.

### Step 2 — Write and present

```
**Component:** [type]
**Context:** [situation]

**Proposed copy:**
> [text]

**Characters:** [n] / [limit]
**Rules applied:** [non-obvious only]
```

### Step 3 — Offer variants
Always provide 2–3 variants, explaining what each one prioritizes (e.g., more direct, warmer, shorter).

---

## ─── MODE: AUDIT SCREEN ───

### Step 1 — Process the input
Accept text, image, or description. If it's an image, extract every visible string.

### Step 2 — Check against the 7 categories

1. **Person and voice** — Tuteo? Active voice? No third person? No voseo/usted?
2. **Tone** — Appropriate for the screen's context? Exclamations controlled? No misplaced diminutives?
3. **Gender and neutrality** — Neutral? No slashes/@s/x? No regionalisms?
4. **Format and punctuation** — Sentence case? Punctuation matching the component? Dates and numbers correct?
5. **Clarity and action** — Actionable? Specific CTAs? Errors with cause + way out? Empty states with context?
6. **Terminology** — "Personas" not "recursos"? No unnecessary anglicisms? HR glossary respected?
7. **Length** — Within per-component limits?

### Step 3 — Report

```
### Audit: [screen name or description]

**Issues found:**

| # | Element | Original text | Issue | Rule | Severity |
|---|---|---|---|---|---|
| 1 | [component type] | "[text]" | [description] | [section] | 🔴/🟡/🟢 |

**Corrected version:**
| Element | Original | Corrected |
|---|---|---|
| [type] | "[original]" | "[corrected]" |

**Changes made:**
- [change]: [brief justification]
```

---

## ─── MODE: AUDIT FLOW ───

Use when there are 2 or more screens in sequence. Detects not only individual errors but **inconsistencies across screens**.

### Step 1 — Map the flow
Identify: name/description of each screen, sequential order, and the context type of each one.

### Step 2 — Audit each screen individually
Apply the "Audit screen" process to each one.

### Step 3 — Detect cross-screen inconsistencies

Check specifically:
- **Tone coherence:** Is the tone consistent with each screen's context, and does it make sense as a progression? A flow shouldn't jump from celebratory to error tone without logical transition.
- **Terminology coherence:** Is the same term used for the same concept across screens? (e.g., never "solicitud" on one and "pedido" on another)
- **Person/voice coherence:** Do all screens use tuteo? Does any screen mix active and passive voice without justification?
- **Format coherence:** Does the same component type follow the same rules on every screen? (e.g., destructive buttons always with the same pattern)
- **Logical progression:** Do messages have continuity from one step to the next? Does the user always know where they are and what comes next?
- **Duplication or contradiction:** Does any message repeat info unnecessarily or contradict something said earlier?

### Step 4 — Flow report

```
## Flow audit: [flow name]

**Screens analyzed:** [list]

---

### Issues per screen

#### Screen 1: [name]
[issues table — same as individual audit]

#### Screen 2: [name]
[issues table]

...

---

### Cross-screen inconsistencies

| # | Screens involved | Inconsistency | Severity |
|---|---|---|---|
| 1 | [S1 ↔ S3] | [description] | 🔴/🟡/🟢 |

---

### Full corrected version
[corrected copy for each screen]

---

### Summary
- **Total issues:** [n] (🔴 [n] critical · 🟡 [n] medium · 🟢 [n] minor)
- **Cross-screen inconsistencies:** [n]
- **Recurring patterns:** [list of errors appearing on multiple screens]
- **Main recommendation:** [1–2 lines on the most important systemic issue]
```

---

## Severities

- 🔴 **Critical:** Voseo, third person, ustedeo, corporate jargon, empty superlatives, error without a way out, terminology inconsistency that confuses the user.
- 🟡 **Medium:** Avoidable passive voice, unnecessary anglicism, too many exclamations, wrong format, length exceeded, tone unfit for the context.
- 🟢 **Minor:** Opportunity to improve tone, could be more direct, small inconsistency that doesn't hurt comprehension.

---

## References

For advanced cases or detailed lookup, read files in `references/`:

| File | Contents | When to read |
|---|---|---|
| `references/voice.md` | Full writing rules, regionalisms, CTAs, lengths | Cases with many specific rules |
| `references/tone.md` | Detailed tone by context with examples | Doubt about appropriate tone |
| `references/microcopy.md` | UI component guide with examples | Specific or uncommon component |
| `references/states.md` | Vocabulary for operation and user states | State texts / pills |
| `references/patterns.md` | 25 most frequent patterns and anti-patterns | Quick check before publishing |
| `references/emails.md` | Email structure and examples | Email audit or writing |
| `references/notifications.md` | Push and in-app with examples | Notification audit or writing |
| `references/vocabulary.md` | Preferred vocabulary + full HR glossary | Specific term in doubt |
| `references/checklist.md` | Full audit checklist | Exhaustive check before publishing |
