What problem does it solve? Maintaining separate TypeScript interfaces, backend validators, SQL contracts, and frontend form configurations for the same data model leads to drift and duplicated effort. This Skill establishes one TypeBox schema file per model that drives types, runtime validation, SQL function documentation, and generated forms, lists, and pickers. ## Core Features & Use Cases - Single-source schema definition: Create Item, Row, LookupRow, payload, and response schemas per model with derived TypeScript types via Static<>. - UI annotation system: Use standard JSON Schema annotations plus x-form, x-list, x-lookup, x-filter, x-ref, and x-transient to drive form fields, list columns, pickers, and generated SQL filters. - Database conventions: Enforce bigint identity primary keys starting at 100, string-typed ids in TypeScript, and reference handling for catalogs, documents, and multi-writer registers. - Use Case: When adding a new bank catalog model, define one bank.schema.ts file and get validated payloads, list/get/save/delete/lookup contracts, and a generated form and list view without writing separate interfaces. ## Quick Start Ask the AI to create a TypeBox model schema for a new catalog model with fields for code, name, and a reference to another model, including list and form annotations.