Claude Clue #26: Running Commands in Your Prompt
If you've spent any time in Claude Code, you've watched it run its own commands all day: reading files, checking git, running tests.
Christopher Moravec
Episode 69 - Wait, what's the difference between a Skill and a Project?
A Skill is a repeatable task. A Project is reference material. Cowork is a Project that can use your computer. They aren't competing products; they are different places to put your context.
Claude Clue #25: Beat the Clock on Your Token Budget
Know when your Claude usage is worth more.
Episode 68 - Don’t Blame the Robot
Most “AI-driven layoffs” aren’t actually driven by AI. The technology is used as a cover for cuts that were already coming for different reasons. No one wants to admit the real reason, so it is easier to blame the robot.
Claude Clue #24: Talk to Your Terminal
If you haven't tried /voice in Claude Code yet, this is your nudge.
Episode 67 - It’s not your prompts
Use AI for thinking (not deciding), fix the system (not the output), and correct without drama.
Claude Clue #23: MCPs Are Just Toolboxes, Not Magic
Claude gets more interesting when you expand what it can touch, and that's where MCPs come in.
Episode 66 - Don’t Tell Claude Who to Be
Tell it what task it's doing and what scope it's working in. The "you are an expert" prompt is mostly cargo cult now; a list of NEVER statements is brittle.
Claude Clue #22: Feed Claude More Than Text
Claude Code can already see images and PDFs—you paste them in with Alt+V on Windows or Ctrl+V on Mac. But it doesn't stop there.
Episode 65 - How to tend a codebase
I double down on the idea that keeping up with AI-generated code looks a lot like gardening: seeds, soil, water, pruning, weeding, and sometimes pulling up a plant.