auto-generated-model-repository-pattern

To migrate static model configurations to a dynamic database-backed repository, use this skill to move configurations into Convex DB storage while maintaining client-server separation through reactive client hooks and server-side static helpers.

Yes, you can use reactive hooks to load models from a Convex database on the client side. The skill provides useModels and useModel hooks that fetch configurations from a centralized database-enabled store with lazy loading support.

The best way to inject AUTO_MODEL at runtime without storing it in the database is to use this skill's injection path, which routes requests to the optimal model dynamically while keeping the configuration store clean and separated.

Yes, this repository pattern supports lazy loading and explicit loading checks for models. It ensures configurations are fetched only when needed via client-side hooks, satisfying requirements for explicit loading state verification.

Server-side static helpers access model configurations without runtime queries by providing immediate access to presets directly from the database-backed repository, bypassing the reactive client hooks used for dynamic fetching.

You should separate client and server model access in a reactive database application when migrating from static configs to dynamic DB storage, ensuring the client uses reactive hooks while the server uses static helpers for immediate configuration access.