菜单
Mental model for a public API server plugin as an operation boundary around one embedded service and one projected client.
用 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-api-server-plugin-frame |
| description | Mental model for a public API server plugin as an operation boundary around one embedded service and one projected client. |
Activation: None. This lowercase
skill.mdis an unregistered design seed. The API, service, TypeBox, and adjacent Habitat packets retain their qualified authority.
An API server plugin projects one service capability into a public caller boundary. Its three public faces have distinct jobs:
service/ owns capability meaning and internal operation behavior.api.ts owns the public operation tree and caller policy.client.ts owns the caller-facing projection of that tree.The API vocabulary is operations. oRPC procedures are the callable leaves that realize those operations; they do not require the public boundary to be described as a procedure container.
Public input enters through TypeBox-owned schemas and API policy, narrows into an operation, crosses the service boundary, and returns through public result and error mapping. Authentication, authorization, rate limits, public redaction, and caller transformation belong here when they are API-specific. Business invariants remain in the service.
Operation leaves may stand alone and compose into a plain router object. Natural groups may share context or guards while neighboring operations remain independent. A section-level JSDoc on each real group names its purpose, guard, shared capability, behavior, and relation to adjacent operations. Grouping signals real semantics; it is not a device for hiding operation logic outside its authoring site.
The application host owns HTTP, Elysia, fetch adaptation, listener lifecycle, and native mounting. The API plugin publishes an operation boundary, not a server runtime.