QuQi

Build a Voice Guide From Published Work

Voice guides are usually a list of adjectives - clear, confident, human, approachable - which every writer already believes describes them, so no draft changes. The useful artefact is descriptive rather than aspirational: it names the patterns in the pages you already consider good and shows the rejected alternative beside each one. Build it once you have enough published work to sample from, and rebuild it when the people doing the writing turn over.

Obtenir le fichier de compétence Laissez les agents s’en charger
CATÉGORIE
Production de contenu
FORMAT
voice-guide-from-published-work.md
ÉTAPES
7
PRIX
Gratuit — sans compte
QUAND S’EN SERVIR

Use when several writers are producing pages that each read differently and nobody can state concretely what the house voice is.

Le fichier de compétence

voice-guide-from-published-work.md
---
name: voice-guide-from-published-work
description: Use when several writers are producing pages that each read differently and nobody can state concretely what the house voice is.
---

# Build a Voice Guide From Published Work

Voice guides are usually a list of adjectives - clear, confident, human, approachable - which every writer already believes describes them, so no draft changes. The useful artefact is descriptive rather than aspirational: it names the patterns in the pages you already consider good and shows the rejected alternative beside each one. Build it once you have enough published work to sample from, and rebuild it when the people doing the writing turn over.

## Ce qu’il vous faut d’abord

- ten to fifteen published pages the team agrees are good, picked before any analysis
- three or four pages the team considers off-voice, which are what make the rules legible
- the actual editing notes from recent review rounds, which usually contain the rules already
- a decision on who holds final say on voice, or the guide gets argued with instead of used

## Méthode

1. Collect the good and the bad samples first and do not justify the choices yet. Choosing by feel and then finding the pattern is more honest than deciding a pattern and hunting for evidence of it.
2. Read the openings of all the samples side by side. Openings carry most of the perceived voice, and the difference between the two piles is usually visible within two sentences.
3. Extract mechanical facts rather than impressions: typical sentence length, whether you address the reader as you, whether contractions appear, whether headings are questions or noun phrases. These are checkable by a writer at midnight; "confident" is not.
4. Mine the last few rounds of editing notes for repeated corrections. Any note an editor has written three times is already a rule and belongs in the guide.
5. Write each rule as a pair: one sentence from a real published page, and the version you rejected. Paired examples change drafts, adjectives do not.
6. Cap the guide at two pages and put the three most broken rules at the top. A long guide is read once during onboarding and never opened again.
7. Add a short banned list of constructions you will always cut, so writers stop producing them rather than editors removing them every time.

## Ce que ça produit

A two-page descriptive voice guide with mechanical rules, paired before-and-after examples and a banned-construction list.

## Là où ça dérape

- Writing the guide from how you wish you sounded rather than from pages you actually published, producing a document no draft ever matches
- Filling it with format rules such as heading levels and image sizes, which buries the writing guidance readers came for
- Freezing it, so it enforces the habits of writers who left and obstructs the ones who arrived

---

Extrait de la bibliothèque de compétences QuQi - https://www.quqi.io/fr/skills/voice-guide-from-published-work
Téléchargement gratuit · sans compte, sans e-mail

Ce qu’il vous faut d’abord

  • ten to fifteen published pages the team agrees are good, picked before any analysis
  • three or four pages the team considers off-voice, which are what make the rules legible
  • the actual editing notes from recent review rounds, which usually contain the rules already
  • a decision on who holds final say on voice, or the guide gets argued with instead of used

Méthode

  1. 01 Collect the good and the bad samples first and do not justify the choices yet. Choosing by feel and then finding the pattern is more honest than deciding a pattern and hunting for evidence of it.
  2. 02 Read the openings of all the samples side by side. Openings carry most of the perceived voice, and the difference between the two piles is usually visible within two sentences.
  3. 03 Extract mechanical facts rather than impressions: typical sentence length, whether you address the reader as you, whether contractions appear, whether headings are questions or noun phrases. These are checkable by a writer at midnight; "confident" is not.
  4. 04 Mine the last few rounds of editing notes for repeated corrections. Any note an editor has written three times is already a rule and belongs in the guide.
  5. 05 Write each rule as a pair: one sentence from a real published page, and the version you rejected. Paired examples change drafts, adjectives do not.
  6. 06 Cap the guide at two pages and put the three most broken rules at the top. A long guide is read once during onboarding and never opened again.
  7. 07 Add a short banned list of constructions you will always cut, so writers stop producing them rather than editors removing them every time.

Ce que ça produit

A two-page descriptive voice guide with mechanical rules, paired before-and-after examples and a banned-construction list.

Là où ça dérape

  • Writing the guide from how you wish you sounded rather than from pages you actually published, producing a document no draft ever matches
  • Filling it with format rules such as heading levels and image sizes, which buries the writing guidance readers came for
  • Freezing it, so it enforces the habits of writers who left and obstructs the ones who arrived

Utiliser cette compétence dans votre propre IA

Le fichier téléchargé est un simple markdown dont l'en-tête porte le nom et le déclencheur. Quand un assistant sait charger des compétences tout seul, c'est cet en-tête qu'il lit pour décider que celle-ci s'applique.

Claude Code Enregistrez-le sous ~/.claude/skills/voice-guide-from-published-work/SKILL.md et Claude le charge tout seul dès que ce que vous faites correspond au déclencheur. Placez-le plutôt dans .claude/skills d'un projet si toute l'équipe doit l'avoir.
Claude Importez le fichier dans la section compétences de vos réglages. Une fois là, il s'applique tout seul dans toute conversation où le déclencheur colle, sans que vous ayez à y penser.
ChatGPT Il n'existe pas de format de compétences où l'installer, alors collez le contenu du fichier dans les instructions d'un Projet ou d'un GPT personnalisé. Il s'applique ensuite à toutes les conversations du projet, pas seulement à celle où vous l'avez collé.
Tout le reste Collez le markdown dans la conversation avant votre question. Cela fonctionne avec n'importe quel assistant, il faut simplement le recoller à chaque fois.

Plus dans Production de contenu