# cherny-claude-code-10-tips-team-x-2026-02-01

## Veille

Claude Code usage tips from the Anthropic team - 10 productivity tricks

## Titre Article

Claude Code Tips from the Claude Code Team

## Date

2026-02-01

## URL

https://x.com/bcherny/status/2017742741636321619?s=20

## Keywords

Claude Code, git worktrees, plan mode, CLAUDE.md, skills, slash commands, subagents, BigQuery, Ghostty, parallelism, developer productivity, MCP Slack, CI/CD

## Authors

Boris Cherny (créateur de Claude Code)

## Ton

**Profile**: Insider perspective (product creator), informal and direct register, intermediate to advanced technical level

**Description**: Boris Cherny adopts a tone of authentic peer-to-peer sharing, presenting not his own way of using Claude Code but his team's. The style is pragmatic, geared toward concrete tips with a clear numbered structure. Authority comes directly from the source (the team that built the tool), lending rare legitimacy. The text avoids marketing jargon in favor of actionable advice. The target audience consists of developers already using Claude Code who are looking to optimize their workflow.

## Pense-betes

- **Git worktrees = major productivity unlock**: 3-5 worktrees in parallel, each with its own Claude session. Native support in Claude Desktop app by @amorriscode
- **Systematic plan mode**: Always start complex tasks in plan mode. Investing in the plan enables a "1-shot" implementation
- **Double Claude for plans**: One Claude writes the plan, a second reviews it as a "staff engineer"
- **Evolving CLAUDE.md**: After every correction, say "Update your CLAUDE.md so you don't make that mistake again." Claude excels at writing its own rules
- **Skills and slash commands**: If an action is repeated more than once a day → skill. Examples: /techdebt, Slack/GDrive/Asana/GitHub sync
- **Simplified bug fixing**: Enable Slack MCP, paste a bug thread, say "fix." Or simply "Go fix the failing CI tests"
- **Ghostty recommended**: Synchronized rendering, 24-bit colors, unicode support
- **Subagents for heavy compute**: Add "use subagents" to complex requests for more compute power
- **BigQuery via CLI**: The team hasn't written SQL in 6+ months, everything goes through Claude + the bq CLI
- **Voice dictation**: Speaking 3x faster than typing, more detailed prompts (fn x2 on macOS)
- **Learning mode**: Enable "Explanatory" or "Learning" style in /config to understand the "why"

## RésuméDe400mots

Boris Cherny, creator of Claude Code, shares ten usage tips drawn directly from the Claude Code team at Anthropic. He notes upfront that there is no single method and encourages experimentation.

**Parallelism via git worktrees**: The team's number-one tip is to use 3 to 5 git worktrees simultaneously, each running its own Claude session. This approach is identified as the biggest productivity gain. Some team members create shell aliases (za, zb, zc) to navigate quickly between worktrees, while others keep a dedicated worktree for log analysis and BigQuery.

**Systematic plan mode**: For any complex task, the team recommends starting in plan mode and investing the effort needed so Claude can implement it in a single pass. One practice is to use one Claude to draft the plan, then a second to review it with the eye of a "staff engineer." As soon as an implementation goes off track, immediately return to plan mode rather than pushing through.

**CLAUDE.md as evolving memory**: After every correction, ask Claude to update its CLAUDE.md file so the mistake isn't repeated. Claude turns out to be remarkably effective at writing its own rules. One engineer has Claude maintain a directory of notes per task/project, updated after every PR.

**Skills and custom commands**: Any action repeated more than once a day deserves to become a skill or slash command. Examples cited: /techdebt to identify duplicated code, a command that syncs 7 days of Slack, GDrive, Asana, and GitHub into a single context, or analytics-engineer-style agents for dbt.

**Autonomous bug fixing**: Enable the Slack MCP, paste a bug thread, and simply say "fix." Or ask "Go fix the failing CI tests" without micromanaging. Claude also handles troubleshooting via docker logs on distributed systems.

**Advanced prompting techniques**: Ask Claude to act as a reviewer ("Grill me on these changes"), to prove the code works via a diff between branches, or to redo a mediocre implementation with "implement the elegant solution."

**Optimized terminal environment**: The team favors Ghostty for its synchronized rendering and unicode support. They use /statusline to display context and the git branch, tabs colored by task, and voice dictation (fn x2 on macOS) for prompts 3x faster.

**Subagents and analytics**: Add "use subagents" to complex requests to delegate compute. The team uses Claude with the BigQuery CLI (bq) for all their analytics queries, and hasn't written SQL by hand in over six months.

**Continuous learning**: Enable the "Explanatory" or "Learning" style in /config, generate HTML presentations or ASCII diagrams to understand code, and create a spaced-repetition skill to consolidate learning.

## GrapheDeConnaissance

- Boris Cherny —a_créé→ Claude Code (TECHNOLOGIE, 0.99)
- Boris Cherny —publie→ conseils équipe Claude Code (DOCUMENT, 0.98)
- Anthropic —a_créé→ Claude Code (TECHNOLOGIE, 0.99)
- Claude Code —utilise→ git worktrees (TECHNOLOGIE, 0.97)
- amorriscode —a_créé→ git worktrees (TECHNOLOGIE, 0.95)
- Claude Desktop app —utilise→ git worktrees (TECHNOLOGIE, 0.95)
- Boris Cherny —recommande→ Plan mode (METHODOLOGIE, 0.96)
- Plan mode —améliore→ qualité implémentation (CONCEPT, 0.9)
- CLAUDE.md —est_instance_de→ mémoire évolutive agent (CONCEPT, 0.93)
- Claude Code —utilise→ slash commands (TECHNOLOGIE, 0.95)
- Claude Code —utilise→ Slack MCP (TECHNOLOGIE, 0.92)
- Claude Code —utilise→ BigQuery (TECHNOLOGIE, 0.94)
- Claude Code —utilise→ subagents (TECHNOLOGIE, 0.95)
- équipe produit —recommande→ Ghostty (TECHNOLOGIE, 0.88)
- Opus 4.5 —s_applique_à→ subagents (CONCEPT, 0.85)

---
Canonical: https://www.thekb.eu/en/fiches/cherny-claude-code-10-tips-team-x-2026-02-01/