Reference for Claude Code features and best practices: writing CLAUDE.md, skills, hooks, sub-agents, agent teams, headless mode, scheduled tasks, worktrees, batch, frontend verification. Use when authoring/auditing CLAUDE.md, configuring Claude Code, writing skills, or orchestrating agents. Keywords CLAUDE.md, skill, hook, sub-agent, agent team, headless, worktree, /loop.
Claude Code Best Practices
Reference knowledge for Claude Code features. Each topic has a local summary and a canonical URL.
Prime Directive: CLAUDE.md Is Load-Bearing
CLAUDE.md is the only file that goes into every Claude Code conversation by default. Every line competes for a finite instruction budget (~150–200 instructions, of which ~50 are already spent on the system prompt). Authoring or editing a CLAUDE.md — global, project, or skill-scoped — is always a high-leverage operation.
Whenever the user asks you to write, refactor, audit, or add to a CLAUDE.md, load writing-claude-mdfirst and apply it. Proactively flag bloat, task-specific rules, linter-style guidance, and long inline examples. Prefer extracting deep content into agent_docs/ (or equivalent) with a one-line pointer from the root file.
Fetch Strategy
Quick answers: use the local summary in the reference file
Before making changes or giving definitive guidance: WebFetch the canonical URL to get the latest docs, then act on the live content