Persist operational learning as atomic, topic-specific notes inside the .codex/notes tree. Use during and after tasks to create or update leaf notes, route them into the right branch, link evidence, and keep the note map navigable.
Traverse the personal note tree in .codex/notes to fetch high-signal context before non-trivial work. Use when starting implementation, debugging, refactoring, architecture changes, or risk analysis; map the task to note branches, read relevant leaf notes,…
Design and evolve the hierarchy of .codex/notes so operational memory stays organized as a navigable tree. Use when new domains emerge, branches become crowded, or note discovery slows down.
Reconcile contradictions and remove stale noise in the .codex/notes tree. Use at phase boundaries or when conflicts appear to merge duplicates, mark superseded notes, archive outdated entries, and keep indexes accurate.
Create or update agent-facing tools in this repository's source-generated tool model. Use when a request asks to add, modify, scaffold, refactor, or secure a tool exposed through REST, MCP, or CLI, including provider-specific request/response DTOs, handler…
Bootstrap a repository derived from this template into a concrete project. Use when Codex needs to clarify the project purpose with the user, choose or confirm the service name, replace `TemplateService` placeholders, refactor project and agentic files to the…
Enforce backend design guardrails for a repository. Use when modifying or reviewing backend code, especially when adding services, endpoints, extractors, clients, dependency-injection wiring, or refactors. Prevent oversized classes, preserve Clean…
Enforce decision-register discipline for this repository. Use when work introduces significant product, architecture, API, data-model, security, dependency, or workflow decisions, so each decision is logged in the registry rooted at docs/specs/DECISIONS.md…