---
language: en
schemaVersion: 1
---

# Accumulated language rules — `<language>`

> **OPT-IN — the plugin never writes this file for you.** Copy it into your data
> dir, one file per review language, and let it grow:
>
> ```bash
> mkdir -p "${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/language-rules"
> cp "${CLAUDE_PLUGIN_ROOT}/config/language-rules.template.md" \
>    "${LINKEDIN_STUDIO_DATA:-$HOME/.claude/linkedin-studio}/language-rules/en.md"
> ```
>
> Name the file after the edition's `language` value (`en.md`, `no.md`, …).
> While it is absent, the shipped baseline applies alone and nothing warns.

This file is **yours**. It holds the language corrections you have made that you
do not want to make again — the judgment half of the fold-in loop
(`references/fold-in-loop.md`). Two things read it:

- **`agents/language-reviewer.md`** (Step 6.5, cold review) — grades against
  these rules in addition to its five standard checks, so a correction you
  confirmed once is caught every edition after.
- **`/linkedin:newsletter` Step 4** (consistency + quality) — reads it while the
  draft is still being cleaned, so the defect is *prevented*, not only caught.

**`/linkedin:newsletter` Step 11** (retro) appends to it: when you promote a
judgment-class fold-in, the rule lands here with the edition that surfaced it.
Mechanical corrections do **not** come here — those become deterministic
`scripts/contract-gate` rules instead.

## Relationship to the shipped baseline

`references/longform-quality-rules.md` rule 3 (the AI-slop ban-list) is the
**baseline** and is never edited by the loop. This file **extends** it. Where the
two disagree, the stricter one wins; if you actually want to overturn a baseline
rule, say so explicitly under *Deliberate exceptions* below — an unexplained
contradiction reads as drift to the next reviewer.

## Format

One rule per bullet. Keep each rule **checkable** — a reviewer must be able to
tell from the text alone whether it was broken. Add the date and the edition that
surfaced it, so a rule that turns out to be wrong can be traced back and dropped.

```markdown
- **<what to avoid>** → <what to do instead>. _(<YYYY-MM-DD>, edition <NN>)_
```

Good: *«"leverage" as a verb → use the plain verb ("use", "build on").»*
Bad: *«write better sentences»* — nothing can check that.

---

## Rules

<!-- Step 11 appends promoted judgment-class fold-ins below this line. -->

_(empty — no rules accumulated yet)_

## Deliberate exceptions

Baseline rules you have consciously decided not to follow, **with the reason**.
Keep this short; a long list here means the baseline is wrong for your practice
and should be discussed, not quietly bypassed.

_(none)_
