What problem does it solve? Connecting MetaObjects-generated code to a running application requires knowing the cross-port runtime contracts — how queries return native types, how REST routes are mounted, and how the universal web client consumes them — and getting any of these wrong produces silent drift between layers. ## Core Features & Use Cases - Runtime query wiring: Pass persistence contexts explicitly into generated CRUD helpers and use generated names artifacts instead of literal table or column names. - Cross-port REST contract: Serve the standard five CRUD endpoints with filter operators, sort, pagination, and wire-format rules (integer minor units for currency, ISO-8601 temporals) across TypeScript, Java, Kotlin, C#, and Python backends. - Universal web client: Supply a single EntityFetcher at the app root so generated TanStack Query hooks, forms, and opt-in data grids work against any backend language. - Use Case: You generated an Author entity with MetaObjects and need to mount Fastify routes, implement the repository against your database, and render a sortable, filterable grid in React — this skill walks through each layer with per-language reference fragments. ## Quick Start Use the metaobjects-runtime-ui skill to wire my generated Author entity into REST routes and a React grid against my Postgres database.
