Menu
Mental model for plugins as narrow projections of existing capability into one runtime role and surface.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | habitat-plugin-frame |
| description | Mental model for plugins as narrow projections of existing capability into one runtime role and surface. |
A plugin projects existing capability into one role and surface. It owns the caller-facing projection shape and the adapter from service capability to that surface. It does not become service truth, acquire providers, select runtime profiles, or redefine application membership.
resource -> provider -> service -> plugin -> app
The service remains authoritative behind the projection. The app decides whether the plugin participates in a concrete product and supplies the runtime context from above. A server route, CLI command, async function, desktop bridge, or Nx projection is therefore a surface fact, not a new semantic owner.
The generic plugin shell is intentionally small. A narrower plugin blueprint may add one positive source shape for its projection lane, but it only narrows the kind; it does not weaken the generic boundary or invent a parallel framework.
adapter, boundary, plugin, projection, role, service, surface