hwpx-templates

What problem does it solve?

Generating complex HWPX reports and official documents from existing templates is error-prone because placeholders are distributed across ZIP-level XML files and auto-generated namespace prefixes can break renderers; this Skill standardizes a safe, repeatable workflow for template selection, placeholder discovery, ZIP-level replacements, namespace normalization, and verification.

Core Features & Use Cases

• Template selection policy that prefers user-uploaded forms, falls back to a packaged report-template, and avoids HwpxDocument.new() for non-template workflows.
• Full-text template inspection using ObjectFinder to enumerate real text runs before designing replacements, preventing blind or destructive substitutions.
• ZIP-level replacement utilities for bulk and sequential placeholder mapping so identical placeholders can be replaced in order across section XML files.
• Post-replacement namespace normalization via a regex-based script to convert auto-generated ns aliases to standard hh/hc/hp/hs prefixes, preventing blank-page rendering in some viewers.
• Use cases: quickly generate public-facing official documents, internal reports, or user-customized templates while preserving complex table and decoration structures that are hard to recreate via XML-first APIs.

Quick Start

Copy the chosen .hwpx template to a working path, run an ObjectFinder scan to collect placeholders, apply bulk and sequential replacements, and then execute scripts/fix_namespaces.py on the output file before final verification.