Make Claude Code work better, one practice at a time.
Clear guides, carefully structured tips, and practical judgment for building reliable workflows with Claude Code. Every page links back to its source and distinguishes documented advice from hands-on verification.
Field guides
All guides ↗Reference for Claude Code startup flags, top level subcommands, and startup environment variables when launching Claude Code from the terminal. Table of Contents 1. Session Managem…
[](https://github.com/shanraisshan/claude code best practice/blob/main/implementation/claude commands implementation.md) Claude Code commands — frontmatter fields and official buil…
[](https://github.com/shanraisshan/claude code best practice/blob/main/.mcp.json) MCP (Model Context Protocol) servers extend Claude Code with connections to external tools, databa…
Persistent context via CLAUDE.md files — how to write them and how they load in monorepos. 1. Writing a Good CLAUDE.md A well structured CLAUDE.md is the single most impactful way …
Interactive lessons teaching Claude Code features with animated demos. Each power up teaches one thing Claude Code can do that most people miss. Introduced in v2.1.90. Usage Power …
[](https://github.com/shanraisshan/claude code best practice/blob/main/.claude/settings.json) A comprehensive guide to all available configuration options in Claude Code's settings…
[](https://github.com/shanraisshan/claude code best practice/blob/main/implementation/claude skills implementation.md) Claude Code skills — frontmatter fields and official bundled …
[](https://github.com/shanraisshan/claude code best practice/blob/main/implementation/claude subagents implementation.md) Claude Code subagents — frontmatter fields and official bu…
Practical tips
All tips ↗Spin up 3–5 git worktrees at once, each running its own Claude session in parallel. It's the single biggest productivity unlock, and the top tip from the team. Personally, Boris us…
Pour your energy into the plan so Claude can 1 shot the implementation. One person has one Claude write the plan, then they spin up a second Claude to review it as a staff engineer…
After every correction, end with: "Update your CLAUDE.md so you don't make that mistake again." Claude is eerily good at writing rules for itself. Ruthlessly edit your CLAUDE.md ov…
Reuse across every project. Tips from the team: If you do something more than once a day, turn it into a skill or command Build a /techdebt slash command and run it at the end of e…
Here's how the team does it: Enable the Slack MCP, then paste a Slack bug thread into Claude and just say "fix." Zero context switching required. Or, just say "Go fix the failing C…
a. Challenge Claude. Say "Grill me on these changes and don't make a PR until I pass your test." Make Claude be your reviewer. Or, say "Prove to me this works" and have Claude diff…
The team loves Ghostty! Multiple people like its synchronized rendering, 24 bit color, and proper unicode support. For easier Claude juggling, use /statusline to customize your sta…
a. Append "use subagents" to any request where you want Claude to throw more compute at the problem. b. Offload individual tasks to subagents to keep your main agent's context wind…
Ask Claude Code to use the "bq" CLI to pull and analyze metrics on the fly. The team has a BigQuery skill checked into the codebase, and everyone uses it for analytics queries dire…
A few tips from the team to use Claude Code for learning: a. Enable the "Explanatory" or "Learning" output style in /config to have Claude explain the "why" behind its changes. b. …
Editorial notes are independent interpretation, not claims of Anthropic endorsement. Product behavior can change; check the linked official documentation before relying on version-sensitive instructions.