Menu
Mental model for one concrete realization of a provider-neutral resource contract.
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.
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.
Basé sur la classification professionnelle SOC
| name | habitat-provider-frame |
| description | Mental model for one concrete realization of a provider-neutral resource contract. |
A provider makes one resource contract real on one vendor or substrate. It
owns concrete clients, configuration decoding, acquisition, release, vendor
failure translation, and the mechanics needed to return the neutral resource
value. Its index.ts is the single realization face.
resource -> provider -> service -> plugin -> app
The provider implements; it does not select itself. App-owned composition chooses a provider and lifetime, then runtime acquisition passes the ready provider-neutral value downward. Services therefore depend on the resource contract rather than concrete vendor code.
Vendor facts may originate here, but service policy does not. If a concern is stable across providers, it may belong in the resource contract or an inert package. If it changes product meaning, it belongs with the service. The closed nested shell prevents those owners from collapsing into one convenient implementation folder.
acquisition, implementation, lifecycle, provider, resource, translation, vendor