Menu
Mental model for AGENTS.md as a local navigation and boundary surface rather than architecture authority or project memory.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-agent-router-frame |
| description | Mental model for AGENTS.md as a local navigation and boundary surface rather than architecture authority or project memory. |
Activation: None. This lowercase
skill.mdis an unregistered design seed; the adjacent Habitat packets remain the only structural and source authority.
An AGENTS.md is the first local reading surface at a package or service-module
ownership boundary. It answers why the component exists, which product
capability it owns, how that capability behaves, which concepts and entities
carry its meaning, what enters and leaves, where its interfaces and boundaries
sit, where deeper authority lives, and how local claims are proved.
The router is intentionally smaller than the system it describes. It is a product-context and navigation router, not a substitute for architecture, design history, a target inventory, code narration, JSDoc, or an active work log. It explains why the code exists rather than restating what the code says. Durable local product facts belong here. Deeper explanations and evolving decisions belong with their conceptual owners and are reached through links.
Context narrows as an agent enters the repository, a package kind, a specific package, and then a service module. Each router adds only the facts needed at that boundary and preserves a route back outward. This produces a lattice of local context rather than one root document that must know every interior.
A useful router makes its component legible without making it sovereign over its neighbors. Purpose and behavior name the product outcome. Concepts name the entities and distinctions needed to reason locally. Boundaries name what the component may own. Flow names what enters, what leaves, and which layer decides. Interfaces name the admitted handoffs. Routes point to canonical owners. Validation names the nearest honest check.
Authored Markdown edges let editors derive backlinks while keeping the route human-readable. Generated backlink inventories would create another state owner and are unnecessary.
