Template Migrator Skill

Migrating LaTeX templates without breaking figures requires fixing single and double column sizing mismatches. The process loads target template constraints and applies atomic, rollback-safe patches to adjust float behavior and validate layout outcomes.

Undefined control sequence errors after switching templates occur due to template-specific macro and package incompatibilities. You must resolve these E3 errors by running a compile-then-verify loop and replacing unsupported macros with target template equivalents.

Fixing page budget drift when changing journal document classes involves comparing the expected page count against the target template constraints. You iteratively apply transactional patches to the main .tex file and recompile until the page budget matches.

Yes, you can automatically adjust figure and table sizes for double column LaTeX templates. The migration process detects E1 sizing mismatches and applies template configuration rules to resize floats appropriately for the target documentclass.

The best way to ensure layout safety during LaTeX template migration is using atomic transactional patch writing. This prevents partially migrated states by keeping patches in-memory until fully assembled, then applying visual layout detection to verify remediation.

Yes, you need a layout detective report and target template constraints from a config file to switch LaTeX templates effectively. These inputs allow the migration process to iteratively correct figure sizing, page budget, and macro compatibility issues.