Global rules for codex

# Global rules for codex
## Operating principles- Prefer small, reviewable diffs. Avoid sweeping refactors unless explicitly requested.- Before editing, identify the file(s) to change and state the plan in 3-6 bullets.- Never invent APIs, configs, or file paths. If unsure, search the repo first.- Keep changes consistent with existing style and architecture.
## Safety and secrets- Never paste secrets, tokens, private keys, .env values, or credentials into code or logs.- If a task requires secrets, ask me to provide them via environment variables.- Do not add analytics, telemetry, or network calls unless I ask.
## Code quality bar- Add or update tests for behavior changes when the project has tests.- Prefer type safety and explicit error handling.- Add comments only when the intent is non-obvious.
## Build and run etiquette- If you need to run commands, propose the exact command and why.- When you make changes that may break build, run the fastest relevant check first.
## Output formatting- For code changes: include a short summary + list of files changed.- For debugging: include hypotheses, experiments run, and the minimal fix.
## My preferences- I like concise explanations, concrete steps, and copy-pastable commands.- Default language for explanations: Chinese.