docs: centralize post-writing verification in writing-guides index

Moves the canonical list of post-writing checks into writing-guides/index.md so it lives in one place, adds the two new format-check skills to that list, and shortens the Post-Writing Verification section in each writing skill (guides, api-reference, env-vars) to a one-line pointer. Also unwraps a pre-existing hard-wrapped paragraph in the api-reference skill's Cross-API Links section.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: RiskeyL

.claude/skills/dify-docs-api-reference/SKILL.md

@@ -145,8 +145,7 @@ Pattern: `{verb}{AppType}{Resource}`
 
 ### Cross-API Links
 
-When a description mentions another endpoint, add a markdown link.
-Pattern: `/api-reference/{category}/{endpoint-name}` (kebab-case from endpoint summary).
+When a description mentions another endpoint, add a markdown link. Pattern: `/api-reference/{category}/{endpoint-name}` (kebab-case from endpoint summary).
 
 ## Parameters
 
@@ -222,7 +221,4 @@ Exception: Tags without a create operation (e.g., Conversations). GET list comes
 
 ## Post-Writing Verification
 
-After completing the document:
-
-1. Invoke `dify-docs-terminology-check` to verify terminology consistency against the glossary and codebase.
-2. Invoke `dify-docs-reader-test` to verify it from the reader's perspective.
+After completing the document, run the post-writing checks listed in `writing-guides/index.md#post-writing-verification`.

.claude/skills/dify-docs-env-vars/SKILL.md

@@ -143,7 +143,4 @@ The automated translation pipeline does not cover `en/self-host/configuration/en
 
 ## Post-Writing Verification
 
-After completing the document:
-
-1. Invoke `dify-docs-terminology-check` to verify terminology consistency against the glossary and codebase.
-2. Invoke `dify-docs-reader-test` to verify it from the reader's perspective.
+After completing the document, run the post-writing checks listed in `writing-guides/index.md#post-writing-verification`.

.claude/skills/dify-docs-guides/SKILL.md

@@ -61,7 +61,4 @@ No overrides. Follow `writing-guides/style-guide.md` as written.
 
 ## Post-Writing Verification
 
-After completing the document:
-
-1. Invoke `dify-docs-terminology-check` to verify terminology consistency against the glossary and codebase.
-2. Invoke `dify-docs-reader-test` to verify it from the reader's perspective.
+After completing the document, run the post-writing checks listed in `writing-guides/index.md#post-writing-verification`.

writing-guides/index.md

@@ -15,6 +15,19 @@ When paths overlap, the most specific match takes precedence.
 
 If no skill matches your task (e.g., fixing a typo, updating navigation), follow the style guide and formatting guide directly.
 
+## Post-Writing Verification
+
+After completing a writing task, run these checks in order. Each is a self-contained skill.
+
+| Step | Skill | Purpose |
+|:-----|:------|:--------|
+| 1 | dify-docs-format-check-en | Enforce `formatting-guide.md` rules (frontmatter, headings, lists, code, images, spacing) on English content. |
+| 2 | dify-docs-format-check-cjk | Enforce general + Chinese/Japanese-specific formatting rules on `zh/` and `ja/` content. Run after translations are generated. |
+| 3 | dify-docs-terminology-check | Verify terminology consistency against the glossary and codebase UI labels. |
+| 4 | dify-docs-reader-test | Read each page from a first-time reader's perspective and flag comprehension gaps. |
+
+Steps 1 and 3 apply to any English doc change. Step 2 applies after the zh/ja translations are produced. Step 4 is always the last step because it depends on the others passing.
+
 ## Reference Files
 
 - **style-guide.md** — Voice, tone, writing patterns, callout usage