メニュー
Mental model for Grit patterns as semantic source relationships that complement structure without replacing types or behavior.
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-grit-pattern-frame |
| description | Mental model for Grit patterns as semantic source relationships that complement structure without replacing types or behavior. |
Activation: None. This lowercase
skill.mdis an unregistered design seed. Executable Grit authority remains in adjacentpattern.mdpackets.
A Grit pattern names a relation in source code. It is valuable when the relation is structural enough to recognize from syntax and meaningful enough to prevent a recurring ownership, direction, or boundary defect.
The pattern is not a text search wearing an architectural name. Its helpers should expose the semantic predicates that make the policy understandable: which owner is in view, which edge is allowed, which boundary is crossed, and which relation is missing.
Good source law narrows possibility through positive relationships. It favors stable kinds and dependency direction over exact message text, current filenames, product inventories, or migration residue. Named helpers carry short comments because their purpose is the policy relation, not the parser mechanics.
Grit complements rather than duplicates:
structure.toml owns filesystem geometry.A passing pattern proves only the relation it can observe. It cannot establish runtime behavior, module resolution, security, or lifecycle outcomes by implication.