Word 专业交付
Use this as the default skill for formal Chinese Word deliverables. It is the installed version of the user's Word production standard; do not use a generic visual-card or marketing-page style unless the user explicitly asks for one.
Mandatory reading
Before taking document actions, read the complete professional standard. It is authoritative for scope control, content fidelity, typography, tables, pagination, validation, and delivery.
Then read exactly the task route that applies:
- New document: tasks/create_new.md
- Existing document reformat or repair: tasks/reformat_existing.md
- Document structure: tasks/build_structure.md
- Table design or repair: tasks/style_tables.md
- Render review: tasks/verify_render.md
- Final cleanup and delivery: tasks/finalize_delivery.md
Use the corresponding detailed references when the task needs them:
- Layout selection: references/adaptive_decision_tree.md
- Font system: references/typography_rules.md
- Design tokens: references/style_tokens.md
- Tables: references/table_rules.md
- QA: references/qa_checklist.md
- Environment limitations: references/known_limitations.md
Operating rules
- Diagnose the requested action, the exact delivery object, and what is out of scope before writing or editing.
- Preserve facts, numbers, dates, units, sources, conclusions, and user-provided terminology. Do not introduce unapproved content, a cover, an executive summary, or extra sections.
- Treat supplied files as read-only. Create a separate output file; never overwrite, remove, or move the original.
- Build or repair the style system first. Use the user's formal Chinese hierarchy, restrained grayscale palette, semantic table layout, natural pagination, and dynamic header/footer rules.
- Use native Word structures for headings, lists, tables, captions, page breaks, headers, and page numbers. Do not imitate a slide deck with decorative cards, excessive color blocks, or image-rendered text.
- For multi-section documents, write and review one major section at a time. Re-read inserted text and its style immediately; correct style inheritance or list leakage before proceeding.
- Run the required audits, render every page, visually inspect every page at 100%, repair every defect, then re-render. Do not claim completion based on a partial preview.
- Finalize only the clean delivery file. Default to DOCX; export PDF only when requested. Do not return temporary renders, debug files, or near-duplicate versions.
Tools and bundled material
Use the retained tools rather than recreating their checks:
scripts/formal_style_pack.py— Word styles and formal document helpersscripts/font_declaration_audit.py— verifies DOCX East Asian, ASCII, and HAnsi font declarationsscripts/heading_audit.py— checks heading hierarchy and title consistencyscripts/table_alignment_audit.py— checks semantic alignment and layout risks in tablesscripts/render_and_verify.py— produces page renders and a basic completeness check; manually inspect every page afterwardscripts/finalize_docx.py— creates a clean final copy without overwriting the source
Read examples/ only when a similar structure is needed. Run tests/smoke_test.py after changing bundled scripts. Use requirements.txt with the bundled workspace runtime if dependencies must be checked.
Delivery response
After a document task, respond briefly with the completed file link and only the verified scope. Do not narrate implementation details, repeat the document, add unasked-for advice, or describe all files as checked unless they were checked.
