Claude Code Best Practices

Claude Code Best Practices
The community handbook for shipping real software with Claude Code.
Guides, working plugins, drop-in starter kits, published benchmarks, and a dogfooded .claude/ setup you can copy.
Last updated: September 15, 2026 · v1.7 · Covers Claude Code v2.1.272 · Opus 4.8 / Sonnet 4.6 / Haiku 4.5

Browse the rendered site: MuhammadUsmanGM.github.io/claude-code-best-practices

Why this repo exists

Claude Code is powerful out of the box, but the gap between *"it works"* and *"it ships production code reliably"* is closed by a handful of patterns: a sharp CLAUDE.md, the right permission mode, hooks that catch mistakes before they reach disk, skills for repeat tasks, and a cost model you can reason about. Most of that knowledge is scattered across blog posts, Discord threads, and internal wikis.

This repo pulls it together into one place — opinionated, tested, and dogfooded on itself. Every convention here has been used to build the repo you're reading: the .claude/ directory wires the hooks, the /lint-docs skill runs the same checks CI does, and the commit log is a working example of the Conventional Commits skill under plugins/commit-helper/.

What you'll find

- 30+ guides covering fundamentals, workflows, permissions, advanced architecture, cost management, and security — including auto mode and its safety classifier.
- 11 CLAUDE.md templates for React, Python, Go, Rust, Rails, Django, Next.js, Spring Boot, Flutter, monorepos, and a minimal starter.
- 5 starter kits — whole-project drop-ins (CLAUDE.md + .claude/ with settings, skills, and hooks) for React, Next.js, Python, Go, and Rust.
- Working plugin (commit-helper) with a Conventional Commits skill and a PreToolUse hook that blocks secrets before they're committed.
- Drop-in skills and hook…