fede-voice · git:20260929.4f79e38 · 2026-09-29 · sha256 706dbb9e92462135
fede-voice git:20260929.4f79e38A
Immutable. This exact content never changes and is served at /api/v1/blob/706dbb9e92462135.
--- name: fede-voice description: Draft or rewrite DMs and public posts in Federico De Ponte's documented voice. Use for writing as Federico; this is a finished profile. --- # Fede Voice Write in Federico's documented style. Use the supplied thread, notes, or verified source for substance. Never borrow a claim, relationship, metric, or opinion from a style example. If a needed fact is missing, ask or mark it for confirmation. To build a new person's profile, use `clone-my-voice`. ## Private messages - Follow the thread's language. Use Federico's own prior messages as the closest style reference when available. - Write lowercase fragments, usually two or three short lines with one thought per line. A short question fragment, casual abbreviation, `...`, or occasional `:D` can fit. - Skip greetings, signoffs, bullets, numbered prose, bold emphasis, and polished transitions. - Suggest rather than command. Keep the stakes at the level Federico stated. ## Public posts - Use normal sentence capitalization and short paragraphs separated by blank lines. Keep each beat concrete and easy to scan. - Open with a real reader problem, event, constraint, or result from supplied material. If a hook borrows a proven shape, identify its source outside the post. Never manufacture a first-person event or measured result. - Put the payoff in the post. Show what happened, then stop after the last supported fact. No tidy summary or engagement question at the end. - Prefer everyday language to technical feature lists. Preserve Federico's phrasing when editing his notes. ## Across formats - No em dash (`—`) or en dash (`–`). Use a period, comma, or colon. - Avoid “game changer,” “excited to announce,” “unlock,” “revolutionary,” artificial urgency, generic praise, and a writerly closing line. - Keep sentences short and direct. One idea per sentence is a useful default, not a fixed word count. - Check counts, names, dates, and claims against the actual source. Do not invent them for style. ## Short pattern examples These are synthetic style illustrations, not Federico's messages or product claims. Replace their facts with the user's real context. **DM, German** > könnte gut passen > sollen wir das morgen kurz testen? **DM, English** > looks useful actually > want me to try it first? **Post opening** > We tested the draft with 12 people. > > Each revision took 30 minutes less in this synthetic example. **Post ending** > The team kept the shorter version. Stop there when that is the last supported fact.