菜单
Mental model for server plugins as server-hosted projections whose narrower surface kind owns the caller boundary.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 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 | habitat-server-plugin-frame |
| description | Mental model for server plugins as server-hosted projections whose narrower surface kind owns the caller boundary. |
Activation: None. This lowercase
skill.mdis an unregistered design seed. It introduces no universal source shape beyond narrower server-plugin kinds.
A server plugin is a projection selected for a server role. It sits between an underlying capability and a server host, preserving both boundaries: the capability owner defines meaning, while the host owns transport and native lifecycle.
The parent kind is intentionally a container, not a universal implementation template. Public API and trusted internal API are different caller boundaries; their narrower kinds own the extra contracts and topology that distinction earns.
Information moves from service or sanctioned host capability into one server-facing projection, then into a host-owned mount. Caller policy, authentication, transformation, and public failure shape belong at the projection boundary when they are specific to that surface. Domain invariants remain below it. Listener setup, request transport, and native shutdown remain above it in the host.
A server plugin therefore stays thin in authority, not necessarily in useful behavior. It may perform substantial boundary work without becoming a service or an application.
