@@ -14,6 +14,7 @@ Check terminology against project glossary and zh_CN/zh_TW mappings.
 2. **Secondary:** `focused_terminology_dictionary.csv` - 118 key terms
 3. **Tertiary:** `.scripts/google_translate/utils.py` - zh_CN to zh_TW mappings
 4. **Usage evidence (not authority):** `.scripts/translation_memory.sh query "<term>"` - how existing translated .po entries render the term (skip if the command fails)
+5. **Reviewer-enforced terms:** the "Terminology enforced by reviewers" table in `../translate-po/references/review-corrections.md` - pairs reviewers repeatedly corrected (e.g. 傳回→回傳, 您→你, 協議→協定, 運行→執行), some context-dependent (串列 vs 清單, 檔案 vs 文件)
 
 ## Check Process
 
 
@@ -0,0 +1,94 @@
+---
+name: review-rendered-html
+description: Builds translated PO files into HTML and reviews the rendered page for reading flow and formatting, by reading the extracted page text and checking Playwright screenshots. Use after translating or editing a PO file, before opening a PR.
+argument-hint: <po-file> [<po-file> ...]
+---
+
+# review-rendered-html
+
+PO-level checks (`msgfmt`, `make lint`, terminology) cannot show how a
+translation reads on the published page. reST roles disappear, links and
+literals change spacing, and Sphinx adds its own labels. Review the rendered
+HTML of every page you changed before opening a PR.
+
+## Prerequisites
+
+- CPython clone at `../cpython` on the branch matching `VERSION` in the
+  Makefile, and the docs venv (`make prepare_deps` sets up both)
+- Playwright MCP tools (`browser_navigate`, `browser_take_screenshot`) for
+  screenshots; without them, read the text dump only and say so in the report
+
+## Step 1: Build and dump the rendered text
+
+```bash
+python3 .scripts/render_review.py library/dataclasses.po [faq/library.po ...]
+```
+
+- Builds only the given pages (same Sphinx options as `make build`) and writes
+  the page prose, without code blocks, to `.render-review/<page>.txt`
+- Prints heuristic findings with the line in the text dump; `--no-build`
+  re-checks without rebuilding
+- "build reported problems" about `redirects to builtins/...` comes from a
+  reused build directory and does not affect the page
+
+## Step 2: Read the text dump as a reader
+
+Read `.render-review/<page>.txt` end to end, focusing on paragraphs from the
+entries you changed. For each one check:
+
+- **Flow:** the sentence reads as natural Taiwanese technical writing; no
+  translationese (被…所…, 將會是, 除…之外的其他事項), no dangling clauses
+  after a role's text disappears
+- **Spacing:** one space between CJK and Latin/digits/literals; no space
+  next to full-width punctuation; no stray space inside Chinese text
+- **Punctuation:** full-width `，。：；（）「」` around Chinese; the colon before
+  a code block stays `：`
+- **Completeness:** compare with the English page when meaning is unclear
+
+Confirm or dismiss every heuristic finding by reading its context. Findings in
+entries you did not touch are follow-ups, not part of the current change.
+
+Paragraphs still in English are usually not your bug. Either the entry is
+untranslated, or the PO msgid is older than the CPython clone, because the
+source changed after the last sync. Mention them in the report and don't fix
+them in the PO by hand.
+
+## Step 3: Screenshot and inspect the layout
+
+Serve the build and open the sections you changed:
+
+```bash
+python3 -m http.server 8765 --bind 127.0.0.1 --directory ../cpython/Doc/build/html
+```
+
+Then use the Playwright MCP tools:
+
+1. `browser_resize` to 1280x1600
+2. `browser_navigate` to `http://127.0.0.1:8765/<page>.html#<anchor>`
+3. `browser_take_screenshot` with `filename: ".playwright-mcp/<name>.png"`
+   (the MCP only writes inside the repo; `.playwright-mcp/` is gitignored)
+4. Read the PNG and check: links and `:term:` text sit flush with the Chinese
+   around them, inline code has normal spacing, parameter lists, notes and
+   admonitions keep their structure, and headings and the sidebar TOC show
+   the translated titles
+
+Stop the server when done.
+
+## Common rendered-only problems and fixes
+
+| Rendered | Cause in msgstr | Fix |
+|---|---|---|
+| `field可以` | ``` ``field``\ 可以 ``` | ``` ``field`` 可以 ``` (keep the space after a literal before CJK) |
+| `全域直譯器鎖(GIL) 來` | `` :term:`…`\ (GIL) 來 `` | `` :term:`…`\ （GIL）來 `` (full-width parens, no extra space) |
+| `磁碟區上的 替代資料串流` | `` 的 `替代資料串流 <url>`_ `` | `` 的\ `替代資料串流 <url>`_ `` |
+| `:meth:` or backticks visible | role typo such as `:meth: ` with a space | restore the exact role syntax |
+| `` `\ `` visible | escaped backslash doubled in the PO | one `\\ ` in the PO file (`\ ` in the value) |
+
+A reST role or link must be followed by whitespace or ASCII/closing
+punctuation, so a full-width opening bracket after a role still needs `\ `.
+
+## Report
+
+List per page: findings fixed, findings dismissed (with reason), follow-ups
+in untouched entries, English paragraphs and their likely cause, and the
+screenshots you checked.
@@ -76,6 +76,41 @@ See `references/rst-cheatsheet.md` for complete rules.
 4. If uncertain, add `#, fuzzy` flag
 5. Never use zh_CN terms from `references/forbidden-terms.md`
 
+### Step 5: Check Against Past Review Corrections
+
+Reviewers of this repo keep asking for the same fixes. Before finishing,
+re-read every changed msgstr against `references/review-corrections.md`
+(mined from ~1,500 review comments). The most frequent ones:
+
+1. **Phrasing and meaning:** no English word order, piles of 的 or needless
+   被; the meaning must match the source exactly (most common correction)
+2. **Terms reviewers enforce:** argument→引數 / parameter→參數, 回傳 (not
+   傳回/返回), 你 (not 您), 引發 (raise), 設定例外 (C API "set an
+   exception"), 透過, 協定, 命令列, 用戶端, 執行 (not 運行), 產生 (not 生成),
+   串列 only for a Python list (otherwise 清單); see the table in the reference
+3. **Spacing:** no space next to full-width punctuation, after 。, or
+   between CJK characters
+4. **`\\ `:** use it between CJK and markup, but not next to `，。、：；）「」`
+   (a full-width `（` right after markup still needs it)
+5. **Punctuation:** `、` for enumerations; keep `...` as in the source; keep
+   ASCII quotes around literal values
+6. **Markup:** re-add ``literal`` markup Poedit drops; balanced backticks
+7. **Completeness:** no omissions (qualifiers, parentheticals, second
+   occurrences) and no additions the source does not state (超譯)
+8. **Keep English:** socket, token, runtime, yield, library names, and words
+   that are really parameter names; translate comments in code samples
+9. **Consistency:** one rendering per term within a page; search existing
+   translations (translation memory) before coining a term
+10. **PO mechanics:** never just strip `#, fuzzy` without updating the
+    translation; index-only entries as `English（譯文）`
+
+### Step 6: Review the Rendered Page
+
+After the PO file is saved, build and read the rendered page with the
+`review-rendered-html` skill (`python3 .scripts/render_review.py <file>.po`,
+then Playwright screenshots of the changed sections). Spacing around
+literals, roles and links can only be judged on the rendered page.
+
 ## Output Format
 
 ```
@@ -95,6 +130,8 @@ Before outputting, verify:
 - [ ] Terminology matches glossary
 - [ ] No forbidden zh_CN terms
 - [ ] Consistent with translation memory hits, unless they conflict with the glossary
+- [ ] Checked against past review corrections (`references/review-corrections.md`)
+- [ ] Rendered page reads naturally and its layout is correct (`review-rendered-html`)
 
 ## Examples
 
@@ -154,4 +191,6 @@ msgstr "可能需要審核的翻譯"
 - `references/terminology.md` - Key term translations (186 terms)
 - `references/forbidden-terms.md` - zh_CN to zh_TW mappings
 - `references/rst-cheatsheet.md` - reST syntax rules
+- `references/review-corrections.md` - What reviewers most often correct, with examples and enforced terms
 - `.scripts/translation_memory.sh` - Translation memory lookup over this repo's .po files
+- `.scripts/render_review.py` - Build pages and check the rendered text (see `review-rendered-html`)