MetaObjects

You can author metadata (fields, entities, relationships, enums) in YAML or JSON, configure and run code generation with hand-edit-preserving regeneration, verify drift across database/codegen/templates, build typed prompt templates with deterministic rendering, wire generated code into runtime CRUD apps with REST routes and web forms, and cut npm/TypeScript releases.

Engineers adopting or already using MetaObjects metadata-driven development: developers authoring metadata schemas, maintainers running codegen and drift verification, teams porting implementations across Java/Python/C#, and release managers publishing @metaobjectsdev npm packages. Fit-assessment and audit skills serve teams evaluating or measuring adoption.

Use the metaobjects-fit-assessment skill before adoption. It is read-only and propose-only: it analyzes a not-yet-adopted project, identifies what would migrate, describes the end-state and drift-protection payoff, and produces a decision-grade, evidence-cited report. Post-adoption, metaobjects-audit produces a scored, prioritized adoption report.

The releasing skill covers cutting and publishing releases of the @metaobjectsdev npm/TypeScript packages: bumping the published npm version, promoting merged work to npm latest, and refreshing version references after a release. It is triggered by requests like 'do a release' or 'release 0.x.y'.

Metadata is authored in YAML or canonical JSON, with custom vocabulary registration via providers. Code generation supports configurable generators, targets, and dialects, and the cross-language-porting skill covers Java, Python, and C# implementations kept aligned to the conformance corpus. Runtime integration includes REST routes and a web client with forms, grids, and filters.