I Was Hitting Claude's Usage Limit Daily Until This

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: I Was Hitting Claude's Usage Limit Daily Until This
- URL: https://www.youtube.com/watch?v=P_rZ5VR23aE
- Topic: Codex + Claude Workflows
- My current learning frame: Open a real Claude Code project, run /context to capture your baseline, then apply the video's five cuts (tool-search always, MCP-to-CLI migration, skill audit, CLAUDE.md slimming, settings.json tuning) and measure how many percentage points of initial context you reclaim.
- Why this matters: This turns daily usage-limit pain into an operating lesson about context budgets, tool sprawl, and agent setup discipline.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "Couple weeks ago, I was always hitting Claw's usage limits and now I no longer have this problem by fixing a couple steps on how I use Claude every single day. And I was able to do this..."
- 5:52 / Evidence 2: "local machine. And then we just instruct claw code here to use the CLI instead of the MCP. But you can see here that I have ask it to in uninstall the MCP and have it to use..."
- 8:12 / Evidence 3: "file which is our system prompt that we're going to update to use the CLI over the MCP. And then we will manually disconnect those integrations instead of our connectors instead of cloud. And here is the potential..."
- 10:00 / Evidence 4: "expectations everything I need to do for this ticket is all split out inside of the terminal as well. So that the large language model here can also access that through the terminal. And furthermore, I have also..."
- 11:56 / Evidence 5: "that are flagged as overlap. So for example, the project loop here already has this cover. So we don't really need the rough loop. So these are all like some you know outdated skills. There's also the feature..."
- 13:36 / Evidence 6: "and also additional things we check for system prompt to do a full audit. So what I did here is basically try to paste that prompt instead of claw code and have it to basically using super power..."
- 17:05 / Evidence 7: "do is that instead of having to have allow list, we can also have a deny list. And for that, I also had a bunch of things that we can deny. for example, no modules, this folders, build..."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "I Was Hitting Claude's Usage Limit Daily Until This", not a generic Codex + Claude Workflows essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.