Claude Code Best Practices

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

37 stars 7 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add iamneilroberts/claude-skills --skill claude-code-best-practices
Manual install
git clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/claude-code-best-practices ~/.claude/skills/claude-code-best-practices

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Claude Code best practices reference

Routes to a local mirror of the official docs at `~/.claude/anthropic-docs/` (refreshed weekly
from https://code.claude.com/docs/llms.txt) — canonical Markdown; cite the source path when you
reference a fact. Read the file for the topic at hand instead of guessing.

## How to look something up

- **Know the topic?** Read `~/.claude/anthropic-docs/en__<slug>.md` (route table below).
- **Don't know it?** `cat ~/.claude/anthropic-docs/_llms.txt | grep -i <keyword>`
- **API/SDK topic** (not the CLI)? Check `en__agent-sdk__*.md`.

## Route table — topic → local file

| Topic | Local file |
|---|---|
| **Best practices overview** (workflow patterns, common failures) | `en__best-practices.md` |
| **CLAUDE.md** (format, placement, what to include/exclude) | `en__memory.md` |
| **Context window** (how it fills, what loads at startup) | `en__context-window.md` |
| **Cost / reduce token usage** | `en__costs.md` |
| **Prompt caching** (also see platform.claude.com docs) | `en__costs.md` (CC-specific) |
| **Checkpointing / /rewind** | `en__checkpointing.md` |
| **Sessions** (continue, resume, fork, naming) | `en__sessions.md` |
| **Interactive mode** (/clear, /compact, /btw, key bindings) | `en__interactive-mode.md` |
| **Slash commands / built-in commands** | `en__commands.md` |
| **Hooks** (events, JSON shape, examples) | `en__hooks-guide.md` + `en__hooks.md` |
| **Skills** (SKILL.md format, when to use) | `en__skills.md` |
Read the full skill on GitHub

Details

Skill name
claude-code-best-practices
Path
skills/claude-code-best-practices/SKILL.md
Repo updated
21 August 2026

FAQ

What does the Claude Code Best Practices skill do?

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

How do I install the Claude Code Best Practices skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill claude-code-best-practices. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Claude Code Best Practices popular?

It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.

Related skills

Brag

37

iamneilroberts/claude-skills

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

Writing & Content

Branch

37

iamneilroberts/claude-skills

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

Git & Code Review

Codex

37

iamneilroberts/claude-skills

Delegate a task or question to the OpenAI Codex CLI running as an isolated subagent, then relay its answer. Use when the user invokes /codex <prompt>, says "ask codex", "have codex look at / do X", or wants a second independent model to investigate a question or make a self-contained edit. Read-only by default; /codex --write lets Codex edit the working tree. Distinct from /codex-review, which is the structured JSON review gate — /codex is a general-purpose Codex delegate.

Software Development

Deepagents

32

joneqian/claude-skills-suite

LangChain Deep Agents framework for building autonomous coding agents. Use for agent harness, backends, subagents, human-in-the-loop, long-term memory, middleware, and CLI-based agent development.

AI, LLMs & Agents

Unity AI Navigation

40

Nice-Wolf-Studio/unity-claude-skills

Unity 6 AI and navigation guide. Use when working with NavMesh, pathfinding, NavMeshAgent, NavMeshSurface, NavMeshObstacle, off-mesh links, or Unity Sentis (ML model inference). Covers AI navigation package, runtime NavMesh baking, and common AI patterns like state machines and behavior trees. Based on Unity 6.3 LTS documentation.

AI, LLMs & Agents

Evaluate

37

iamneilroberts/claude-skills

Tear down a third-party product/tool/library from a single URL and answer two questions: (1) is the product worth adopting as-is — installed into your Claude Code workflow (a CLI, MCP server, skill, or dotfile) or otherwise kept around — and (2) are there features or code worth lifting into your current repo. Most evaluations are hunting for one of those two wins. It resolves the URL to its source (repo, README, launch post — with Reddit and paywalled-fetch fallbacks), characterizes the product from its docs, clones the code locally when it's open source, then fans out read-only subagents — ea

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.