Great read.

• Claude Fable 5 makes the human the bottleneck, because the model now exposes every missing decision.

• Claude is getting good enough that weak prompts now fail less from syntax and more from missing context.

• A prompt gives the model a map, but the repository contains the roads, detours, weird legacy choices, and invisible tradeoffs. Every unstated assumption becomes a fork where the model has to choose for you.

• That choice may be reasonable, clean, and still wrong. The best move, then, is to spend less time pretending your spec is complete and more time building tools that expose its gaps.

• Great agentic coding is not writing perfect prompts, but shrinking the gap between intent and reality.

• Ask Claude to find your blind spots before coding, especially inside unfamiliar code or unfamiliar domains.

• Prototype first when taste is hard to explain, because 4 rough versions beat 1 polished mistake.

• Make Claude interview you before building, starting with answers that could change the architecture.

• Keep implementation notes during the build, because every deviation reveals a hidden assumption.

• Do not merge until Claude can quiz you and you fully understand what changed.