doc

Topics in the source

• DOCX Skill
• When to use
• Workflow
• Temp and output conventions
• Dependencies (install if missing)
• Environment
• Rendering commands
• Quality expectations

Read or review DOCX content where layout matters (tables, diagrams, pagination). Create or edit DOCX files with professional formatting. Validate visual layout before delivery. 1. Prefer visual review (layout, tables, diagrams). If soffice and pdftoppm are available, convert DOCX -> PDF -> PNGs. Or use scripts/renderdocx.py (requires pdf2image and Poppler). If these tools are missing, install them or ask the user to review rendered pages locally. 2. Use python-docx for edits and structured creation (headings, styles, tables, lists). 3. After each meaningful change, re-render and inspect the pages. 4. If visual review is not possible, extract text with python-docx as a fallback and call out layout risk. 5. Keep intermediate outputs organized and clean up after final approval. Use tmp/docs/ for intermediate files; delete when done. Write final artifacts under output/doc/ when working in this repo. Keep filenames stable and descriptive. Prefer uv for dependency management. Python packages: If uv is unavailable: System tools (for rendering): If installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally. No required environme

This is an excerpt. Refer to the complete source and its current requirements.