Repository organization

Keep each repository easy for humans and agents to navigate by putting durable context, reusable guidance, automation, and decisions in the right layer. Prefer the smallest durable home that will be loaded at the time it matters.

For source conventions, apply codebase-design: keep each capability together, expose complete operations, and extract only when the split improves understanding. Use domain-organization for domain/role paths. Keep the governing rule short in always-on instructions and link the full examples; maintain one canonical definition instead of competing style lists.

When to use

• A user asks where to put a new instruction, convention, policy, skill, command, script, workflow, reference doc, or ADR.
• A repo is accumulating scattered Markdown, duplicated agent instructions, or ad hoc decision notes.
• A change introduces a naming, layout, vendor, architecture, security, deployment, or process decision that future contributors should not re-litigate.
• A README is being created, reorganized, or reviewed for standard structure.
• A user asks whether something belongs in AGENTS.md, .agent/context/, .agent/policy/, .agent/workflows/, skills/, docs/, scripts/, or presets/.
• A project is being bootstrapped from the darkmatter template and needs its local context filled in cleanly.