@fectivnfy112358/minimax-code-web 0.1.0-preview.0 → 0.1.0-preview.3

package/server/assets/skills/docx/docs/task-read-rendered.md

@@ -0,0 +1,78 @@
+# Task: READ_RENDERED
+
+Use this task family when the user wants page truth.
+
+## Required inputs
+
+- one source `.docx`
+- a page-level question: blank pages, cover / TOC layout, overflow, clipped content, visual mismatch,
+  pagination, page numbers, header/footer appearance, or “why does this Word look wrong?”
+
+## Evidence profile
+
+Default evidence: **rendered truth + structure truth**.
+
+Rendered evidence judges the problem. Structure evidence helps explain the cause.
+
+## Execution path
+
+### Preferred route: DOCX -> PDF / page artifacts inside this skill
+```bash
+python3 <skill_dir>/scripts/docx_to_pdf.py --input <input.docx> --output /tmp/docx-render.pdf
+```
+
+Then inspect the generated PDF or derived page artifacts from inside `docx`. Rendered truth
+must stay in this skill so DOCX page diagnosis and repair are all-in-one.
+
+### Page PNG route
+```bash
+python3 <skill_dir>/scripts/render_docx_pages.py <input.docx> --output-dir /tmp/docx-pages
+```
+
+This route is valid only when full-fidelity rendering requirements are met. If the required render toolchain is missing, block and report the missing dependency. Do not degrade to a lower-fidelity preview path.
+
+### Delivery route: rendered artifact -> page issue summary -> structure alignment
+After page inspection, write down the observed rendered symptoms and produce the rendered report from
+inside `docx`:
+
+```bash
+python3 <skill_dir>/scripts/read_docx_structure.py <input.docx> --json > /tmp/docx-structure.json
+python3 <skill_dir>/scripts/rendered_report.py \
+  --pdf /tmp/docx-render.pdf \
+  --pages-dir /tmp/docx-pages \
+  --structure-json /tmp/docx-structure.json \
+  --issue-file /tmp/rendered-issues.json \
+  --format markdown > /tmp/rendered-report.md
+```
+
+The exact issue-file format and output contract are defined in `rendered-delivery.md`.
+
+## Output contract
+
+Return:
+- `artifactSummary`: PDF / PNG artifact inventory
+- `pageIssueSummary`: each issue must name pages, severity, and visual symptom
+- `structureCauseAlignment`: for each issue, align the symptom to structure signals
+- `likelyStructuralCauses`: explain why the structure signals matter
+- `recommendedChecks`: tell the next operator what to verify or rerender
+
+Typical issue classes that must use this format:
+- `layout_overflow_or_clipping`
+- `template_fidelity`
+- `toc_layout_or_update`
+- `header_footer_mismatch`
+- `page_number_wrong`
+- `extra_blank_page`
+
+Delivering only the PDF or page PNG directory is incomplete. Artifact generation is evidence collection,
+not the rendered-truth answer.
+
+## Acceptance profile
+
+`light`
+
+## Common mistake
+
+Do not stay in pure XML once the task is about page appearance. XML is evidence, not the judge.
+Do not treat a generated PDF or PNG folder as the final deliverable. The final deliverable is the
+page issue summary plus structure alignment.

package/server/assets/skills/docx/docs/task-read-structure.md

@@ -0,0 +1,93 @@
+# Task: READ_STRUCTURE
+
+Use this task family when the user wants Word/OpenXML truth rather than plain text.
+
+## Required inputs
+
+- one source `.docx`
+- a structure question: styles, sections, numbering, TOC, headers/footers, revisions, comments,
+  bookmarks, fields, template internals, or structural differences that affect later edits
+
+## Evidence profile
+
+Default evidence: **structure truth**.
+
+Use content truth only as a locator aid. Use rendered truth only if the user also asks what the
+structure difference means visually.
+
+## Execution path
+
+### Primary analyzer (structure truth oracle)
+
+`scripts/read_docx_structure.py` is the **structure-truth implementation** for this skill. It is
+not a summary that needs another tool to be useful; it parses every OOXML part directly with the
+Python stdlib and produces an independent, self-contained structure report. Run it as the first
+step of every READ_STRUCTURE task:
+
+```bash
+python3 <skill_dir>/scripts/read_docx_structure.py <input.docx> --json
+```
+
+The report owns these structure axes — none of them are delegated to dotnet:
+
+| Section | What it gives you |
+|---------|-------------------|
+| `packaging` | `[Content_Types]`, package rels, document rels, full part inventory with sizes |
+| `sections` | per-section graph: type, page size (mm), margins (mm), columns, `titlePg`, `lineNumbering`, `pageBorders`, header/footer rId references |
+| `headerFooterParts` | every header/footer part resolved through rels with paragraph / field / drawing / hyperlink counts and per-part field kinds |
+| `styles.byId` + `defaults` | full styles dictionary with `basedOn`, `linked`, `next`, `outlineLvl`, `numId`, `isCustom`, `isDefault` |
+| `styles.usedParagraphStyles` / `usedRunStyles` | usage histograms straight from document body |
+| `styles.missingReferenced` / `definedButUnused` / `headingsWithoutOutlineLvl` | template-diagnosis cross-reference audit |
+| `numbering.abstractNums` / `nums` | the `numId → abstractNumId → levels` chain with `multiLevelType`, per-level `numFmt`, `lvlText`, `start`, `pStyle` |
+| `numbering.usage` | paragraph counts per `numId` and per `(numId, ilvl)` |
+| `fields.simple` / `complex` | full instruction text, classified `kind` (TOC, PAGE, REF, STYLEREF, …), `dirty` / `locked` flags, captured field result |
+| `fields.kindCountsAllParts` | rolled-up field-kind counts including header/footer parts |
+| `bookmarks` | start/end pairing with paragraph spans, orphan starts and ends, reserved-name flag |
+| `hyperlinks` | anchor + rId resolved to URL via document rels, `external` flag |
+| `comments` | comment defs, `commentsExtended` parent links, in-body range/reference counts, orphans both ways |
+| `revisions` | per-kind counts (`ins`, `del`, `moveFrom`, `moveTo`, `cell*`, `rPrChange`, `pPrChange`, `sectPrChange`, …), authors, date range |
+| `contamination` | direct-formatting heatmap: `pPrDirect`, `rPrDirectRuns`, dirty-paragraph ratio |
+| `settingsFlags` | `trackChanges`, `evenAndOddHeaders`, `mirrorMargins`, `updateFields`, footnote/endnote presence |
+| `diagnostics` | categorized findings (`severity` × `code` × `message`) for missing styles, broken section / hyperlink rels, undefined comment ids, orphan bookmarks, missing numIds, heading styles without outline level |
+
+To request a subset of axes (cheaper context), pass `--section`:
+
+```bash
+python3 <skill_dir>/scripts/read_docx_structure.py <input.docx> --json --section sections,numbering,diagnostics
+```
+
+The `diagnostics` array is intentionally the place to look first when the user asks
+"what's wrong with this template?" — every finding includes a stable `code` and the
+ids/paths needed to act on it.
+
+### Independent confirmation (optional)
+
+`dotnet run --project <skill_dir>/scripts/dotnet/MiniMaxAIDocx.Cli -- analyze --input <input.docx> --json`
+remains available as an **independent confirmation** shot — different runtime, different parser,
+different JSON shape — and is useful when you need to sanity-check the Python analyzer or compare
+counts across two parsers. It is not the structure-truth source. The dotnet `analyze` command
+returns a deliberately shallower view (sections, headings, tables, image count, custom style ids,
+XML file sizes) and does **not** cover numbering chains, field topology, bookmark pairing,
+hyperlink rel resolution, contamination heatmap, or template diagnostics. If the two disagree on
+something the Python analyzer covers, treat the Python output as authoritative and investigate
+the divergence.
+
+## Output contract
+
+Return:
+
+- a direct answer to the structure question
+- the key objects involved: styles, section breaks, numbering, refs, fields, revisions, etc.
+- any hazards from `diagnostics` that matter for later write work
+- if applicable, the `code` of any diagnostic that downstream tasks (REPAIR_LAYOUT,
+  APPLY_TEMPLATE) should pre-flight on
+
+## Acceptance profile
+
+`light`
+
+## Common mistake
+
+Do not claim a visual fix or visual defect from structure evidence alone when the user asked about
+pages. That belongs in `READ_RENDERED` or `REPAIR_LAYOUT`. And do not run `dotnet analyze` *before*
+the Python analyzer — the dotnet command is a corroboration shot, not the entry point.

package/server/assets/skills/docx/docs/task-repair-layout.md

@@ -0,0 +1,70 @@
+# Task: REPAIR_LAYOUT
+
+Use this task family when the document already exists, the user reports that it looks wrong, and the
+job is to fix the visual outcome rather than merely inspect it.
+
+## Required inputs
+
+- one source `.docx`
+- a layout complaint
+- optional target screenshot or template reference
+
+Normalize the complaint into one or more issue classes:
+- `extra_blank_page`
+- `header_footer_mismatch`
+- `section_restart_wrong`
+- `toc_not_generated`
+- `heading_number_wrong`
+- `table_row_split`
+- `image_float_overlap`
+- `title_orphan`
+- `style_contamination`
+- `inconsistent_page_numbers`
+
+## Evidence profile
+
+Fixed sequence:
+1. rendered truth first
+2. structure truth second
+3. rendered truth again after repair
+
+## Execution model
+
+1. classify the complaint
+2. inspect the rendered defect
+3. map to likely structural causes
+4. choose backend (`D`, `S`, or low-risk `X` only if truly local)
+5. repair
+6. rerender and verify
+
+## Delivery contract
+
+`REPAIR_LAYOUT` must produce two rendered reports using the same issue classes and page references:
+
+1. **before repair** — reproduce the defect and pin the failing pages
+2. **after repair** — rerender and prove the same complaint no longer reproduces
+
+Use `rendered-delivery.md` and `scripts/rendered_report.py` for both passes. The report must include:
+
+- page-level symptom summary
+- structure-cause alignment
+- likely structural causes
+- recommended checks
+
+Typical repair classes:
+- `extra_blank_page`
+- `header_footer_mismatch`
+- `page_number_wrong`
+- `toc_layout_or_update`
+- `template_fidelity`
+- `layout_overflow_or_clipping`
+
+## Hard no
+
+- Do not start from XML alone when the problem statement is visual.
+- Do not claim success until rerendered pages confirm the fix.
+- Do not claim success from artifact generation alone. A rerendered report is required.
+
+## Acceptance profile
+
+`strict`

package/server/assets/skills/docx/docs/template-dsl.md

@@ -0,0 +1,32 @@
+# Template DSL
+
+This skill does not rely on ad-hoc placeholder folklore. It uses explicit anchors and optional template
+manifests.
+
+## Anchor forms
+
+Recommended anchors:
+- `@@FIELD:name@@`
+- `@@FIELD:date@@`
+- `@@BLOCK:intro@@`
+- `@@TABLE:items@@`
+- `@@IMAGE:logo@@`
+- `@@RICH:summary@@`
+
+## Rules
+
+- anchors should live in a single `w:t` node whenever possible
+- anchors should not cross runs or paragraphs
+- table repetition should use structural row cloning, not Jinja-style inline loop syntax
+- if atomicity fails, either normalize runs safely or reject the template as unsafe for automated fill
+
+## Template manifest
+
+A template manifest is a JSON description of:
+- template mode
+- required sections
+- expected style IDs
+- anchor rules
+- validation profile
+
+See `../references/sample-template-manifests.json` for example structure.

package/server/assets/skills/docx/docs/track-changes.md

@@ -0,0 +1,15 @@
+# Track changes
+
+Track changes are not ordinary text edits. Preserve semantics.
+
+## Runtime rules
+
+- `w:del` uses `w:delText`, not `w:t`
+- `w:ins` uses `w:t`, not `w:delText`
+- if the task truly requires revision-graph manipulation, prefer backend `D` or `S`
+- do not use pandoc to preserve tracked changes in a Word-authored DOCX
+
+## Practical rule
+
+If the user only wants readable content and does not care about tracked-change semantics, read-side
+content extraction may ignore them. But write-side preservation must not.

package/server/assets/skills/docx/docs/xml-patch-dsl.md

@@ -0,0 +1,33 @@
+# XML patch DSL
+
+Patch plans exist to convert a natural-language edit request into a deterministic operation list.
+They are not a full programming language.
+
+## Supported operations
+
+- `replace_text`
+- `fill_anchor`
+- `insert_paragraph_after`
+- `insert_paragraph_before`
+- `remove_paragraph`
+- `clone_table_row`
+- `fill_table_row`
+- `strip_direct_formatting`
+- `set_paragraph_style`
+- `set_run_style`
+- `merge_runs`
+- `fix_element_order`
+
+## Locator types
+
+- `anchor`
+- `heading_text`
+- `paragraph_text_exact`
+- `paragraph_index`
+- `table_anchor`
+- `xpath` (advanced, not default)
+
+## Safety boundary
+
+If the operation implies section topology changes, numbering rebuilds, header/footer graph edits, or
+relationship rewrites, the patch plan should escalate from `X` to `D` or `S`.

package/server/assets/skills/docx/references/cjk_typography.md

@@ -0,0 +1,357 @@
+# CJK Typography & Mixed-Script Guide
+
+Rules for Chinese, Japanese, and Korean text in DOCX documents.
+
+## Table of Contents
+
+1. [Font Selection](#font-selection)
+2. [Font Size Names (CJK)](#font-size-names)
+3. [RunFonts Mapping](#runfonts-mapping)
+4. [Punctuation & Line Breaking](#punctuation--line-breaking)
+5. [Paragraph Indentation](#paragraph-indentation)
+6. [Line Spacing for CJK](#line-spacing)
+7. [Chinese Government Standard (GB/T 9704)](#gbt-9704)
+8. [Mixed CJK + Latin Best Practices](#mixed-script)
+9. [OpenXML Quick Reference](#openxml-quick-reference)
+
+---
+
+## Font Selection
+
+### Recommended CJK Fonts
+
+| Language | Serif (正文) | Sans (标题) | Notes |
+|----------|-------------|-------------|-------|
+| **Simplified Chinese** | 宋体 (SimSun) | 微软雅黑 (Microsoft YaHei) | YaHei for screen, SimSun for print |
+| **Simplified Chinese** | 仿宋 (FangSong) | 黑体 (SimHei) | Government documents |
+| **Traditional Chinese** | 新細明體 (PMingLiU) | 微軟正黑體 (Microsoft JhengHei) | Taiwan standard |
+| **Japanese** | MS 明朝 (MS Mincho) | MS ゴシック (MS Gothic) | Classic pairing |
+| **Japanese** | 游明朝 (Yu Mincho) | 游ゴシック (Yu Gothic) | Modern, Windows 10+ |
+| **Korean** | 바탕 (Batang) | 맑은 고딕 (Malgun Gothic) | Standard pairing |
+
+### Government Document Fonts (公文)
+
+| Element | Font | Size |
+|---------|------|------|
+| 标题 (title) | 小标宋 (FZXiaoBiaoSong-B05S) | 二号 (22pt) |
+| 一级标题 | 黑体 (SimHei) | 三号 (16pt) |
+| 二级标题 | 楷体_GB2312 (KaiTi_GB2312) | 三号 (16pt) |
+| 三级标题 | 仿宋_GB2312 加粗 | 三号 (16pt) |
+| 正文 (body) | 仿宋_GB2312 (FangSong_GB2312) | 三号 (16pt) |
+| 附注/页码 | 宋体 (SimSun) | 四号 (14pt) |
+
+---
+
+## Font Size Names
+
+CJK uses named sizes. Map to points and `w:sz` half-point values:
+
+| 字号 | Points | `w:sz` | Common Use |
+|------|--------|--------|------------|
+| 初号 | 42pt | 84 | Display title |
+| 小初 | 36pt | 72 | Large title |
+| 一号 | 26pt | 52 | Chapter heading |
+| 小一 | 24pt | 48 | Major heading |
+| 二号 | 22pt | 44 | Document title (公文) |
+| 小二 | 18pt | 36 | Western H1 equivalent |
+| 三号 | 16pt | 32 | CJK heading / 公文 body |
+| 小三 | 15pt | 30 | Sub-heading |
+| 四号 | 14pt | 28 | CJK subheading |
+| 小四 | 12pt | 24 | Standard body (CJK) |
+| 五号 | 10.5pt | 21 | Compact CJK body |
+| 小五 | 9pt | 18 | Footnotes |
+| 六号 | 7.5pt | 15 | Fine print |
+
+---
+
+## RunFonts Mapping
+
+OpenXML uses four font slots to handle multilingual text:
+
+```xml
+<w:rFonts
+  w:ascii="Calibri"        <!-- Latin characters (U+0000–U+007F) -->
+  w:hAnsi="Calibri"        <!-- Latin extended, Greek, Cyrillic -->
+  w:eastAsia="SimSun"      <!-- CJK Unified Ideographs, Kana, Hangul -->
+  w:cs="Arial"             <!-- Arabic, Hebrew, Thai, Devanagari -->
+/>
+```
+
+**Word's character classification logic:**
+
+1. Character is in CJK range → uses `w:eastAsia` font
+2. Character is in complex script range → uses `w:cs` font
+3. Character is basic Latin (ASCII) → uses `w:ascii` font
+4. Everything else → uses `w:hAnsi` font
+
+**Key**: `w:eastAsia` is the **only** way to set CJK fonts. Setting just `w:ascii` will NOT affect CJK characters. Mixed text within a single run auto-switches fonts at the character level — no need for separate runs.
+
+### Document Defaults
+
+```xml
+<w:docDefaults>
+  <w:rPrDefault>
+    <w:rPr>
+      <w:rFonts w:ascii="Calibri" w:hAnsi="Calibri" w:eastAsia="SimSun" w:cs="Arial" />
+      <w:sz w:val="22" />
+      <w:szCs w:val="22" />
+      <w:lang w:val="en-US" w:eastAsia="zh-CN" />
+    </w:rPr>
+  </w:rPrDefault>
+</w:docDefaults>
+```
+
+`w:lang w:eastAsia` helps Word resolve ambiguous characters (e.g., punctuation shared between CJK and Latin).
+
+---
+
+## Punctuation & Line Breaking
+
+### Full-Width vs Half-Width
+
+CJK text uses full-width punctuation:
+
+| Type | CJK | Latin |
+|------|-----|-------|
+| Period | 。(U+3002) | . |
+| Comma | ，(U+FF0C) 、(U+3001) | , |
+| Colon | ：(U+FF1A) | : |
+| Semicolon | ；(U+FF1B) | ; |
+| Quotes | 「」『』 or ""'' | "" '' |
+| Parentheses | （）(U+FF08/09) | () |
+
+In mixed text, use the punctuation style of the **surrounding language context**.
+
+### OpenXML Controls
+
+```xml
+<w:pPr>
+  <w:adjustRightInd w:val="true" />   <!-- Adjust right indent for CJK punctuation -->
+  <w:snapToGrid w:val="true" />        <!-- Align to document grid -->
+  <w:kinsoku w:val="true" />           <!-- Enable CJK line breaking rules -->
+  <w:overflowPunct w:val="true" />     <!-- Allow punctuation to overflow margins -->
+</w:pPr>
+```
+
+### Kinsoku Rules (禁則処理)
+
+Prevents certain characters from appearing at the start or end of a line:
+- **Cannot start a line**: `）」』】〉》。、，！？；：` and closing brackets
+- **Cannot end a line**: `（「『【〈《` and opening brackets
+
+Word applies these automatically when `w:kinsoku` is enabled.
+
+### Line Breaking
+
+- CJK characters can break between **any two characters** (no word boundaries needed)
+- Latin words within CJK text still follow word-boundary breaking
+- `w:wordWrap w:val="false"` enables CJK-style breaking (break anywhere)
+
+---
+
+## Paragraph Indentation
+
+### Chinese Standard: 2-Character Indent
+
+Chinese body text conventionally uses a 2-character first-line indent:
+
+```xml
+<w:ind w:firstLineChars="200" />  <!-- 200 = 2 characters × 100 -->
+```
+
+Preferred over `w:firstLine` with fixed DXA because `firstLineChars` scales with font size.
+
+| Indent | Value |
+|--------|-------|
+| 1 character | `w:firstLineChars="100"` |
+| 2 characters | `w:firstLineChars="200"` |
+| 3 characters | `w:firstLineChars="300"` |
+
+---
+
+## Line Spacing
+
+- CJK characters are taller than Latin characters at the same point size
+- Default `1.0` line spacing may feel cramped with CJK text
+- Recommended: `1.15–1.5` for mixed CJK+Latin, `1.0` with fixed 28pt for 公文
+
+### Auto Spacing
+
+```xml
+<w:pPr>
+  <w:autoSpaceDE w:val="true"/>  <!-- auto space between CJK and Latin -->
+  <w:autoSpaceDN w:val="true"/>  <!-- auto space between CJK and numbers -->
+</w:pPr>
+```
+
+Adds ~¼ em spacing between CJK and non-CJK characters automatically. **Recommended: always enable.**
+
+---
+
+## GB/T 9704
+
+Chinese government document standard (党政机关公文格式). These are **strict requirements**, not suggestions.
+
+### Page Setup
+
+| Parameter | Value | OpenXML |
+|-----------|-------|---------|
+| Page size | A4 (210×297mm) | Width=11906, Height=16838 |
+| Top margin | 37mm | 2098 DXA |
+| Bottom margin | 35mm | 1984 DXA |
+| Left margin | 28mm | 1588 DXA |
+| Right margin | 26mm | 1474 DXA |
+| Characters/line | 28 | |
+| Lines/page | 22 | |
+| Line spacing | Fixed 28pt | `line="560"` lineRule="exact" |
+
+### Document Structure
+
+```
+┌─────────────────────────────────┐
+│     发文机关标志 (红头)           │  ← 小标宋 or 红色大字
+│     ══════════════════ (红线)    │  ← Red #FF0000, 2pt
+├─────────────────────────────────┤
+│  发文字号: X机发〔2025〕X号      │  ← 仿宋 三号, centered
+│                                 │
+│  标题 (Title)                   │  ← 小标宋 二号, centered
+│                                 │     可分多行，回行居中
+│  主送机关:                      │  ← 仿宋 三号
+│                                 │
+│  正文 (Body)...                 │  ← 仿宋_GB2312 三号
+│  一、一级标题                    │  ← 黑体 三号
+│  （一）二级标题                  │  ← 楷体 三号
+│  1. 三级标题                    │  ← 仿宋 三号 加粗
+│  (1) 四级标题                   │  ← 仿宋 三号
+│                                 │
+│  附件: 1. xxx                   │  ← 仿宋 三号
+│                                 │
+│  发文机关署名                    │  ← 仿宋 三号
+│  成文日期                       │  ← 仿宋 三号, 小写中文数字
+├─────────────────────────────────┤
+│  ══════════════════ (版记线)     │
+│  抄送: xxx                      │  ← 仿宋 四号
+│  印发机关及日期                   │  ← 仿宋 四号
+└─────────────────────────────────┘
+```
+
+### Numbering System
+
+```
+一、        ← 黑体 (SimHei), no indentation
+（一）      ← 楷体 (KaiTi), indented 2 chars
+1.          ← 仿宋加粗 (FangSong Bold), indented 2 chars
+(1)         ← 仿宋 (FangSong), indented 2 chars
+```
+
+### Colors
+
+| Element | Color | Requirement |
+|---------|-------|-------------|
+| All body text | Black #000000 | Mandatory |
+| 红头 (agency name) | Red #FF0000 | Mandatory |
+| 红线 (separator) | Red #FF0000 | Mandatory |
+| 公章 (official seal) | Red | Mandatory |
+
+### Page Numbers
+
+- Position: bottom center
+- Format: `-X-` (dash-number-dash)
+- Font: 宋体 四号 (SimSun 14pt, `sz="28"`)
+- No page number on cover page if present
+
+---
+
+## Mixed Script
+
+### Font Size Harmony
+
+CJK characters appear larger than Latin characters at the same point size. Compensation:
+
+- If body is Calibri 11pt, pair with CJK at 11pt (same size — CJK looks slightly larger but acceptable)
+- If precise visual match needed, CJK can be set 0.5–1pt smaller
+- In practice, same point size is standard — don't over-optimize
+
+### Bold and Italic
+
+- **Chinese/Japanese have no true italic.** Word synthesizes a slant which looks poor
+- Use **bold** for emphasis in CJK text
+- Use 着重号 (emphasis dots) for traditional emphasis: `<w:em w:val="dot"/>` on RunProperties
+
+---
+
+## OpenXML Quick Reference
+
+### Set EastAsia Font (C#)
+
+```csharp
+new Run(
+    new RunProperties(
+        new RunFonts { EastAsia = "SimSun", Ascii = "Calibri", HighAnsi = "Calibri" },
+        new FontSize { Val = "32" }  // 三号 = 16pt = sz 32
+    ),
+    new Text("这是正文内容")
+);
+```
+
+### Document Defaults (C#)
+
+```csharp
+new DocDefaults(new RunPropertiesDefault(new RunPropertiesBaseStyle(
+    new RunFonts {
+        Ascii = "Calibri", HighAnsi = "Calibri",
+        EastAsia = "Microsoft YaHei"
+    },
+    new Languages { Val = "en-US", EastAsia = "zh-CN" }
+)));
+```
+
+### 公文 Style Definitions (C#)
+
+```csharp
+// Title style — 小标宋 二号 centered
+new Style(
+    new StyleName { Val = "GongWen Title" },
+    new BasedOn { Val = "Normal" },
+    new StyleRunProperties(
+        new RunFonts { EastAsia = "FZXiaoBiaoSong-B05S" },
+        new FontSize { Val = "44" },  // 二号 = 22pt
+        new Bold()
+    ),
+    new StyleParagraphProperties(
+        new Justification { Val = JustificationValues.Center },
+        new SpacingBetweenLines { Line = "560", LineRule = LineSpacingRuleValues.Exact }
+    )
+) { Type = StyleValues.Paragraph, StyleId = "GongWenTitle" };
+
+// Body style — 仿宋_GB2312 三号
+new Style(
+    new StyleName { Val = "GongWen Body" },
+    new StyleRunProperties(
+        new RunFonts { EastAsia = "FangSong_GB2312", Ascii = "FangSong_GB2312" },
+        new FontSize { Val = "32" }  // 三号 = 16pt
+    ),
+    new StyleParagraphProperties(
+        new SpacingBetweenLines { Line = "560", LineRule = LineSpacingRuleValues.Exact }
+    )
+) { Type = StyleValues.Paragraph, StyleId = "GongWenBody" };
+```
+
+### Emphasis Dots (着重号)
+
+```csharp
+new RunProperties(new Emphasis { Val = EmphasisMarkValues.Dot });
+```
+
+### East Asian Text Layout
+
+```xml
+<!-- Snap to grid (align CJK chars to character grid) -->
+<w:snapToGrid w:val="true"/>
+
+<!-- Two-lines-in-one (双行合一) -->
+<w:eastAsianLayout w:id="1" w:combine="true"/>
+
+<!-- Vertical text in a cell -->
+<w:textDirection w:val="tbRl"/>
+```