菜单
Mental model for locating work in RAWR's blueprint kinds while keeping semantic direction, ownership, and structural proof distinct.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Mental model for a sealed service whose context and authorship narrow toward operation handlers.
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.
Mental model for inert reusable support that carries no product, runtime, or projection authority.
| name | habitat-blueprint-direction |
| description | Mental model for locating work in RAWR's blueprint kinds while keeping semantic direction, ownership, and structural proof distinct. |
Activation: None. This lowercase
skill.mdis an unregistered design seed. It informs judgment but creates no discovery, enforcement, or runtime authority.
A blueprint kind is a sealed architectural habitat. It gives one class of work a stable name, a bounded interior, known public faces, and a predictable handoff to neighboring kinds. The enclosure is valuable because an author can reason locally without reconstructing the whole repository.
A blueprint is not a capability or niche. A capability adds a reusable facet to an admitted instance. A niche governs a community selected from accepted instance and capability facts. Those relations are additive; neither may silently weaken the instance's blueprint kind.
RAWR's durable direction is:
packages support
resources declare
providers implement
services own
plugins project
apps select
Nx schedules
Habitat asserts
tests prove
These are different authorities, not interchangeable folder labels. Shared infrastructure does not transfer ownership. A namespace does not become an owner. A runtime projection does not become capability truth.
Work moves toward the smallest kind that can own its meaning. Inside that kind, context narrows from public boundary to local decision. Across kinds, handoffs cross explicit public faces rather than mechanical source directories.
Strong boundaries make bad destinations unavailable. A vague shared,
internal, or utils container is not neutral: it erases the reason a thing
exists and expands the context required to change it. When matter does not fit
the admitted kinds, the unresolved question is ownership, not where to hide a
file.
Within a v3 blueprint, one structural spine is a singular anchor and therefore
lives at the blueprint root as structure.toml. Directory trees are reserved
for genuinely plural rule families whose members need additional local
context; nesting is not a substitute for naming the blueprint's one relation.
The skill seed supplies orientation. Neighboring structure.toml files close
filesystem possibility, pattern.md files assert source relations, TypeScript
owns type compatibility, and behavioral tests prove the capability itself.
None may impersonate another.