⚡ Activation

💭 in your head · nothing to type

Picture changing horses mid-river: hold both until the new one is steady under your weight.

What will you move first without letting go of the old horse?

👁 Reflection

💭 in your head · nothing to type

Picture a snake shedding its skin 🐍. It doesn't rip the old layer off in one go. The new one grows underneath, the old one peels away gradually, and for a while both exist at once. That's not weakness — it's the only way to stay covered.

Catch the same idea here. Most common migration mistake: "I'll just uninstall Claude Code, install Hermes, and be more efficient." Doesn't work — the new skin hasn't hardened yet.

Return to the river crossing and two horses: migration moves in steps until the new support survives real work.

What small transfer would show that the new horse can carry your weight?

💡 Concept

The seven-day plan

The template below sets a safe sequence: setup and reproduce a familiar task first, then real work, customization, honest comparison, and a decision. The common mistake is removing the old stack before the new one survives real work; keep the old stack as a fallback.

Migration template

# Migration to [your stack] — 7 days

## Day 1: Setup
- [ ] Install the frontend agent (Claude Code / Codex / Hermes)
- [ ] Bring up LiteLLM gateway locally
- [ ] Get API keys (Cerebras / Gemini / etc.)
- [ ] Make a "hello world" call via curl

## Day 2: Reproduce
- [ ] Pick ONE task you did on the old stack in the past week
- [ ] Redo it on the new stack
- [ ] Note: where it's slower / where it's faster / where it breaks

## Days 3–4: Real work
- [ ] Do one real work task on the new stack
- [ ] Keep the old stack as fallback
- [ ] Don't talk yourself into "the new one is better" — record facts

## Day 5: Customize
- [ ] Set up 1–2 skills / hooks for your workflow
- [ ] Add your CLAUDE.md / AGENTS.md for the new agent
- [ ] LiteLLM: configure the fallback chain

## Day 6: Honest comparison
- [ ] Write down: what's better on the new stack, what's worse
- [ ] Where hybrid makes sense (e.g., Claude Code for design + Codex for refactoring)

## Day 7: Decision
- [ ] Verdict: full migration / hybrid / rollback
- [ ] If rollback — what would the new stack need to make you reconsider?
- [ ] If migration — commit: remove the old stack from active memory

• 🧩 Check yourself: You've chosen a new stack. Which move does the unit call the most common migration mistake?
• 🧩 Check yourself: Why, on the second day of the plan, repeat on the new stack a task you've already solved on the old one?

🛠 Practice

Create my-experiments/u5-migration-plan.md from the template above. Fill in concrete dates.