What problem does it solve? Porting a feature from one language implementation to another risks silent behavioral drift, un-idiomatic code, or accidentally changing shared semantics. This Skill provides a disciplined workflow for porting metaobjects features between TypeScript, Java, Python, and C# while keeping every port aligned to the shared conformance corpus. ## Core Features & Use Cases - Tier-based change taxonomy: Classifies every aspect of a port as Tier 1 (invariant semantics, wire format, error codes), Tier 2 (idiomatic naming, null handling, async style), or Tier 3 (internal implementation), so you know exactly what may and may not change. - Conformance-first workflow: Requires fixtures to exist and pass on the reference implementation before porting, then uses the conformance runner as the oracle for the new port. - Honest progress tracking: Maintains an expected-failures ledger and forbids silently regenerating golden files to force a green check. - Use Case: You implemented a new metadata validation feature in TypeScript and need it in Python. Follow the workflow to write the Python ConformanceAdapter, run the shared corpus against it, and record any genuinely incomplete cases in the ledger. ## Quick Start Port the metadata validation feature from the TypeScript implementation to Python, keeping it aligned with the conformance corpus.
