word

<quality_workflow> For all professional deliverables, you MUST follow the "Render & Review" loop:

1. Edit: Use python-docx for structure/styling or the Document library for XML edits.
2. Render: Convert to PDF/PNG using soffice and pdftoppm:
   • soffice --headless --convert-to pdf document.docx
   • pdftoppm -png -r 150 document.pdf page
3. Inspect: Read the generated PNG images. You MUST look for clipped text, overlapping shapes, or misaligned margins.
4. Fix: Address defects and repeat the loop until the document is visually flawless. </quality_workflow>

<technical_workflows>

1. Creating New Documents

• Python: You SHOULD use python-docx. Establish hierarchy with HeadingLevel styles.
• JavaScript: You SHOULD use docx-js. Reference: See references/docx-js.md for syntax.
• CRITICAL: You MUST NOT use \n for line breaks (use Paragraphs). You MUST NOT use Unicode bullets (use numbering config). PageBreak MUST be inside a Paragraph.

<quality_workflow> For all professional deliverables, you MUST follow the "Render & Review" loop:

1. Edit: Use python-docx for structure/styling or the Document library for XML edits.
2. Render: Convert to PDF/PNG using soffice and pdftoppm:
   • soffice --headless --convert-to pdf document.docx
   • pdftoppm -png -r 150 document.pdf page
3. Inspect: Read the generated PNG images. You MUST look for clipped text, overlapping shapes, or misaligned margins.
4. Fix: Address defects and repeat the loop until the document is visually flawless. </quality_workflow>

<technical_workflows>

1. Creating New Documents

• Python: You SHOULD use python-docx. Establish hierarchy with HeadingLevel styles.
• JavaScript: You SHOULD use docx-js. Reference: See references/docx-js.md for syntax.
• CRITICAL: You MUST NOT use \n for line breaks (use Paragraphs). You MUST NOT use Unicode bullets (use numbering config). PageBreak MUST be inside a Paragraph.