habitat-package-frame
Mental model for inert reusable support that carries no product, runtime, or projection authority.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Mental model for inert reusable support that carries no product, runtime, or projection authority.
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-package-frame |
| description | Mental model for inert reusable support that carries no product, runtime, or projection authority. |
A package is reusable support. It may own types, algorithms, adapters, or mechanics whose meaning remains stable across product boundaries. It does not declare a provisionable resource, realize a provider, own service truth, project a surface, or select an application runtime.
package = reusable support
resource -> provider -> service -> plugin -> app
The separation keeps reuse honest. Code belongs here when consumers can use it without inheriting a product lifecycle or authority relation. When a helper starts naming provider selection, domain decisions, caller surfaces, or app composition, its meaning has moved into the corresponding kind.
The closed project shell keeps the package local and predictable. Contract
proof establishes public type compatibility; semantics proof establishes
reusable behavior. Those finite proof members support the package without
turning test/ into an open cabinet.
boundary, contract, locality, package, proof, reuse, semantics, support