diff --git a/tips/assets/boris-1-feb-26/0.png b/tips/assets/boris-26-2-1/0.png similarity index 100% rename from tips/assets/boris-1-feb-26/0.png rename to tips/assets/boris-26-2-1/0.png diff --git a/tips/assets/boris-1-feb-26/1.png b/tips/assets/boris-26-2-1/1.png similarity index 100% rename from tips/assets/boris-1-feb-26/1.png rename to tips/assets/boris-26-2-1/1.png diff --git a/tips/assets/boris-1-feb-26/10.png b/tips/assets/boris-26-2-1/10.png similarity index 100% rename from tips/assets/boris-1-feb-26/10.png rename to tips/assets/boris-26-2-1/10.png diff --git a/tips/assets/boris-1-feb-26/2.png b/tips/assets/boris-26-2-1/2.png similarity index 100% rename from tips/assets/boris-1-feb-26/2.png rename to tips/assets/boris-26-2-1/2.png diff --git a/tips/assets/boris-1-feb-26/3.png b/tips/assets/boris-26-2-1/3.png similarity index 100% rename from tips/assets/boris-1-feb-26/3.png rename to tips/assets/boris-26-2-1/3.png diff --git a/tips/assets/boris-1-feb-26/4.png b/tips/assets/boris-26-2-1/4.png similarity index 100% rename from tips/assets/boris-1-feb-26/4.png rename to tips/assets/boris-26-2-1/4.png diff --git a/tips/assets/boris-1-feb-26/5.png b/tips/assets/boris-26-2-1/5.png similarity index 100% rename from tips/assets/boris-1-feb-26/5.png rename to tips/assets/boris-26-2-1/5.png diff --git a/tips/assets/boris-1-feb-26/6.png b/tips/assets/boris-26-2-1/6.png similarity index 100% rename from tips/assets/boris-1-feb-26/6.png rename to tips/assets/boris-26-2-1/6.png diff --git a/tips/assets/boris-1-feb-26/7.png b/tips/assets/boris-26-2-1/7.png similarity index 100% rename from tips/assets/boris-1-feb-26/7.png rename to tips/assets/boris-26-2-1/7.png diff --git a/tips/assets/boris-1-feb-26/8.png b/tips/assets/boris-26-2-1/8.png similarity index 100% rename from tips/assets/boris-1-feb-26/8.png rename to tips/assets/boris-26-2-1/8.png diff --git a/tips/assets/boris-1-feb-26/9.png b/tips/assets/boris-26-2-1/9.png similarity index 100% rename from tips/assets/boris-1-feb-26/9.png rename to tips/assets/boris-26-2-1/9.png diff --git a/tips/claude-boris-10-tips-01-feb-26.md b/tips/claude-boris-10-tips-01-feb-26.md index 2e2ceab..0bf5f6d 100644 --- a/tips/claude-boris-10-tips-01-feb-26.md +++ b/tips/claude-boris-10-tips-01-feb-26.md @@ -15,7 +15,7 @@ A summary of team tips shared by Boris Cherny ([@bcherny](https://x.com/bcherny) Boris shared tips for using Claude Code sourced directly from the Claude Code team. The way the team uses Claude is different than how Boris uses it personally. Remember: there is no one right way to use Claude Code — everyone's setup is different. You should experiment to see what works for you! -Boris Cherny intro tweet +Boris Cherny intro tweet --- @@ -27,7 +27,7 @@ Some people also name their worktrees and set up shell aliases (`2a`, `2b`, `2c` See: [Worktrees Docs](https://code.claude.com/docs/en/common...) -Do more in parallel +Do more in parallel --- @@ -39,7 +39,7 @@ One person has one Claude write the plan, then they spin up a second Claude to r Another says the moment something goes sideways, they switch back to plan mode and re-plan. Don't keep pushing. They also explicitly tell Claude to enter plan mode for verification steps, not just for the build. -Start every complex task in plan mode +Start every complex task in plan mode --- @@ -51,7 +51,7 @@ Ruthlessly edit your `CLAUDE.md` over time. Keep iterating until Claude's mistak One engineer tells Claude to maintain a notes directory for every task/project, updated after every PR. They then point `CLAUDE.md` at it. -Invest in your CLAUDE.md +Invest in your CLAUDE.md --- @@ -66,7 +66,7 @@ Reuse across every project. Tips from the team: See: [Extend Claude with Skills — Claude Code Docs](https://code.claude.com/docs/en/skills) -Create your own skills +Create your own skills --- @@ -80,7 +80,7 @@ Or, just say "Go fix the failing CI tests." Don't micromanage how. Point Claude at docker logs to troubleshoot distributed systems — it's surprisingly capable at this. -Claude fixes most bugs by itself +Claude fixes most bugs by itself --- @@ -92,7 +92,7 @@ b. **After a mediocre fix,** say: "Knowing everything you know now, scrap this a c. **Write detailed specs** and reduce ambiguity before handing work off. The more specific you are, the better the output. -Level up your prompting +Level up your prompting --- @@ -106,7 +106,7 @@ Use voice dictation. You speak 3x faster than you type, and your prompts get way See: [Terminal Setup Docs](https://code.claude.com/docs/en/termin...) -Terminal and environment setup +Terminal and environment setup --- @@ -118,7 +118,7 @@ b. Offload individual tasks to subagents to keep your main agent's context windo c. Route permission requests to Opus 4.5 via a hook — let it scan for attacks and auto-approve the safe ones. See: [Hooks Docs](https://code.claude.com/docs/en/hooks#...) -Use subagents +Use subagents --- @@ -128,7 +128,7 @@ Ask Claude Code to use the "bq" CLI to pull and analyze metrics on the fly. The This works for any database that has a CLI, MCP, or API. -Use Claude for data and analytics +Use Claude for data and analytics --- @@ -144,7 +144,7 @@ c. Ask Claude to draw ASCII diagrams of new protocols and codebases to help you d. Build a spaced-repetition learning skill: you explain your understanding, Claude asks follow-ups to fill gaps, stores the result. -Learning with Claude +Learning with Claude ---