diff --git a/tips/assets/boris-3-jan-26/0.png b/tips/assets/boris-26-1-3/0.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/0.png
rename to tips/assets/boris-26-1-3/0.png
diff --git a/tips/assets/boris-3-jan-26/1.png b/tips/assets/boris-26-1-3/1.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/1.png
rename to tips/assets/boris-26-1-3/1.png
diff --git a/tips/assets/boris-3-jan-26/10.png b/tips/assets/boris-26-1-3/10.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/10.png
rename to tips/assets/boris-26-1-3/10.png
diff --git a/tips/assets/boris-3-jan-26/11.png b/tips/assets/boris-26-1-3/11.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/11.png
rename to tips/assets/boris-26-1-3/11.png
diff --git a/tips/assets/boris-3-jan-26/12.png b/tips/assets/boris-26-1-3/12.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/12.png
rename to tips/assets/boris-26-1-3/12.png
diff --git a/tips/assets/boris-3-jan-26/13.png b/tips/assets/boris-26-1-3/13.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/13.png
rename to tips/assets/boris-26-1-3/13.png
diff --git a/tips/assets/boris-3-jan-26/2.png b/tips/assets/boris-26-1-3/2.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/2.png
rename to tips/assets/boris-26-1-3/2.png
diff --git a/tips/assets/boris-3-jan-26/3.png b/tips/assets/boris-26-1-3/3.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/3.png
rename to tips/assets/boris-26-1-3/3.png
diff --git a/tips/assets/boris-3-jan-26/4.png b/tips/assets/boris-26-1-3/4.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/4.png
rename to tips/assets/boris-26-1-3/4.png
diff --git a/tips/assets/boris-3-jan-26/5.png b/tips/assets/boris-26-1-3/5.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/5.png
rename to tips/assets/boris-26-1-3/5.png
diff --git a/tips/assets/boris-3-jan-26/6.png b/tips/assets/boris-26-1-3/6.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/6.png
rename to tips/assets/boris-26-1-3/6.png
diff --git a/tips/assets/boris-3-jan-26/7.png b/tips/assets/boris-26-1-3/7.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/7.png
rename to tips/assets/boris-26-1-3/7.png
diff --git a/tips/assets/boris-3-jan-26/8.png b/tips/assets/boris-26-1-3/8.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/8.png
rename to tips/assets/boris-26-1-3/8.png
diff --git a/tips/assets/boris-3-jan-26/9.png b/tips/assets/boris-26-1-3/9.png
similarity index 100%
rename from tips/assets/boris-3-jan-26/9.png
rename to tips/assets/boris-26-1-3/9.png
diff --git a/tips/claude-boris-13-tips-03-jan-26.md b/tips/claude-boris-13-tips-03-jan-26.md
index 2202065..8b17eb8 100644
--- a/tips/claude-boris-13-tips-03-jan-26.md
+++ b/tips/claude-boris-13-tips-03-jan-26.md
@@ -15,7 +15,7 @@ A summary of setup tips shared by Boris Cherny ([@bcherny](https://x.com/bcherny
Boris shared his personal Claude Code setup, noting it's "surprisingly vanilla" — Claude Code works great out of the box, so he doesn't customize it much. There's no one correct way to use it: the team intentionally builds it so you can use, customize, and hack it however you like. Each person on the Claude Code team uses it very differently.
-
+
---
@@ -25,7 +25,7 @@ Run 5 Claudes in parallel in your terminal. Number your tabs 1–5, and use syst
See: [Terminal Setup Docs](https://code.claude.com/docs/en/terminal)
-
+
---
@@ -33,7 +33,7 @@ See: [Terminal Setup Docs](https://code.claude.com/docs/en/terminal)
Run 5–10 Claudes on claude.ai/code in parallel with your local Claudes. Hand off local sessions to web sessions using `claude.ai/code`, manually kick off sessions in Chrome, and teleport back and forth.
-
+
---
@@ -41,7 +41,7 @@ Run 5–10 Claudes on claude.ai/code in parallel with your local Claudes. Hand o
Use Opus 4.5 with thinking for everything. It's the best coding model Boris has ever used — even though it's bigger and slower than Sonnet, since you have to steer it less and it's better at tool use, it is almost always faster than using a smaller model in the end.
-
+
---
@@ -49,7 +49,7 @@ Use Opus 4.5 with thinking for everything. It's the best coding model Boris has
Share a single `CLAUDE.md` for the repo. Check it into git, and have the whole team contribute multiple times a week. Anytime Claude does something incorrectly, add it to the `CLAUDE.md` so Claude knows not to do it next time.
-
+
---
@@ -57,7 +57,7 @@ Share a single `CLAUDE.md` for the repo. Check it into git, and have the whole t
During code review, tag `@claude` on your coworkers' PRs to add something to the `CLAUDE.md` as part of the PR. Use the Claude Code GitHub action ([install-@hub-action](https://github.com/apps/claude)) for this — it's Boris's version of Compounding Engineering.
-
+
---
@@ -65,7 +65,7 @@ During code review, tag `@claude` on your coworkers' PRs to add something to the
Start most sessions in Plan mode (shift+tab twice). If the goal is to write a Pull Request, use Plan mode and go back and forth with Claude until you like its plan. From there, switch into auto-accept edits mode and Claude can usually 1-shot it. A good plan is really important.
-
+
---
@@ -75,7 +75,7 @@ Use slash commands for every "inner loop" workflow that you do many times a day.
Example: `/commit-push-pr` — Commit, push, and open a PR.
-
+
---
@@ -85,7 +85,7 @@ Use a few subagents regularly: `code-simplifier` simplifies the code after Claud
Subagents live in `.claude/agents/`.
-
+
---
@@ -107,7 +107,7 @@ Use a `PostToolUse` hook to format Claude's code. Claude usually generates well-
]
```
-
+
---
@@ -115,7 +115,7 @@ Use a `PostToolUse` hook to format Claude's code. Claude usually generates well-
Don't use `--dangerously-skip-permissions`. Instead, use `/permissions` to pre-allow common bash commands that you know are safe in your environment, to avoid unnecessary permission prompts. Most of these are checked into `.claude/settings.json` and shared with the team.
-
+
---
@@ -123,7 +123,7 @@ Don't use `--dangerously-skip-permissions`. Instead, use `/permissions` to pre-a
Claude Code uses all your tools. It often searches and posts to Slack (via the MCP server), runs BigQuery queries to answer analytics questions (using `bq` CLI), grabs error logs from Sentry, etc. The Slack MCP configuration is checked into `.mcp.json` and shared with the team.
-
+
---
@@ -131,7 +131,7 @@ Claude Code uses all your tools. It often searches and posts to Slack (via the M
For very long-running tasks, either (a) prompt Claude to verify its work with a background agent when it's done, (b) use an agent Stop hook to do that more deterministically, or (c) use the ralph-wiggum plugin (originally dreamt up by @GeoffreyHuntley).
-
+
---
@@ -141,7 +141,7 @@ Probably the most important thing to get great results out of Claude Code — gi
Claude tests every single change Boris lands.
-
+
---