What problem does it solve? Maintaining the generated API::Docker::Type::* class hierarchy requires knowing exactly where each change belongs — the generator, its YAML data files, or the runtime DSL — because hand-editing generated files breaks the byte-identical verification suite and is silently lost on regeneration. ## Core Features & Use Cases - Change routing: Maps each kind of edit (prose, Perl field names, inline class names, deliberate spec deviations) to the correct maint/ data file or script. - Generation rules enforcement: Documents the non-obvious invariants — never hand-edit generated files, the generator only creates never overwrites, caller-data keys under additionalProperties pass through byte for byte, and null handling differs for known versus unknown fields. - Drift verification workflow: Defines completion criteria via spec-to-type.pl --verify, spec-drift-check.pl baselines, and the full test suite. - Use Case: When a drift check reports that a newer Docker swagger adds fields to HostConfig, use this Skill to decide whether the fix goes in spec-to-type-names.yaml, the exceptions file, or the generator itself, then regenerate and verify. ## Quick Start Ask the assistant to update the API::Docker type model for a newer Docker swagger spec and verify the generated classes pass the drift check.
