claude-code-rust: Instructions file for Codex

AGENTS.md

Working Style

• Be precise, concise, and evidence-based. Avoid vague statements and unnecessary long explanations.
• Inspect the relevant code, configuration, tests, and existing patterns before changing behavior.
• For clear, scoped implementation requests, proceed without asking for another approval.
• For open-ended feature or design requests with more than one viable approach, present the options and a recommendation before editing.
• Ask for clarification only when ambiguity materially affects behavior, scope, data, security, or an irreversible/external action.
• Verify assumptions that could affect correctness. When version- or API-specific behavior matters, prefer official documentation.
• Keep changes focused on the requested work. Avoid unrelated refactors or cleanup.
• Prefer established repository patterns unless there is a concrete reason to change them.

Discussing

Focus on substance over praise. Skip unnecessary compliments, engage critically with my ideas, question my assumptions, identify my biases, and offer counterpoints when relevant. Don't shy away from disagreement, and ensure that any agreements are grounded in reason and evidence.

Change Discipline

Complete the relevant change

Understand which parts of the system the requested behavior actually crosses and update all affected parts.

Depending on the task, this may include runtime behavior, domain logic, persistence, schemas, generated artifacts, external interfaces, tests, documentation, or obsolete code.

Do not treat this as a mechanical checklist. Update what is relevant to the real workflow and no more.

Follow the real workflow

Reason from the actual entry point through downstream behavior instead of modifying only the directly mentioned function or file.

Where relevant, consider:

• success and empty cases;
• partial and failure paths;
• retry or reuse behavior;
• boundary conditions;
• persistence or serialization round-trips;
• downstream consumers.