What problem does it solve?
This Skill helps you define and wire a type-safe relational database schema so your rendering engine can store state in a consistent, statically-typed, SQL-like way instead of relying on unstructured ECS-style component attachment.
Core Features & Use Cases
- Declare entities (tables) and components (columns): Create multiple entity types with fixed, statically-typed columns and defaults per column.
- Model relationships with explicit foreign keys: Define cross-table links via typed foreign key columns for predictable data flow between systems.
- Register schemas and use CRUD/query patterns: Initialize the global database schema in the correct order and perform typed reads/writes plus reactive hook-driven incremental updates.
Use case: when adding a new rendering subsystem (e.g., scene nodes, materials, transforms), define new tables and columns, connect dependencies with foreign keys, and then query or react to changes incrementally.
Quick Start
Register a new entity type and its columns (including any foreign keys) with the global database, then use EntityWriter to create rows and EntityReader or ComponentReadView to read typed column values.