Route · Available
Code Like Me
How I program with Claude Code every day: the status line, hooks, the reviewer, model routing, handing off between sessions and thresholds.
Part of the Claude Code Ecosystem →
Goal
Read your own status line, decide which model each task uses, and let hooks enforce the rules that today depend on remembering them.
For: Anyone using Claude Code who wants to spend less, lose less context and know the state of a session at a glance.
Before you start
- Claude Code installed
- Bash (Git Bash on Windows)
- jq
Lessons
0 of 8 done in this browser
- 01
Look at the two lines of the status bar and know, at a glance, four things: how much context you have left before the session degrades, whether the cache is still warm, whether your work is safe (commit, push, HANDOFF)…
- 02
Before picking a model, ask whether one is needed at all. Deterministic, repeatable work goes to code that runs without a model (Python/SQL/shell).
- 03
Source: home/.claude/rules/context-hygiene.md, home/.claude/rules/thresholds.json, home/.claude/settings.json, home/.claude/statusline.sh, home/.claude/MANUAL.md ch. 2, home/.claude/CLAUDE.md §Status line.
- 04
Fixed sections, exact headings:
- 05
Five scripts under home/.claude/hooks/, wired in home/.claude/settings.json. Every hook always exits 0 — a hook must never be the reason a session, a compaction, or the tool it watches fails.
- 06
Source: home/.claude/rules/thresholds.json (full file), docs/statusline-internals.md §Thresholds, home/.claude/statusline.sh, home/.claude/hooks/session-drift-warn.sh, tests/statuslinetest.sh.
- 07
A model reviewing its own output shows measurable self-preference bias; a different model that is at least as strong does not.
- 08
Source: home/.claude/MANUAL.md (index); home/.claude/skills/manual/SKILL.md.
Mini project
Install the kit and read your status line
Clone claude-kit, install the configuration into your ~/.claude with the sync script, and explain, segment by segment, what your own status line tells you in a real session.
Open it →