Thread Truncated (Cap Enforced)
Only the first 20 tweets are unrolled into slides to ensure reliable PDF exporting and high server performance.
Canvas & Ratio
Choose your destination platform format
Layout Template
Choose a content structure for your slides
Preset Themes
Typography & Sizing
Brand Kit Customization
AGENCYConfigure brand assets for headers & footers
Outro Slide CTA
Customize your closing call-to-action slide
Background Pattern
Build Your Carousel
Drag and drop any post card below onto a slide, or use the quick buttons to insert content/images instantly!
Working with Claude Fable 5 keeps re-teaching me an old lesson: the map is not the territory.
The map, a representation of the work to be done, is my prompts and skills and context, itās what I give Claude. The territory is where the work needs to happen, the codebase, the real world, its actual constraints.
The difference between the map and the territory is what I call <i>unknowns</i>. When Claude runs into an unknown, it needs to make a decision based on its best guess of what I want. The more work being done, the more unknowns Claude might run into
Fable is the first model where I find the quality of the work is bottlenecked by my ability to clarify itsĀ unknowns.
Importantly, just planning ahead isnāt always enough. You can find unknowns deep in implementation, or your unknowns may point you to the fact that you should actually be solving the problem in a different way altogether.
Iāve found that working with Fable is an iterative process of discovering my unknowns before, during, and after implementation.
I've made some <b><a target="_blank" href="https://thariqs.github.io/html-effectiveness/unknowns/" color="blue">example artifacts for finding unknowns here</a></b><a target="_blank" href="https://thariqs.github.io/html-effectiveness/unknowns/" color="blue">,</a> but be sure to come back to build the intuition for when to use them.
## Knowing your unknowns
What are your unknowns? When I come to Claude with a problem I tend to break itĀ down in 4Ā ways:
ā¢ <b>Known Knowns:</b>Ā This is essentially what is in my prompt. What do I tell the agent that I want?
ā¢ <b>Known Unknowns:</b>Ā What haven't I figured out yet, but Iām aware that I havenāt?
ā¢ <b>Unknown Knowns:</b>Ā What's so obvious Iād never write it down, but would recognize it if I saw it?
ā¢ <b>Unknown Unknowns:</b>Ā What haven't I considered at all? What knowledge am I not aware of? Do I know how good something can be?
The best agentic coders are good have relatively few unknowns. Watching someone like <a target="_blank" href="https://www.google.com/url?q=https://www.linkedin.com/in/bcherny&sa=D&source=editors&ust=1783101769343560&usg=AOvVaw0NSN4RLOEaJ_k7bIWfat2t" color="blue">Boris</a>Ā or <a target="_blank" href="https://www.google.com/url?q=https://www.linkedin.com/in/jarred-sumner-a8772425&sa=D&source=editors&ust=1783101769343738&usg=AOvVaw1jFeuVIbBffAC5464Tk_TD" color="blue">Jarred</a>Ā prompt, it is obvious to me that they know what they want in-detail. They are deeply in-sync with both the codebase and the model behaviors.
But they also assume unknowns. In many ways, reducing and planning for your unknownsĀ is the <b>skill</b>Ā of agentic coding. But luckily, this is a skill you can improve at, by working with Claude.
## Help Claude help you
Instructing Claude is a delicate balance. If you are too specific, Claude will follow your instructions even when a pivot may be more appropriate. If you are too vague, Claude will often make choices and assumptions based on industry best practices that may not be a fit for your task.