- tweet 1 · tweet 2 · tweet 3 + Boris Cherny on X (tweet 1 · tweet 2 · tweet 3)
- tweet 1 · tweet 2 · tweet 3
+ Boris Cherny on X (tweet 1 · tweet 2 · tweet 3)
@@ -73,36 +81,38 @@ See [orchestration-workflow](orchestration-workflow/orchestration-workflow.md) f
■ **Workflows**
-- Claude.md should not exceed 150+ lines. (still not 100% guaranteed)
-- use commands for your workflows instead of agents
-- have feature specific subagents (extra context) with skills (progressive disclosure) instead of general qa, backend engineer.
-- /memory, /rules, constitution.md does not guarantee anything
-- do manual /compact at max 50%
-- always start with plan mode
-- subtasks should be so small that it can be completed in less than 50% context
+- [CLAUDE.md](https://code.claude.com/docs/en/memory) should not exceed 150+ lines. (still not 100% guaranteed)
+- use [commands](https://code.claude.com/docs/en/skills) for your workflows instead of [agents](https://code.claude.com/docs/en/sub-agents)
+- have feature specific [subagents](https://code.claude.com/docs/en/sub-agents) (extra context) with [skills](https://code.claude.com/docs/en/skills) (progressive disclosure) instead of general qa, backend engineer.
+- [/memory](https://code.claude.com/docs/en/memory), [/rules](https://code.claude.com/docs/en/memory#organize-rules-with-clauderules), constitution.md does not guarantee anything
+- avoid agent dumb zone, do manual /compact at max 50%
+- always start with [plan mode](https://code.claude.com/docs/en/common-workflows)
- vanilla cc is better than any workflows with smaller tasks
- commit often, as soon as task is completed, commit.
+- [agent teams](https://code.claude.com/docs/en/agent-teams) and [git worktrees](https://x.com/bcherny/status/2025007393290272904) for parallel development
+- use [Ralph Wiggum plugin](https://github.com/shanraisshan/novel-llm-26) for long-running autonomous tasks
■ **Utilities**
-- iTerm terminal instead of IDE (crash issue)
-- Wispr Flow for voice prompting (10x productivity)
-- claude-code-voice-hooks for claude feedback
-- status line for context awareness and fast compacting
-- git worktrees for parallel development
-- /permissions with wildcard syntax (`Bash(npm run *)`, `Edit(/docs/**)`) instead of dangerously-skip-permissions
-- /sandbox to reduce permission prompts with file and network isolation
-- output styles: use Explanatory when learning a new codebase, Learning for coaching
-- /keybindings to remap any key, settings live reload
+- [iTerm](https://iterm2.com/) terminal instead of IDE (crash issue)
+- [Wispr Flow](https://wisprflow.ai) for voice prompting (10x productivity)
+- [claude-code-voice-hooks](https://github.com/shanraisshan/claude-code-voice-hooks) for claude feedback
+- [status line](https://github.com/shanraisshan/claude-code-status-line) for context awareness and fast compacting
+- [/permissions](https://code.claude.com/docs/en/permissions) with wildcard syntax (`Bash(npm run *)`, `Edit(/docs/**)`) instead of dangerously-skip-permissions
+- [/sandbox](https://code.claude.com/docs/en/sandboxing) to reduce permission prompts with file and network isolation
+- [output styles](https://code.claude.com/docs/en/output-styles): use Explanatory when learning a new codebase, Learning for coaching
-■ **Debugging**
-- /doctor
+■ **Debugging**
+- [/doctor](https://code.claude.com/docs/en/cli-reference)
- always ask claude to run the terminal (you want to see logs of) as a background task for better debugging
-- use mcp (claude in chrome, playwright, chrome dev tool) to let claude see chrome console logs on its own
+- use mcp ([Claude in Chrome](https://code.claude.com/docs/en/chrome), [Playwright](https://github.com/microsoft/playwright-mcp), [Chrome DevTools](https://developer.chrome.com/blog/chrome-devtools-mcp)) to let claude see chrome console logs on its own
- provide screenshots of the issue
-- [Feb 2026 - 12 Tips](reports/claude-boris-tips-feb-26.md) ([Reddit thread](https://www.reddit.com/r/ClaudeAI/comments/1r2m8ma/12_claude_code_tips_from_creator_of_claude_code/))
+- [Git Worktrees - 5 ways how boris is using | 21 Feb 2026]() ● [Tweet](https://x.com/bcherny/status/2025007393290272904)
+- [Boris setup - 5 tips | 03/Jan/26]() ● [Tweet](https://x.com/bcherny/status/2007179832300581177)
+- [10 tips for using claude code by team itself | 01/Feb/26]() ● [Tweet](https://x.com/bcherny/status/2017742741636321619)
+- [12 ways how people are customizing their claudes | 12/Feb/26](reports/claude-boris-tips-feb-26.md) ● [Tweet](https://x.com/bcherny/status/2021699851499798911)
## REPORTS
@@ -113,6 +123,5 @@ See [orchestration-workflow](orchestration-workflow/orchestration-workflow.md) f
| [Global vs Project Settings](reports/claude-global-vs-project-settings.md) | Which features are global-only (`~/.claude/`) vs dual-scope, including Tasks and Agent Teams |
| [Skills Discovery in Monorepos](reports/claude-skills-for-larger-mono-repos.md) | How skills are discovered and loaded in large monorepo projects |
| [Agent Memory Frontmatter](reports/claude-agent-memory.md) | Persistent memory scopes (`user`, `project`, `local`) for subagents — enabling agents to learn across sessions |
-| [Boris Cherny's 12 Customization Tips](reports/claude-boris-tips-feb-26.md) | 12 ways to customize Claude Code — from terminal config to plugins, agents, hooks, and output styles |
| [Advanced Tool Use Patterns](reports/claude-advanced-tool-use.md) | Programmatic Tool Calling (PTC), Tool Search, and Tool Use Examples |
| [Usage, Rate Limits & Extra Usage](reports/claude-usage-and-rate-limits.md) | Usage commands (`/usage`, `/extra-usage`, `/cost`), rate limits, and pay-as-you-go overflow billing |