Menu
Frame a database as an optional service-owned persistence boundary that projects store capabilities through context.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Mental model for a sealed service whose context and authorship narrow toward operation handlers.
Mental model for locating work in RAWR's blueprint kinds while keeping semantic direction, ownership, and structural proof distinct.
Mental model for Nx as the repository graph and scheduler while project owners retain their qualified build and verification work.
Mental model for one conventional installed Oclif application that owns CLI identity while commands retain qualified capability boundaries.
Mental model for a first-party Oclif command plugin as one host-composed terminal projection on public package boundaries.
Mental model for an application as the concrete selection and realization boundary of the product chain.
| name | service-database-frame |
| description | Frame a database as an optional service-owned persistence boundary that projects store capabilities through context. |
Activation: None. This lowercase
skill.mdis an unregistered design seed. Service, resource, provider, and adjacent Habitat packets retain their qualified authority.
A database is persistence owned by one service, not a module, provider,
resource, or Nx project. It always holds the service's owner-issued migrations
and store implementations. Migrations own physical evolution. A closed
schema interior appears only when the selected database technology requires
physical mappings beyond those authorities. The database does not become a
home for generated clients, memory substitutes, repositories, sessions,
provider wiring, helpers, indexes, or alternate composition faces.
Migration, schema, and store leaves use atomic names because their containing directories already carry the database role.
Physical schema describes storage mapping, not domain identity. Stores remain
private persistence implementations and infer their native record types from
that mapping. They may map persisted records into canonical entities when the
domain models continuing identity, or return value and snapshot projections.
Entity declarations never import database types or stores. Stable domain
identity and transition invariants belong under service or module
model/entities; operation and boundary projections belong under model/dto.
The database has no parallel DTO authority.
provider -> resource -> service base -> named root middleware
-> store capability -> module handler
The provider realizes an external database resource. The application binds that ready dependency into service context. Direct named service-root middleware may use the service-owned database source to project narrow store capabilities. Modules inherit those capabilities through native oRPC context; production modules do not construct persistence or import database internals. Owner-local package proof may inspect a private store without creating a public dependency or alternate production client path.