Menu
Customize CLAUDE.md file(s) for either the user or a project, including guidance on project, subdirectory, and user-level instruction scope.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Planning-centric workflow for substantial work across software, analyses, artifacts, documentation, and configuration. Invoke manually with $work-cycle when alignment matters; not for straightforward one- or two-edit requests.
Create or update developer-facing and agent-facing project documentation, or run module-scoped codebase audits. Invoke manually with $documentation for codebase maps, module documentation, codebase review/audit workflows, and README.md or AGENTS.md work.
Documentation subskill for project hygiene maintenance. Use through $documentation when the user asks to maintain, clean up, health-check, refresh AGENTS.md/notebook/TODOs, inspect git branches/PRs/stashes, or review overall project state. Do not use for codebase audit, codebase review, release-check, or module-scoped bug-finding requests; those belong to module-codebase-review.
Manual-only workflow for codebase audit, codebase review, release-check, paper-freeze-check, and module-scoped multi-agent read-only bug/code-smell audits that produce a prioritized notebook report and TODO-ready findings. Use this instead of maintain-project for requests that ask to audit or review code behavior.
Ergonomic notebook-backed TODO capture for deferred work. Invoke manually with /defer when the user asks to defer, save, park, or add a TODO for later work while preserving the current conversation context.
Initialize a project workspace for Claude Code with project instructions, repository checks, notebook scaffolding, optional remotes, and optional O2/SLURM setup. Invoke manually with /init-project for first-time project setup, notebook bootstrap, project remotes, or O2/SLURM setup.
| name | agents-md |
| description | Customize CLAUDE.md file(s) for either the user or a project, including guidance on project, subdirectory, and user-level instruction scope. |
Use this subskill when changing durable agent instructions in CLAUDE.md files.
Claude Code can use one CLAUDE.md per directory, including the project root. Agents working inside subdirectories automatically load and concatenate the relevant CLAUDE.md files along that path.
Use project CLAUDE.md files for stable context:
Subdirectory CLAUDE.md files should contain context specifically relevant to understanding or modifying that part of the codebase. For typical scientific programming projects, extensive directory-specific prompt structure is usually unnecessary.
Do not use CLAUDE.md as technical documentation; either the documentation becomes stale when the code changes, or every code change incurs the overhead cost of updating the documentation file.
Claude Code loads the user-owned ~/.claude/CLAUDE.md. The unified installer preserves that file and adds an @<config-repo>/claude/global/CLAUDE.md import line.
Use this command for first-run setup:
${CLAUDE_HOME:-$HOME/.claude}/bin/config-agent-tool install --agent claude
Changes to the shared global file are picked up by new Claude Code sessions through the import. Changes to the user's own ~/.claude/CLAUDE.md should remain short and personal.