https://stackonward.com/tags/claude.md/Recent content in CLAUDE.md on StackOnwardHugoen-USFri, 11 Sep 2026 03:40:00 +0800https://stackonward.com/posts/agents-md-claude-md-project-rules/Fri, 11 Sep 2026 03:20:00 +0800https://stackonward.com/posts/agents-md-claude-md-project-rules/<p>How to write AGENTS.md starts with who a fact stays true for, and whether it should change a coding agent&rsquo;s next file or command. Repo-wide maps, canonical commands, and cross-module boundaries belong at the repository root. Rules that only bind backend, frontend, or a worker sit in that directory. Habits that hold across repositories stay in the user-global file. What this task must change stays in the current prompt. CLAUDE.md uses the same content boundary; Claude Code just finds it through its own files.</p> <p>If the root file also stores frontend commands, backend migrations, a release workflow, and “do not touch deploy this time,” four different lifetimes enter unrelated sessions. Confirm the fact in code or build config first, then keep the long-lived rule in the smallest scope that still needs it. Workflows, task variables, and hard stops belong to other mechanisms. The same scope-and-mechanism split is already mapped in <a href="https://stackonward.com/posts/claude-code-codex-configuration-guide/">Claude Code configuration</a>.</p>https://stackonward.com/posts/claude-code-codex-configuration-guide/Fri, 11 Sep 2026 02:00:00 +0800https://stackonward.com/posts/claude-code-codex-configuration-guide/<p>Claude Code configuration has to answer two questions: who should see this fact, and how it should take effect. Habits that hold across repositories belong at the user layer. Facts the team shares belong in the repo. Rules that only bind frontend or backend sit next to that directory. This change stays in the prompt. A repeatable judgment workflow becomes a skill. A mechanical action that must run is a hook, a permission, or existing CI.</p> <p>The split does not require a separate config repository or a new directory template. It starts from the repo already in use and moves facts out of chat logs, global files, and duplicated project rules until each fact has one source of truth. Claude Code and Codex can share that source. Each client still owns its file format, discovery order, and events.</p>