"We trace everything" is an intention, not a guarantee: one new code path is enough to open a hole nobody sees. What holds the rule is a test that freezes the inventory of call sites — plus two traps that cost me time.
I kept editing the system prompt, kept re-running, and nothing moved. The culprit wasn't a cache: the graph is built once at startup. Three lifetimes coexist inside an agent, and knowing which one applies changes the feedback loop.
Ask an image model for an App Store screenshot and you get a beautiful visual with an unreadable headline. I inverted the order: a script draws the text, and the model isn't allowed near it. Plus the bit of arithmetic that cost me a full set of screenshots.
Once you delegate to agents, you always have two or three branches in flight. A plain `git checkout` breaks everything: stash, Docker stack restart, ports fighting each other. Here's the layout that unblocked me — and what it actually costs.
Perplexity is pulling back from MCP internally, and their reasons are real. But token bloat and weak permissions are a wiring problem, not a protocol one. Here's a POC that exposes my tools once and grants each agent only its slice.
Screenshots are the #1 conversion lever on the store — and a pain to produce. Here's how a Claude skill + Nano Banana Pro got me a full, consistent, honest set in one afternoon.
How I use Claude Skills to brainstorm 10 SaaS ideas scored out of 100, in 15 minutes — with a real run on my local niche, Réunion Island.
Going from Claude that codes to Claude that disciplines itself. SessionStart to bootstrap the repo, PreToolUse to block sketchy commands, Stop to notify you when a task ends. Four concrete hooks running silently in my repos.
A Rust CLI proxy that sits between Claude Code and your shell commands. It compresses verbose output (git status, ls, jest...) before it ever reaches the context window. One command to install, instant payoff.