rigor: Skill for Claude Code

rigor-docs-review — user-facing docs review battery

Reviews Rigor's user-facing documentation — docs/manual/ (operational reference) and docs/handbook/ (type-model walkthrough) — from multiple expert lenses run as independent-context subagents, records each to a note, and applies only the necessary, axis-preserving fixes. This skill is the methodology freeze; the personas are re-pointed at whatever chapter/scope each run targets.

The full design rationale (what ports from the chibirigor book battery, what drops, what inverts, why L0 is new) is docs/notes/20260610-user-docs-review-battery-design.md. Read it once; do not restate it here.

The one load-bearing constraint: this is software documentation, not a book. Prose depth is not a virtue. A book battery rewards narrative richness and woven-in background; here the reference job is correctness and necessary clarity, and background thinness is not a defect. This is why L3 is inverted (a bloat detector, not a depth booster) and why no lens is allowed to recommend padding.

When to use / not

• Use: a manual/handbook chapter reached a stopping point; pre-release doc pass; "does the doc still match the implementation?"; the user says "review the docs / 査読して / 校閲して".
• Do NOT use: a single-line fix or an obvious typo — the lens-launch overhead is not worth it.

The five layers

Run order is L0 → L1 → L2 → L3 → L4 (機械 → 真 → 伝 → 簡 → 整). A full cycle runs at milestones; day-to-day, run only the layer in question (see "Which layer to run"). Parallel within a layer, sequential across — a later layer reads the text the earlier layer's fixes already corrected, because polishing an incorrect claim, or tidying prose a reader can't follow, is wasted work.