practice makes claude perfect
Click on this badge to show the latest best practice
Click on this badge to show implementation in this repo
Click on this badge to see the Command → Agent → Skill orchestration workflow
Boris Cherny on X (tweet 1 · tweet 2 · tweet 3)
| Feature | Location | Description |
|---|---|---|
| Commands | .claude/commands/<name>.md |
Knowledge injected into existing context — simple user-invoked prompt templates for workflow orchestration |
| Subagents | .claude/agents/<name>.md |
Autonomous actor in fresh isolated context — custom tools, permissions, model, memory, and persistent identity |
| Skills | .claude/skills/<name>/SKILL.md |
Knowledge injected into existing context — configurable, preloadable, auto-discoverable, with context forking and progressive disclosure · Official Skills |
| Workflows | .claude/commands/weather-orchestrator.md |
|
| Hooks | .claude/hooks/ |
Deterministic scripts that run outside the agentic loop on specific events |
| MCP Servers | .claude/settings.json, .mcp.json |
Model Context Protocol connections to external tools, databases, and APIs |
| Plugins | distributable packages | Bundles of skills, subagents, hooks, and MCP servers · Marketplaces |
| Settings | .claude/settings.json |
Hierarchical configuration system · Permissions · Model Config · Output Styles · Sandboxing · Keybindings · Fast Mode |
| Status Line | .claude/settings.json |
Customizable status bar showing context usage, model, cost, and session info |
| Memory | CLAUDE.md, .claude/rules/, ~/.claude/rules/, ~/.claude/projects/<project>/memory/ |
Persistent context via CLAUDE.md files and @path imports · Auto Memory · Rules |
| Checkpointing | automatic (git-based) | Automatic tracking of file edits with rewind (Esc Esc or /rewind) and targeted summarization |
| CLI Startup Flags | claude [flags] |
Command-line flags, subcommands, and environment variables for launching Claude Code · Interactive Mode |
| AI Terms | Agentic Engineering · Context Engineering · Vibe Coding |
|
| Best Practices | Official best practices · Prompt Engineering · Extend Claude Code |
| Feature | Location | Description |
|---|---|---|
| /btw | /btw |
Side chain conversations while Claude is working |
Code Review  |
GitHub App (managed) | Multi-agent PR analysis that catches bugs, security vulnerabilities, and regressions · Blog |
| Scheduled Tasks | /loop, cron tools |
Run prompts on a recurring schedule (up to 3 days), set one-time reminders, poll deployments and builds |
| Voice Mode |
/voice |
speak to prompt - /voice to activate |
| Simplify & Batch | /simplify, /batch |
Built-in skills for code quality and bulk operations — simplify refactors for reuse and efficiency, batch runs commands across files |
| Agent Teams |
built-in (env var) | Multiple agents working in parallel on the same codebase with shared task coordination |
| Remote Control | /remote-control, /rc |
Continue local sessions from any device — phone, tablet, or browser · Headless Mode |
| Git Worktrees | built-in | Isolated git branches for parallel development — each agent gets its own working copy |
| Ralph Wiggum Loop | plugin | Autonomous development loop for long-running tasks — iterates until completion |
See orchestration-workflow for implementation details of Command → Agent → Skill pattern.
claude
/weather-orchestrator- Github Speckit · ★ 74k
- obra/superpowers · ★ 72k
- OpenSpec OPSX · ★ 28k
- get-shit-done (GSD) · ★ 25k
- Garry Tan (CEO of Y Combinator) - gstack · ★ 11.5k
- Brian Casel (Creator of Agent OS) - 2026 Workflow · ★ 4k - it's overkill in 2026
- Human Layer RPI - Research Plan Implement · ★ 1.5k
- Andrej Karpathy (Founding Member, OpenAI) Workflow
- Boris Cherny (Creator of Claude Code) - Feb 2026 Workflow
- Peter Steinberger (Creator of OpenClaw) Workflow
■ Prompting (4)
- challenge Claude — "grill me on these changes and don't make a PR until I pass your test." or "prove to me this works" and have Claude diff between main and your branch
- after a mediocre fix — "knowing everything you know now, scrap this and implement the elegant solution"
- Claude fixes most bugs by itself — paste the bug, say "fix", don't micromanage how 👶
- say "use subagents" to throw more compute at a problem — offload tasks to keep your main context clean and focused 👶
■ Planning/Specs (5)
- always start with plan mode
- start with a minimal spec or prompt and ask Claude to interview you using AskUserQuestion tool, then make a new session to execute the spec
- always make a phase-wise gated plan, with each phase having multiple tests (unit, automation, integration)
- spin up a second Claude to review your plan as a staff engineer, or use cross-model for review
- write detailed specs and reduce ambiguity before handing work off — the more specific you are, the better the output
■ Workflows (12)
- CLAUDE.md should target under 200 lines per file. 60 lines in humanlayer (still not 100% guaranteed).
- use multiple CLAUDE.md for monorepos — ancestor + descendant loading
- use .claude/rules/ to split large instructions
- use commands for your workflows instead of sub-agents
- have feature specific sub-agents (extra context) with skills (progressive disclosure) instead of general qa, backend engineer.
- memory.md, constitution.md does not guarantee anything
- avoid agent dumb zone, do manual /compact at max 50%. Use /clear to reset context mid-session if switching to a new task
- vanilla cc is better than any workflows with smaller tasks
- use skills in subfolders for monorepos
- use /model to select model and reasoning, /context to see context usage, /usage to check plan limits, /extra-usage to configure overflow billing, /config to configure settings
- always use thinking mode true (to see reasoning) and Output Style Explanatory (to see detailed output with ★ Insight boxes) in /config for better understanding of Claude's decisions
- use ultrathink keyword in prompts for high effort reasoning
- /rename important sessions (e.g. [TODO - refactor task]) and /resume them later
- use Esc Esc or /rewind to undo when Claude goes off-track instead of trying to fix it in the same context
- commit often — try to commit at least once per hour, as soon as task is completed, commit.
■ Workflows Advanced (6)
- use ASCII diagrams a lot to understand your architecture
- agent teams with tmux and git worktrees for parallel development
- use /loop for recurring monitoring — poll deployments, babysit PRs, check builds (runs up to 3 days)
- use Ralph Wiggum plugin for long-running autonomous tasks
- /permissions with wildcard syntax (Bash(npm run *), Edit(/docs/**)) instead of dangerously-skip-permissions
- /sandbox to reduce permission prompts with file and network isolation
■ Debugging (5)
- make it a habit to take screenshots and share with Claude whenever you are stuck with any issue
- use mcp (Claude in Chrome, Playwright, Chrome DevTools) to let claude see chrome console logs on its own
- always ask claude to run the terminal (you want to see logs of) as a background task for better debugging
- /doctor to diagnose installation, authentication, and configuration issues
- error during compaction can be resolved by using /model to select a 1M token model, then running /compact
- use a cross-model for QA — e.g. Codex for plan and implementation review
■ Utilities (5)
- iTerm/Ghostty /tmux terminals instead of IDE (VS Code/Cursor)
- Wispr Flow for voice prompting (10x productivity)
- claude-code-voice-hooks for claude feedback
- status line for context awareness and fast compacting
- explore settings.json features like Plans Directory, Spinner Verbs for a personalized experience
■ Daily (3)
- update Claude Code daily and start your day by reading the changelog
- follow r/ClaudeAI, r/ClaudeCode
- follow Boris, Thariq, Cat, Lydia, Noah, Anthony, Claude, Alex
- Always use plan mode, give Claude a way to verify, use /code-review (Boris) | 27/Dec/25 ● Tweet
- Ask Claude to interview you using AskUserQuestion tool (Thariq) | 28/Dec/25 ● Tweet
- How I use Claude Code — 13 tips from my surprisingly vanilla setup (Boris) | 03/Jan/26 ● Tweet
- 10 tips for using Claude Code from the team (Boris) | 01/Feb/26 ● Tweet
- 12 ways how people are customizing their claudes (Boris) | 12/Feb/26 ● Tweet
- Git Worktrees - 5 ways how boris is using | 21 Feb 2026 ● Tweet
- Seeing like an Agent - lessons from building Claude Code (Thariq) | 28 Feb 2026 ● Tweet
- AskUserQuestion + ASCII Markdowns (Thariq) | 28 Feb 2026 ● Tweet
- /loop — schedule recurring tasks for up to 3 days (Boris) | 07 Mar 2026 ● Tweet
- Code Review & Test Time Compute (Boris) | 10/Mar/26 ● Tweet
- /btw — side chain conversations while Claude works (Thariq) | 10 Mar 2026 ● Tweet
| Claude | Replaced |
|---|---|
| Code Review | Greptile, CodeRabbit, Devin Review, OpenDiff, Cursor BugBot |
| Voice Mode | Wispr Flow, SuperWhisper |
| Remote Control | OpenClaw |
| Cowork | OpenAI Operator, AgentShadow |
| Tasks | Beads |
| Plan Mode | Agent OS |
| Skills / Plugins | YC AI wrapper startups (reddit) |
If you have answers, do let me know at shanraisshan@gmail.com
Memory & Instructions (4)
- What exactly should you put inside your CLAUDE.md — and what should you leave out?
- If you already have a CLAUDE.md, is a separate constitution.md or rules.md actually needed?
- How often should you update your CLAUDE.md, and how do you know when it's become stale?
- Why does Claude still ignore CLAUDE.md instructions — even when they say MUST in all caps? (reddit)
Agents, Skills & Workflows (6)
- When should you use a command vs an agent vs a skill — and when is vanilla Claude Code just better?
- How often should you update your agents, commands, and workflows as models improve?
- Does giving your subagent a detailed persona improve quality? What does a "perfect persona/prompt" for research/QA subagent look like?
- Should you rely on Claude Code's built-in plan mode — or build your own planning command/agent that enforces your team's workflow?
- If you have a personal skill (e.g., /implement with your coding style), how do you incorporate community skills (e.g., /simplify) without conflicts — and who wins when they disagree?
- Are we there yet? Can we convert an existing codebase into specs, delete the code, and have AI regenerate the exact same code from those specs alone?
Specs & Documentation (3)
- Should every feature in your repo have a spec as a markdown file?
- How often do you need to update specs so they don't become obsolete when a new feature is implemented?
- When implementing a new feature, how do you handle the ripple effect on specs for other features?
✨Trending on Github in March 2026✨
1. Read the repo like a course, learn what commands, agents, skills, and hooks are before trying to use them.
2. Clone this repo and play with the examples, try /weather-orchestrator, listen to the hook sounds, run agent teams, so you can see how things actually work.
3. Go to your own project and ask Claude to suggest what best practices from this repo you should add, give it this repo as a reference so it knows what's possible.
Workflow Description /workflows:best-practice:workflow-concepts Update the README CONCEPTS section with the latest Claude Code features and concepts /workflows:best-practice:workflow-claude-settings Track Claude Code settings report changes and find what needs updating /workflows:best-practice:workflow-claude-subagents Track Claude Code subagents report changes and find what needs updating /workflows:best-practice:workflow-claude-commands Track Claude Code commands report changes and find what needs updating /workflows:best-practice:workflow-claude-skills Track Claude Code skills report changes and find what needs updating
