fede-voice git:20260929.dff6ee8A

Immutable. This exact content never changes and is served at /api/v1/blob/898dcbb45e51fa99.

---
name: fede-voice
description: Build a reusable voice profile from a person's own writing, then draft or rewrite DMs and posts in that voice. Use when someone asks for text in their voice or Federico's voice, especially with a no-dash constraint.
---

# Write in a person's voice

Use the author's own sent writing as evidence. Do not infer a voice from incoming messages, a biography, or a topic brief. If samples are unavailable, ask for 5 to 10 representative pieces or make a clearly labelled provisional draft from the user's explicit rules.

## Build the profile

1. Sort samples by format: private messages, public posts, email, and so on. Recent examples and explicit corrections outrank old examples. Keep the original language of each sample.
2. Record observable rules: typical sentence and paragraph length, capitalization, greetings, closers, punctuation, emoji, contractions, recurring words, hooks, and phrases the author rejects. Keep a private source pointer beside each inferred rule; quote a sample only when the author explicitly wants it stored. Redact third-party names and confidential details.
3. Separate facts from style. A sample's claims, people, metrics, or opinions are not reusable facts for a new draft.
4. Write a compact profile with format-specific rules, 3 abstract pattern examples, banned patterns, and an uncertainty note. Keep the profile in the current conversation by default; save it only at the author’s request, in the destination they choose. Do not retain raw samples in the saved profile. Ask the author to approve or correct it. Update rules after corrections.

## Draft or rewrite

- Read the current thread or raw notes first. Preserve the intended point, language, factual claims, and relationship context. Never invent a personal event, metric, endorsement, or urgency.
- Pick the profile section for this format. Match the author's rhythm and casing; do not flatten all formats into one style.
- For a rewrite, change phrasing and structure only as far as needed. For a new draft without source facts, ask for the missing substance.
- Compare the result with 2 or 3 samples of the same format. Remove generic hooks, polished filler, and any banned punctuation. Return the draft without an essay about your choices.

## Worked profile: Federico

This is an example of how a profile can differ by format. It is not the default for other people.

**Private messages:** lowercase fragments, usually 2 or 3 short lines; no greeting, signoff, or bullet list. Casual abbreviations and an occasional question fragment can fit. Suggest rather than command. Match the language of the thread.

**Public posts:** normal sentence capitalization. Short paragraphs, a concrete opening tied to the reader's problem, then the actual event or result from supplied notes. Keep the payoff in the post. A hook must be grounded in a real sample or result, never manufactured. No inflated stakes or tidy writerly closer.

**Across both:** no em dash or en dash. No invented first-person claim, artificial urgency, stock phrases such as “game changer” or “excited to announce,” or closing question added for engagement. Keep real numbers and names only when the supplied source supports them.