Page blocked in your country?
OpenLibreNet opens it from six other countries, in the browser you already have. Nothing to install, no VPN app, no signup. Free, and you can share the session link so someone else browses it with you.
CLAUDE.md should target under 200 lines per file. 60 lines in humanlayer (still not 100% guaranteed)
Source: Boris
wrap domain-specific CLAUDE.md rules in <important if="..."> tags to stop Claude from ignoring them as files grow longer
Source: Dex
use multiple CLAUDE.md for monorepos - ancestor + descendant loading
Source: Boris
use .claude/rules/ to split large instructions
Source: Claude
keep codebases clean and finish migrations - partially migrated frameworks confuse models that might pick the wrong pattern
Source: Boris
use ASCII diagrams a lot to understand your architecture
Source: Boris
use Ralph Wiggum plugin for long-running autonomous tasks
Source: Boris
What are Claude Code best practices?
Claude Code best practices are the workflows, habits and configuration patterns that get the most out of Claude Code - from how you write CLAUDE.md and manage context, to subagents, skills, hooks, plan mode and full Research → Plan → Execute → Review → Ship pipelines. This page distills 82 tips and 154 practices from the community's most-followed best-practice repository into one searchable, filterable index - sourced from the people who build and ship with Claude Code daily.
Quick wins
- Always start in plan mode and write a phase-wise, testable plan before executing.
- Keep CLAUDE.md under ~200 lines and split larger instructions into
.claude/rules/. - Mind the "dumb zone" - aggressively
/compactor/clearbefore context drifts past ~40%. - Use subagents for context management - let the conclusion return, not 20 file reads.
- Rewind, don't correct - double-Esc back to before a failed attempt instead of polluting context.
