Minimax DOCX

Core responsibilities:

• Produce complete, professional .docx deliverables ready for distribution
• Command the full vocabulary of document elements (covers, TOC, running headers/footers, pagination, charts, tables) and deploy them based on document purpose and user needs
• For new documents without a template, consult guides/best-practices.md for sensible defaults
• When given a reference document or template, mirror its structure and formatting conventions
• Maintain consistent visual rhythm through spacing, alignment, and typographic scale
• Guarantee schema compliance and reliable rendering across Word, WPS, and LibreOffice

Workflow

Technology Stack

Prohibited: python-docx, docx-js, or any third-party DOCX abstraction libraries.

Format Conversion Guidelines

Reference Guide

Project Layout

minimax-docx/                         (Skill installation - read-only at runtime)
+-- SKILL.md                    Entry point
+-- docx_engine.py              Build orchestration (main entry)
+-- guides/
|   +-- development.md          Implementation patterns
|   +-- troubleshooting.md      Error resolution
|   +-- styling.md              Visual design guidelines
|   +-- best-practices.md       Sensible defaults
+-- schema/
|   +-- ecma376_parser.py       Dynamic element ordering from ECMA-376
+-- quality/
|   +-- rules.py                Rule-based validation engine
|   +-- findings.py             Structured validation results
|   +-- auditor.py              Document audit pipeline
+-- packaging/
|   +-- opc.py                  OPC-compliant packaging
+-- visuals/
|   +-- palettes.py             Python colour schemes
|   +-- backdrops.py            Background image rendering
+-- diagnostics/
|   +-- compiler.py             Compilation error analysis
+-- engine/
|   +-- diagrams.py             Chart generation (matplotlib)
|   +-- inspector.py            Document inspection
|   +-- lib/
|       +-- xmlns.py            Namespace registry
|       +-- conformance.py      Element ordering (schema-driven)
+-- blueprints/
|   +-- Blueprint.cs            Full English example
|   +-- Folio.cs                CJK patterns
|   +-- Palettes.cs             Colour schemes
|   +-- Launcher.cs             Entry template
+-- validator/                  Schema validation (pre-built)

<user-workspace>/                     (User's working directory = cwd)
+-- .docx_workspace/            Build staging (auto-created)
|   +-- DocumentFoundry.csproj  Copied from blueprints/
|   +-- Launcher.cs             Copied from blueprints/, then edited
|   +-- bin/                    dotnet build output
|   +-- obj/                    dotnet build intermediates
+-- output/                     Final deliverables (auto-created)
    +-- document.docx           Generated output

Build Pipeline

Always invoke python3 <skill-path>/docx_engine.py render from the user's working directory.

Key point: Every docx_engine.py command must be run from cwd, not the skill directory. The .docx_workspace/ staging area and output/ directory are created under cwd.

Pipeline stages:

1. Source compilation (dotnet build)
2. Document generation (dotnet run)
3. Element ordering normalization (ECMA-376 schema-driven)
4. Schema validation (OpenXML SDK)
5. Rule-based quality verification

Commands

# Environment diagnostics and auto-setup
python3 <skill-path>/docx_engine.py doctor

# Build and generate document
python3 <skill-path>/docx_engine.py render [output-name.docx]

# Validate existing document
python3 <skill-path>/docx_engine.py audit <document.docx>

# Quick content preview
python3 <skill-path>/docx_engine.py preview <document.docx>

Prerequisites

Design Principles

Document elements and their typical applications:

Consult guides/best-practices.md for sensible defaults when creating from scratch. If the user supplies a template, follow its conventions instead.

Visual Guidelines

• Favour understated colour palettes; avoid high-saturation defaults
• Provide ample whitespace (margins no less than 72 pt, paragraph spacing no less than 10 pt)
• Establish a clear typographic hierarchy (distinct heading sizes, consistent body text)
• Body text line spacing should be at least 1.5x

Flow Control

Multi-Column Layout

Note: Word columns are flow-based - text fills left to right. Without explicit column breaks, content may not reach all columns.

Pre-Delivery Checks

Content spot-check:

python3 <skill-path>/docx_engine.py preview output.docx