Official Document Formatting

Problem

Formal document formatting is easy to get wrong at the detail level: A4 page margins, text area, font family, font size, line spacing, page number placement, red header placement, hierarchical heading fonts, and preserving image-containing paragraphs. Manual Word adjustments are slow and can miss GB/T 9704-2012 and GB/T 33476.2-2016 requirements. Reformatting an existing .docx file can also accidentally alter tables, images, embedded objects, or page number fields.

How It Works

The skill turns official document formatting into explicit, checkable rules instead of relying only on a style template:

• Mode selection: white produces plain text documents, redhead produces complete documents with a red issuing-authority mark, and redhead_space reserves the red header area for printing on preprinted letterhead paper.
• Page setup: fixed A4 size, 37mm top margin, 35mm bottom margin, 28mm left margin, 26mm right margin, 156mm × 225mm text area, and 0 point spacing before and after paragraphs.
• Typography: titles use FZXiaoBiaoSong-B05S, first-level headings use Hei, second-level headings use Kai, third-level headings and body text use FangSong, page numbers use Song, and Arabic numerals plus Latin letters use Times New Roman.
• Existing document reformatting: read the .docx, apply body and hierarchy rules paragraph by paragraph, skip paragraphs containing images, charts, or embedded objects, validate compliance, then save a new file named “(formatted) + original filename”.

Boundaries and Notes

It is suitable for formatting official documents, notices, letters, and internal files, but it does not replace content review, approval workflows, or visual design of red headers. Check the local font environment, refresh page number fields, configure even and odd pages correctly, and avoid replacing character-based indents such as w:firstLineChars="200" with fixed centimeter values. The output creates a new file and does not overwrite the original.