[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BFX09MYSAKVZCM1713YAE":3,"skill-same:01M75BFX09MYSAKVZCM1713YAE":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75BFX09MYSAKVZCM1713YAE","write-french",null,"Use when the output is French - a chat reply in French, or a French markdown deliverable such as a guide, a report or a synthesis - including when the user writes in French and expects French back. Prevents French that reads as translated English: word-for-word calques, sentences compressed until the meaning is gone, jargon used before it is defined, invented turns of phrase.","NormandErwan\u002FClaude","NormandErwan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7470865?v=4","01M75BENGB5CYYFMHFPN2P5VDN","Erwan Normand","01M75BENH549BJRCTY1483T64R",1,"BSD-3-Clause","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: write-french\nversion: 1.6.2\ndescription: \"Use when the output is French - a chat reply in French, or a French markdown deliverable such as a guide, a report or a synthesis - including when the user writes in French and expects French back. Prevents French that reads as translated English: word-for-word calques, sentences compressed until the meaning is gone, jargon used before it is defined, invented turns of phrase.\"\n---\n\n# Write French\n\n## Overview\n\nFrench produced without care keeps English thinking under French words. A native\nreader rarely calls it wrong; they call it foreign, and they slow down to guess\nwhat was meant.\n\n**Core principle:** write the sentence a French speaker would have written to say\nthat thing - not the French translation of the English sentence.\n\nRules below are in English, examples in French with their accents. A translated\nexample proves nothing about French.\n\n## When to Use\n\n- Any French output: chat replies, guides, reports, syntheses\n- The user writes in French, so the reply is French\n\n**Not for:** skills, commit messages, PR bodies, code, code comments,\nREADME files and manifests - English by repo rule.\n\n## Concision Has A Floor\n\nCut filler, politeness, hedging and restatement, always. Never cut a subject, a\nverb, an article, a preposition or a linking word that carries the meaning.\n\nA sentence that is short because a load-bearing word is missing is not concise,\nit is broken: the reader spends more effort rebuilding it than the word would\nhave cost. Concision is measured in ideas - one idea per sentence, no idea\ntwice - never in characters saved.\n\n## The Six Defects\n\n### 1. Calque - English phrasing carried over word for word\n\nThe phrase only makes sense once translated back into English. Test: translate\nit back; if the English reads better, the French is a calque.\n\n| Instead of | Write |\n|---|---|\n| « Tu seras moins souvent l'expert de la pièce » | « Tu ne seras plus le plus compétent de l'équipe sur chaque sujet » |\n| « le bruit venu d'en haut » | « les demandes et les urgences de la direction » |\n| « Fréquent et petit vaut mieux que rare et solennel » | « Mieux vaut un retour court et régulier qu'un long entretien une fois par an » |\n| « c'est un défaut de conception » (d'une équipe) | « c'est ton organisation qui est en cause, pas les personnes » |\n\n### 2. Compression that costs the meaning\n\nA word carrying the meaning was dropped to make the sentence shorter.\n\nThe excuse changes, the defect doesn't. A writer who prizes saying a lot in a\nfew words will drop a verb or a referent on the second half of a sentence and\ncall the result elegant - « X ne fait pas ceci, Y si » (Y does, but the verb\nthat says so is never written again). It isn't elegant: a reader has to\nsilently supply whatever was left out, on the writer's behalf, before the\nsentence closes. Test: say the sentence once, aloud, as if to someone hearing\nit for the first time. If a word is missing before they'd understand it, put\nthe word back - a shorter sentence that costs the reader a reconstruction is\nnot concise, per the concision floor above.\n\n| Instead of | Write |\n|---|---|\n| « Ta valeur devient indirecte » | « Ce que tu apportes passe désormais par le travail des autres » |\n| « jamais annulé - déplacé au pire » | « Ne l'annule jamais : au pire, déplace-le » |\n| « Réversible et peu coûteuse : tranche vite, seul » | « Quand la décision est réversible et peu coûteuse, tranche vite et seul » |\n| « La procédure ne change pas, son destinataire si » | « La procédure reste la même. Seul le destinataire de ce qu'elle produit change. » |\n\n### 3. Term used before being defined\n\nOne test covers every shape this defect takes: strip away what the reader is\nassumed to already know, and check whether the sentence itself still says what a\nreference means and why it is here. If it doesn't, the reference is undefined -\nwhether that reference is an abstract management noun, a legal term of art, a\ntrade word, a named person or framework, a bare acronym or initialism, the\ndocument's own coined shorthand, or one name lost inside a list of several. The\nforms differ; the failure is always the same one: the writer already knows what\nit means, so the sentence never bothers to say it.\n\nThe test does not depend on who the reader is - which is exactly why \"would a\nreader outside the field stumble?\" is the wrong question for a named authority or\na trade acronym: a reader fluent in the field is precisely who stops noticing\nthese went unglossed. Ask the sentence-only question instead: could you write\nout, right now, in French, what this stands for and why it matters here? If the\nsentence doesn't already say that, neither does the reader's memory of it - and\nneither does an appendix or bibliography elsewhere in the document, since the\nreader meets the term in the body first, on a single read-through.\n\nOne shape needs a different fix, not a different test: several such references\nthrown into one enumerating clause (« s'appuie sur des auteurs identifiés —\nNygard, Brown, Fowler, Klein, Cockburn, Fairbanks, Poppendieck »). Glossing every\nname inline trades this defect for defect 6 - a wall of parenthetical asides.\nApply the same test per name instead: is this one's contribution established\nanywhere else in the document? Yes - leave it bare here; that other point is its\nreal first use, and the list is only an index of it. Never - it fails the test\nexactly as an unglossed acronym would, so it has no place in the enumerating\nclause: cut it, and point to wherever the source list already lives (an annex, a\nbibliography) instead of pretending it was introduced in body prose.\n\nRule: any reference used in body prose - named person, framework, acronym,\ninternal shorthand, or one name inside a longer list - gets a one-clause gloss at\nfirst use, even when an appendix explains it in full or the term is a recognized\nindustry standard inside the field. A guide must be self-contained on a single\nread-through; a reader does not arrive at paragraph three having already read the\nannex, and does not carry a professional certification just because the writer\ndoes.\n\nA repository's own English term (a file's nickname, a process name: ledger,\nhandoff, hook) is a reference too. It has a plain French equivalent -> write the\nFrench word in prose; keep the English name only as a file path or a command.\nThe same holds for any English technical term with an established French\nequivalent: write the French term, with the English one in parentheses at first\nuse if the reader may know it under that name. A borrowing already established in\nFrench stays (« le Web »).\n\n| Instead of | Write |\n|---|---|\n| « Tu as maintenant un pouvoir asymétrique » | « Tu évalues les autres, ils ne t'évaluent pas : la même remarque n'a plus le même poids » |\n| « un comportement toxique » | « des remarques qui humilient quelqu'un devant les autres » |\n| « le squelette ambulant de Cockburn, les tranches de release de Patton » | « le squelette ambulant d'Alistair Cockburn - une version minimale de l'application, qui prouve que l'architecture tient - et les tranches de release de Jeff Patton - des regroupements d'éléments assez complets pour être démontrés » |\n| « le critère testable d'INVEST » | « le critère testable d'INVEST - la grille en six critères (Independent, Negotiable, Valuable, Estimable, Small, Testable) qui évalue une user story » |\n| « le slicing des tâches » | « le découpage des tâches » |\n| « Le ledger compte 17 entrées » | « Le registre des rétrospectives (`RETROSPECTIVE.md`) compte 17 entrées » |\n| « Écrire cette frontière avant le premier raffinage » | « Décider par écrit, avant le premier raffinage, ce qui relève du raffinage interne ou de l'avenant contractuel » |\n| « Le reste s'appuie sur des auteurs identifiés — Nygard, Brown, Fowler, Klein, Cockburn, Fairbanks, Poppendieck — et sur des compositions assumées » | « Le reste s'appuie sur des auteurs identifiés — Nygard, Brown, Fowler et Fairbanks — et sur des compositions assumées. Ces quatre noms sont cités et glosés plus loin dans le texte. La liste complète des sources est en annexe E. » |\n\n### 4. Wrong or non-existent French\n\n| Instead of | Write |\n|---|---|\n| « N'intervient que si le résultat est en jeu » | « N'interviens que si le résultat est en jeu » |\n| « en public et en précis » | « en public et de façon précise » |\n\n### 5. Lexical ambiguity\n\nThe first reading is not the intended one, the turn of phrase was invented, or a\nprecise\u002Festablished term was swapped for one that only sounds more idiomatic and\nthe meaning drifted in the process. In a technical, legal or administrative\nregister, native means the specialist's exact term, not a looser paraphrase -\ncheck that a swap means exactly the same thing before trusting that it reads\nmore fluently. This is different from defect 3: there, the term is undefined for\nthe reader; here, the term was correct and got traded away.\n\n| Instead of | Write |\n|---|---|\n| « Les gens se contredisent en réunion » | « Les gens osent contredire les autres en réunion » |\n| « pèse lourd chez l'autre » | « prend beaucoup d'importance pour la personne qui la reçoit » |\n| « une contestation orale ne vaut plus rien » | « une contestation orale ne vaut rien » |\n\n### 6. One sentence, several ideas\n\nEvery word is fine and the French is correct - the sentence just joins two\nindependent claims at a conjunction, dash or colon. Not a calque, not compression:\nsplitting it changes nothing but the number of sentences. Test: if the sentence\ncontains two clauses each of which could stand alone as a complete, meaningful\nsentence, split it at the joint. This is different from defect 2 - there, a word\nis missing; here, nothing is missing, there is just too much in one sentence.\n\nThree or more parallel claims chained by semicolons are the same defect at a\nlarger scale - and splitting them into bare, unconnected sentences loses the\none thing that justified grouping them: that they stand as independent\nevidence for the same point. Fix by announcing the group in a lead sentence,\nthen giving each claim its own sentence. A semicolon rarely earns its place in\nFrench prose; when several claims need to be held together, a colon that\nintroduces them does the job the semicolons were being asked to do.\n\n| Instead of | Write |\n|---|---|\n| « Cette frontière n'est pas étanche, et il vaut mieux le dire que le masquer : cinq points du document ont besoin d'un dimensionnement pour fonctionner — E2.5, §5.2... » | « Cette frontière a une exception, assumée plutôt que cachée. Cinq points du document ont besoin d'un minimum de dimensionnement pour fonctionner : E2.5, §5.2... » |\n| « Il ne correspond ni à une couche (« la base de données »), ni à un composant (« le service d'authentification »). » | « Il ne correspond pas à une couche, comme « la base de données ». Il ne correspond pas non plus à un composant, comme « le service d'authentification ». » |\n| « se lit mieux que « Import d'un fichier conforme », et c'est la forme employée par les patterns du §4 » | « « Importer un fichier conforme » se lit mieux que « Import d'un fichier conforme ». C'est aussi la forme employée par les patterns du §4. » |\n| « Un découpage qui n'a que des tranches n'a pas de périmètre — il ne peut ni se contractualiser, ni se contrôler en couverture » | « Un découpage qui ne contient que des tranches, sans lots, n'a pas de périmètre : il ne peut ni être contractualisé, ni être contrôlé en couverture. » |\n| « Trois signaux le confirment : la charge a doublé sans aide supplémentaire ; les retards s'accumulent depuis trois semaines ; deux personnes ont demandé un point individuel cette semaine » | « Trois signaux le confirment. La charge a doublé sans aide supplémentaire. Les retards s'accumulent depuis trois semaines. Deux personnes ont demandé un point individuel cette semaine. » |\n| « Ce découpage montre un résultat utilisable dès la première tranche, alors qu'un découpage en couches oblige à finir toute la base de données avant qu'un seul écran fonctionne » | « Ce découpage montre un résultat utilisable dès la première tranche. Un découpage en couches oblige au contraire à finir toute la base de données avant qu'un seul écran fonctionne. » |\n\n## Review Pass - Markdown Deliverables Only\n\nRequired before delivering a French guide, report or synthesis. Not required for\nchat replies: applying the rules while writing is enough there.\n\n1. Read each sentence against the six defects, one category at a time. Mixing\n   the categories in one pass hides the ones you are not looking for.\n2. Rewrite only the sentences that actually hit a defect. A sentence with none\n   stays untouched - polishing a clean sentence for style, not to fix a listed\n   defect, is how new defects get introduced.\n3. Rewrite each hit, then re-check the rewrite against all six. Removing a\n   calque by compressing further moves the defect into category 2, it does not\n   remove it.\n4. Last check on the whole text: every jargon term defined at first use, no English\n   term that has an established French one, every sentence has a subject and a verb.\n5. Grill the sentences you found yourself admiring. A sentence that struck you\n   as tight, elegant or well-turned while writing it is exactly the one to\n   interrogate - the same way a design decision gets questioned before it is\n   accepted, not after. Ask what it assumes the reader already knows or can\n   reconstruct alone: which word, referent or link did you leave for them to\n   supply? Say the sentence once, aloud, as if to someone hearing it for the\n   first time with no access to the rest of the document. If they would\n   stumble, or need it twice, the elegance was yours, not theirs - rewrite it.\n   This step exists because defects 1-6 are patterns, and a sentence can be\n   hard to parse on one read without matching any of them by the letter -\n   grill it anyway; the reader doesn't care which numbered defect it was.\n   Default to plain, direct phrasing over any rhetorical construction -\n   cleft sentence (« C'est X qui... »), elliptical antithesis (« X ne fait\n   pas ceci, Y si »), a subject-verb-splitting aside (« Le projet — lancé\n   en janvier, repoussé deux fois — a finalement livré »), or other. It\n   earns its place only by being clearer, never denser: dense rhetoric is\n   exactly what makes a writer misjudge their own sentence as elegant, so\n   it gets no benefit of the doubt.\n\n## Red Flags - Stop And Rewrite\n\n- The English back-translation reads better than your French\n- An adjective doing the work of a noun (« Fréquent et petit vaut mieux... »)\n- A colon or a dash standing in for the verb\n- An abstract noun carrying the sentence: valeur, impact, niveau, dimension\n- A jargon term used now, explained later, or never\n- A named person, framework, bare acronym\u002Finitialism or internal shorthand term\n  with no gloss at first use, even if an appendix explains it or the acronym is\n  well known inside the field\n- A list of several bare names in one clause where some never come back with\n  a gloss anywhere else in the document\n- A sentence you could cut in two with a period and lose nothing\n- A cleft sentence, elliptical antithesis, subject-verb-splitting\n  parenthetical, or other rhetorical construction kept over its plain\n  rewrite without the rhetoric being clearer\n- You noticed a sentence was elegant before you noticed whether it was clear\n- A sentence you rewrote though it hit none of the six defects\n- An imperative form you did not actually check\n- A turn of phrase you cannot recall ever hearing\n\n## Common Mistakes\n\n- Shortening a clumsy sentence instead of rewriting it - defect 2 replaces defect 1\n- Defining a term two lines after its first use and calling it defined\n- Treating « toxique », « asymétrique », « indirect » as explanations\n- Treating jargon as a management-only problem - a legal term of art\n  (« contradictoire ») or a trade word (« pousse ») needs the same gloss\n- Treating a bibliography or appendix entry as a definition the body text can\n  skip - the reader meets the term in the body first\n- Treating a trade acronym (PMI, INVEST, SRD) as self-explanatory because\n  specialists in the field all recognize it - the test is whether the sentence\n  itself says what it stands for, never whether this reader would stumble on it\n- Treating a name in a list as covered because the list around it says \"des\n  auteurs\" - a category word glosses the list's shape, not any one name's\n  contribution\n- Swapping a precise term for a more idiomatic-sounding one and drifting the\n  meaning in the process - « ne vaut plus rien » is not « ne vaut rien »\n- Rewriting a sentence that had no defect, for style alone\n- Leaving two independent claims joined by « et », « : » or « — » because each\n  half, alone, is grammatically fine - defect 6 is about idea count, not grammar\n- Treating a sentence's tightness as evidence it is good, instead of testing\n  whether a first-time listener would parse it in one pass - cleverness is the\n  writer's reward, not the reader's; the grill step exists to catch this\n- Keeping a cleft sentence, elliptical antithesis, or subject-verb-splitting\n  parenthetical on a dense rhetorical register because it parses without a\n  defect, instead of defaulting to the plain phrasing - passing the six\n  defects is not a reason to prefer rhetoric\n- Running the review pass on a chat reply, or skipping it on a deliverable\n\n## Real-World Impact\n\nBenchmark history and per-version rationale: see `evidence.md`.\n","# Write French\n\n## Overview\n\nFrench produced without care keeps English thinking under French words. A native\nreader rarely calls it wrong; they call it foreign, and they slow down to guess\nwhat was meant.\n\n**Core principle:** write the sentence a French speaker would have written to say\nthat thing - not the French translation of the English sentence.\n\nRules below are in English, examples in French with their accents. A translated\nexample proves nothing about French.\n\n## When to Use\n\n- Any French output: chat replies, guides, reports, syntheses\n- The user writes in French, so the reply is French\n\n**Not for:** skills, commit messages, PR bodies, code, code comments,\nREADME files and manifests - English by repo rule.\n\n## Concision Has A Floor\n\nCut filler, politeness, hedging and restatement, always. Never cut a subject, a\nverb, an article, a preposition or a linking word that carries the meaning.\n\nA sentence that is short because a load-bearing word is missing is not concise,\nit is broken: the reader spends more effort rebuilding it than the word would\nhave cost. Concision is measured in ideas - one idea per sentence, no idea\ntwice - never in characters saved.\n\n## The Six Defects\n\n### 1. Calque - English phrasing carried over word for word\n\nThe phrase only makes sense once translated back into English. Test: translate\nit back; if the English reads better, the French is a calque.\n\n| Instead of | Write |\n|---|---|\n| « Tu seras moins souvent l'expert de la pièce » | « Tu ne seras plus le plus compétent de l'équipe sur chaque sujet » |\n| « le bruit venu d'en haut » | « les demandes et les urgences de la direction » |\n| « Fréquent et petit vaut mieux que rare et solennel » | « Mieux vaut un retour court et régulier qu'un long entretien une fois par an » |\n| « c'est un défaut de conception » (d'une équipe) | « c'est ton organisation qui est en cause, pas les personnes » |\n\n### 2. Compression that costs the meaning\n\nA word carrying the meaning was dropped to make the sentence shorter.\n\nThe excuse changes, the defect doesn't. A writer who prizes saying a lot in a\nfew words will drop a verb or a referent on the second half of a sentence and\ncall the result elegant - « X ne fait pas ceci, Y si » (Y does, but the verb\nthat says so is never written again). It isn't elegant: a reader has to\nsilently supply whatever was left out, on the writer's behalf, before the\nsentence closes. Test: say the sentence once, aloud, as if to someone hearing\nit for the first time. If a word is missing before they'd understand it, put\nthe word back - a shorter sentence that costs the reader a reconstruction is\nnot concise, per the concision floor above.\n\n| Instead of | Write |\n|---|---|\n| « Ta valeur devient indirecte » | « Ce que tu apportes passe désormais par le travail des autres » |\n| « jamais annulé - déplacé au pire » | « Ne l'annule jamais : au pire, déplace-le » |\n| « Réversible et peu coûteuse : tranche vite, seul » | « Quand la décision est réversible et peu coûteuse, tranche vite et seul » |\n| « La procédure ne change pas, son destinataire si » | « La procédure reste la même. Seul le destinataire de ce qu'elle produit change. » |\n\n### 3. Term used before being defined\n\nOne test covers every shape this defect takes: strip away what the reader is\nassumed to already know, and check whether the sentence itself still says what a\nreference means and why it is here. If it doesn't, the reference is undefined -\nwhether that reference is an abstract management noun, a legal term of art, a\ntrade word, a named person or framework, a bare acronym or initialism, the\ndocument's own coined shorthand, or one name lost inside a list of several. The\nforms differ; the failure is always the same one: the writer already knows what\nit means, so the sentence never bothers to say it.\n\nThe test does not depend on who the reader is - which is exactly why \"would a\nreader outside the field stumble?\" is the wrong question for a named authority or\na trade acronym: a reader fluent in the field is precisely who stops noticing\nthese went unglossed. Ask the sentence-only question instead: could you write\nout, right now, in French, what this stands for and why it matters here? If the\nsentence doesn't already say that, neither does the reader's memory of it - and\nneither does an appendix or bibliography elsewhere in the document, since the\nreader meets the term in the body first, on a single read-through.\n\nOne shape needs a different fix, not a different test: several such references\nthrown into one enumerating clause (« s'appuie sur des auteurs identifiés —\nNygard, Brown, Fowler, Klein, Cockburn, Fairbanks, Poppendieck »). Glossing every\nname inline trades this defect for defect 6 - a wall of parenthetical asides.\nApply the same test per name instead: is this one's contribution established\nanywhere else in the document? Yes - leave it bare here; that other point is its\nreal first use, and the list is only an index of it. Never - it fails the test\nexactly as an unglossed acronym would, so it has no place in the enumerating\nclause: cut it, and point to wherever the source list already lives (an annex, a\nbibliography) instead of pretending it was introduced in body prose.\n\nRule: any reference used in body prose - named person, framework, acronym,\ninternal shorthand, or one name inside a longer list - gets a one-clause gloss at\nfirst use, even when an appendix explains it in full or the term is a recognized\nindustry standard inside the field. A guide must be self-contained on a single\nread-through; a reader does not arrive at paragraph three having already read the\nannex, and does not carry a professional certification just because the writer\ndoes.\n\nA repository's own English term (a file's nickname, a process name: ledger,\nhandoff, hook) is a reference too. It has a plain French equivalent -> write the\nFrench word in prose; keep the English name only as a file path or a command.\nThe same holds for any English technical term with an established French\nequivalent: write the French term, with the English one in parentheses at first\nuse if the reader may know it under that name. A borrowing already established in\nFrench stays (« le Web »).\n\n| Instead of | Write |\n|---|---|\n| « Tu as maintenant un pouvoir asymétrique » | « Tu évalues les autres, ils ne t'évaluent pas : la même remarque n'a plus le même poids » |\n| « un comportement toxique » | « des remarques qui humilient quelqu'un devant les autres » |\n| « le squelette ambulant de Cockburn, les tranches de release de Patton » | « le squelette ambulant d'Alistair Cockburn - une version minimale de l'application, qui prouve que l'architecture tient - et les tranches de release de Jeff Patton - des regroupements d'éléments assez complets pour être démontrés » |\n| « le critère testable d'INVEST » | « le critère testable d'INVEST - la grille en six critères (Independent, Negotiable, Valuable, Estimable, Small, Testable) qui évalue une user story » |\n| « le slicing des tâches » | « le découpage des tâches » |\n| « Le ledger compte 17 entrées » | « Le registre des rétrospectives (`RETROSPECTIVE.md`) compte 17 entrées » |\n| « Écrire cette frontière avant le premier raffinage » | « Décider par écrit, avant le premier raffinage, ce qui relève du raffinage interne ou de l'avenant contractuel » |\n| « Le reste s'appuie sur des auteurs identifiés — Nygard, Brown, Fowler, Klein, Cockburn, Fairbanks, Poppendieck — et sur des compositions assumées » | « Le reste s'appuie sur des auteurs identifiés — Nygard, Brown, Fowler et Fairbanks — et sur des compositions assumées. Ces quatre noms sont cités et glosés plus loin dans le texte. La liste complète des sources est en annexe E. » |\n\n### 4. Wrong or non-existent French\n\n| Instead of | Write |\n|---|---|\n| « N'intervient que si le résultat est en jeu » | « N'interviens que si le résultat est en jeu » |\n| « en public et en précis » | « en public et de façon précise » |\n\n### 5. Lexical ambiguity\n\nThe first reading is not the intended one, the turn of phrase was invented, or a\nprecise\u002Festablished term was swapped for one that only sounds more idiomatic and\nthe meaning drifted in the process. In a technical, legal or administrative\nregister, native means the specialist's exact term, not a looser paraphrase -\ncheck that a swap means exactly the same thing before trusting that it reads\nmore fluently. This is different from defect 3: there, the term is undefined for\nthe reader; here, the term was correct and got traded away.\n\n| Instead of | Write |\n|---|---|\n| « Les gens se contredisent en réunion » | « Les gens osent contredire les autres en réunion » |\n| « pèse lourd chez l'autre » | « prend beaucoup d'importance pour la personne qui la reçoit » |\n| « une contestation orale ne vaut plus rien » | « une contestation orale ne vaut rien » |\n\n### 6. One sentence, several ideas\n\nEvery word is fine and the French is correct - the sentence just joins two\nindependent claims at a conjunction, dash or colon. Not a calque, not compression:\nsplitting it changes nothing but the number of sentences. Test: if the sentence\ncontains two clauses each of which could stand alone as a complete, meaningful\nsentence, split it at the joint. This is different from defect 2 - there, a word\nis missing; here, nothing is missing, there is just too much in one sentence.\n\nThree or more parallel claims chained by semicolons are the same defect at a\nlarger scale - and splitting them into bare, unconnected sentences loses the\none thing that justified grouping them: that they stand as independent\nevidence for the same point. Fix by announcing the group in a lead sentence,\nthen giving each claim its own sentence. A semicolon rarely earns its place in\nFrench prose; when several claims need to be held together, a colon that\nintroduces them does the job the semicolons were being asked to do.\n\n| Instead of | Write |\n|---|---|\n| « Cette frontière n'est pas étanche, et il vaut mieux le dire que le masquer : cinq points du document ont besoin d'un dimensionnement pour fonctionner — E2.5, §5.2... » | « Cette frontière a une exception, assumée plutôt que cachée. Cinq points du document ont besoin d'un minimum de dimensionnement pour fonctionner : E2.5, §5.2... » |\n| « Il ne correspond ni à une couche (« la base de données »), ni à un composant (« le service d'authentification »). » | « Il ne correspond pas à une couche, comme « la base de données ». Il ne correspond pas non plus à un composant, comme « le service d'authentification ». » |\n| « se lit mieux que « Import d'un fichier conforme », et c'est la forme employée par les patterns du §4 » | « « Importer un fichier conforme » se lit mieux que « Import d'un fichier conforme ». C'est aussi la forme employée par les patterns du §4. » |\n| « Un découpage qui n'a que des tranches n'a pas de périmètre — il ne peut ni se contractualiser, ni se contrôler en couverture » | « Un découpage qui ne contient que des tranches, sans lots, n'a pas de périmètre : il ne peut ni être contractualisé, ni être contrôlé en couverture. » |\n| « Trois signaux le confirment : la charge a doublé sans aide supplémentaire ; les retards s'accumulent depuis trois semaines ; deux personnes ont demandé un point individuel cette semaine » | « Trois signaux le confirment. La charge a doublé sans aide supplémentaire. Les retards s'accumulent depuis trois semaines. Deux personnes ont demandé un point individuel cette semaine. » |\n| « Ce découpage montre un résultat utilisable dès la première tranche, alors qu'un découpage en couches oblige à finir toute la base de données avant qu'un seul écran fonctionne » | « Ce découpage montre un résultat utilisable dès la première tranche. Un découpage en couches oblige au contraire à finir toute la base de données avant qu'un seul écran fonctionne. » |\n\n## Review Pass - Markdown Deliverables Only\n\nRequired before delivering a French guide, report or synthesis. Not required for\nchat replies: applying the rules while writing is enough there.\n\n1. Read each sentence against the six defects, one category at a time. Mixing\n   the categories in one pass hides the ones you are not looking for.\n2. Rewrite only the sentences that actually hit a defect. A sentence with none\n   stays untouched - polishing a clean sentence for style, not to fix a listed\n   defect, is how new defects get introduced.\n3. Rewrite each hit, then re-check the rewrite against all six. Removing a\n   calque by compressing further moves the defect into category 2, it does not\n   remove it.\n4. Last check on the whole text: every jargon term defined at first use, no English\n   term that has an established French one, every sentence has a subject and a verb.\n5. Grill the sentences you found yourself admiring. A sentence that struck you\n   as tight, elegant or well-turned while writing it is exactly the one to\n   interrogate - the same way a design decision gets questioned before it is\n   accepted, not after. Ask what it assumes the reader already knows or can\n   reconstruct alone: which word, referent or link did you leave for them to\n   supply? Say the sentence once, aloud, as if to someone hearing it for the\n   first time with no access to the rest of the document. If they would\n   stumble, or need it twice, the elegance was yours, not theirs - rewrite it.\n   This step exists because defects 1-6 are patterns, and a sentence can be\n   hard to parse on one read without matching any of them by the letter -\n   grill it anyway; the reader doesn't care which numbered defect it was.\n   Default to plain, direct phrasing over any rhetorical construction -\n   cleft sentence (« C'est X qui... »), elliptical antithesis (« X ne fait\n   pas ceci, Y si »), a subject-verb-splitting aside (« Le projet — lancé\n   en janvier, repoussé deux fois — a finalement livré »), or other. It\n   earns its place only by being clearer, never denser: dense rhetoric is\n   exactly what makes a writer misjudge their own sentence as elegant, so\n   it gets no benefit of the doubt.\n\n## Red Flags - Stop And Rewrite\n\n- The English back-translation reads better than your French\n- An adjective doing the work of a noun (« Fréquent et petit vaut mieux... »)\n- A colon or a dash standing in for the verb\n- An abstract noun carrying the sentence: valeur, impact, niveau, dimension\n- A jargon term used now, explained later, or never\n- A named person, framework, bare acronym\u002Finitialism or internal shorthand term\n  with no gloss at first use, even if an appendix explains it or the acronym is\n  well known inside the field\n- A list of several bare names in one clause where some never come back with\n  a gloss anywhere else in the document\n- A sentence you could cut in two with a period and lose nothing\n- A cleft sentence, elliptical antithesis, subject-verb-splitting\n  parenthetical, or other rhetorical construction kept over its plain\n  rewrite without the rhetoric being clearer\n- You noticed a sentence was elegant before you noticed whether it was clear\n- A sentence you rewrote though it hit none of the six defects\n- An imperative form you did not actually check\n- A turn of phrase you cannot recall ever hearing\n\n## Common Mistakes\n\n- Shortening a clumsy sentence instead of rewriting it - defect 2 replaces defect 1\n- Defining a term two lines after its first use and calling it defined\n- Treating « toxique », « asymétrique », « indirect » as explanations\n- Treating jargon as a management-only problem - a legal term of art\n  (« contradictoire ») or a trade word (« pousse ») needs the same gloss\n- Treating a bibliography or appendix entry as a definition the body text can\n  skip - the reader meets the term in the body first\n- Treating a trade acronym (PMI, INVEST, SRD) as self-explanatory because\n  specialists in the field all recognize it - the test is whether the sentence\n  itself says what it stands for, never whether this reader would stumble on it\n- Treating a name in a list as covered because the list around it says \"des\n  auteurs\" - a category word glosses the list's shape, not any one name's\n  contribution\n- Swapping a precise term for a more idiomatic-sounding one and drifting the\n  meaning in the process - « ne vaut plus rien » is not « ne vaut rien »\n- Rewriting a sentence that had no defect, for style alone\n- Leaving two independent claims joined by « et », « : » or « — » because each\n  half, alone, is grammatically fine - defect 6 is about idea count, not grammar\n- Treating a sentence's tightness as evidence it is good, instead of testing\n  whether a first-time listener would parse it in one pass - cleverness is the\n  writer's reward, not the reader's; the grill step exists to catch this\n- Keeping a cleft sentence, elliptical antithesis, or subject-verb-splitting\n  parenthetical on a dense rhetorical register because it parses without a\n  defect, instead of defaulting to the plain phrasing - passing the six\n  defects is not a reason to prefer rhetoric\n- Running the review pass on a chat reply, or skipping it on a deliverable\n\n## Real-World Impact\n\nBenchmark history and per-version rationale: see `evidence.md`.\n",{"name":5,"version":24,"description":7},"1.6.2","main","336ef9f9a6dd71a2cc287082873fa3c8597dcf75","skills\u002Fwrite-french",0,"https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude","https:\u002F\u002Fgithub.com\u002FNormandErwan","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fnormanderwan\u002F","2026-11-11 04:37:11",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add NormandErwan\u002FClaude --skill write-french",{"tool":39,"command":40},"bunx","bunx skills add NormandErwan\u002FClaude --skill write-french",{"tool":42,"command":43},"pnpm","pnpm dlx skills add NormandErwan\u002FClaude --skill write-french","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002FSKILL.md",true,[47,53,57,61,65,69],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"evidence.md","REFERENCE","参考文档",8535,"https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002Fevidence.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"examples\u002Fbaseline-guide-pastry.md",7467,"https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002Fexamples\u002Fbaseline-guide-pastry.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"examples\u002Fbaseline-guide-tenant-rights.md",6847,"https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002Fexamples\u002Fbaseline-guide-tenant-rights.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"examples\u002Fbaseline-guide.md",6013,"https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002Fexamples\u002Fbaseline-guide.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"examples\u002Fbaseline-synthesis-sleep-memory.md",6807,"https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002Fexamples\u002Fbaseline-synthesis-sleep-memory.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"examples\u002Fdefect-grid.md",5113,"https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-french\u002Fexamples\u002Fdefect-grid.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M75BG0TBQH53V52ZF840MGD2","write-guide","Use when writing a guide someone else will follow - a method guide, a playbook, a how-we-do-it document for a team or a client - or when reworking, auditing or extending one that already exists. Also when an outline is handed to you to fill in, when a guide's rules need evidence labels, or when a second guide joins the first and the two start contradicting each other.","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-guide\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M75BFQQ0EPV92467E0C40CEX","verify-sources","Use when about to state a factual, technical, historical, or procedural claim in ANY domain (software, DIY\u002Fcraft, health, legal, finance...) - a version number, default value, statistic, API behavior, a legal deadline, a health claim, a manufacturer spec, \"X always\u002Fnever does Y\", \"the docs say\", \"best practice is\" - that you have not verified against a source this turn, or when tempted to answer a factual question from memory under time pressure","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fverify-sources\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M75BFJW35J7NT1MGEZ0P477T","token-file-ops","Use when reading, editing, creating, or manipulating files; or running commands with potentially large output. Provides generic bash-first patterns for any file type.","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Ftoken-file-ops\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M75BFEFWPR9ZXEWACJJBQBRS","token-codebase-exploration","Use when exploring an unfamiliar codebase, understanding how a specific feature or pattern works, or learning how components interact. Provides the exploration workflow and strategy.","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Ftoken-codebase-exploration\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M75BFBQA8JWX7TFPDWTCTFW2","teach","Use when the user sets learning a topic or skill as their own goal - \"teach me X\", \"I want to learn X\", \"help me get good at X\", a course or study plan for themselves. Not for a question one reply answers (\"what is X\", \"explain X\").","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M75BF8H0DK5VBG33Z5ZW83X4","search-first","Use before writing any script, config, workflow or service that automates a task or connects two systems - even when a standard approach seems obvious. Search for an existing tool, package, GitHub Action or service first, then adopt, extend, compose or build.","MIT","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fsearch-first\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNormandErwan\u002FClaude\u002Fblob\u002Fmain\u002Fskills\u002Fsearch-first\u002FSKILL.md",[],[]]