Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Claude Fable 5 early tester: "If you're using Fable 5 for everything, that is almost 100% overkill." in 10 minutes, Nate breaks down the six prompting habits that actually get the most out of it here's what he covers: > always give the why, not just the what >... negative prompting: tell it exactly what not to do > baking verification loops into every agent and skill file > the one prompt type that silently downgrades you to a weaker model most people are just throwing longer prompts at a more expensive model the ones getting real results changed how they prompt, not how much they spend an article on how to build a fully automated AI company with Claude Fable 5 👇show more

rewind

4,607 subscribers

11,868 views • 3 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Anthropic finally published the prompting playbook for every Claude model. > Prompting Claude Sonnet 5. > Prompting Claude Opus 4.8. > Prompting Claude Opus 5. > Prompting Claude Fable 5. After reading it, one thing is clear. Almost nobody is getting the most out of Claude. It shows exactly how each model should be prompted instead of relying on guesswork. If Claude is in your workflow, bookmark this.

Anthropic finally published the prompting playbook for every Claude model. > Prompting Claude Sonnet 5. > Prompting Claude Opus 4.8. > Prompting Claude Opus 5. > Prompting Claude Fable 5. After reading it, one thing is clear. Almost nobody is getting the most out of Claude. It shows exactly how each model should be prompted instead of relying on guesswork. If Claude is in your workflow, bookmark this.

shmidt

123,935 views • 2 months ago

Claude Fable 5 built a 3D product website with Claude Code Generate an image of a product with the Magnific MCP, and convert it into a 3D model. Download that model and give it to Fable 5 to develop an interactive page with. Here's the final result + prompts:

Claude Fable 5 built a 3D product website with Claude Code Generate an image of a product with the Magnific MCP, and convert it into a 3D model. Download that model and give it to Fable 5 to develop an interactive page with. Here's the final result + prompts:

Jerrod Lew

33,687 views • 3 months ago

Turns out Fable 5 isn't expensive, you're just using it wrong. The Claude team just showed how they run it Use Fable 5 as the brain, Sonnet or Opus as the hands. Fable makes one or two calls to set direction, other model does the rest of the work cheap. Near-Fable results at half the cost, from their own benchmarks below Same logic as a good manager: your best person steers the decisions, not every task

Turns out Fable 5 isn't expensive, you're just using it wrong. The Claude team just showed how they run it Use Fable 5 as the brain, Sonnet or Opus as the hands. Fable makes one or two calls to set direction, other model does the rest of the work cheap. Near-Fable results at half the cost, from their own benchmarks below Same logic as a good manager: your best person steers the decisions, not every task

Yarchi

46,494 views • 2 months ago

Claude Code creator, Boris Cherny: "I'm not prompting my agents anymore. I'm building Loops and Graphs that do it for me." In 10 minutes he explains how they do agentic engineering at Anthropic, and why they stopped prompting a long time ago. The missing piece most people skip: you don't prompt agents to work. You build Loops and Graphs that prompt them for you. Watch it, then read the full guide on Loops and Graphs below

Claude Code creator, Boris Cherny: "I'm not prompting my agents anymore. I'm building Loops and Graphs that do it for me." In 10 minutes he explains how they do agentic engineering at Anthropic, and why they stopped prompting a long time ago. The missing piece most people skip: you don't prompt agents to work. You build Loops and Graphs that prompt them for you. Watch it, then read the full guide on Loops and Graphs below

Mahax

28,776 views • 1 month ago

Boris Cherny, creator of Claude Code: "Opus 5 does in a day what used to take your team a month. Most people will keep using it wrong." In 12 minutes he explains why Opus 5 needs less prompting than any model before, and why your old detailed prompts now work against you. Watch it, then read the article below on how to prompt Opus 5 👇

Boris Cherny, creator of Claude Code: "Opus 5 does in a day what used to take your team a month. Most people will keep using it wrong." In 12 minutes he explains why Opus 5 needs less prompting than any model before, and why your old detailed prompts now work against you. Watch it, then read the article below on how to prompt Opus 5 👇

Rahul

304,668 views • 2 months ago

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,683 views • 2 months ago

An asian guy just found a way to use Fable 5 forever, even though Anthropic is going to make it access-limited after 12th July. He used Opus 4.8 to host the operating manual of fable 5 with just one single prompt. Access to the best model is never guaranteed. It disappeared once already this year. But you can use it forever. Here's how: 1. Extract the operating manual of Fable 5 2. Create an .md file and save it on your device 3. Create a new project "Fable 5 Brain" in Claude 4. Paste the instructions/ .md file straight into it 5. Run a pressure test to verify Save and bookmark this no matter what:

An asian guy just found a way to use Fable 5 forever, even though Anthropic is going to make it access-limited after 12th July. He used Opus 4.8 to host the operating manual of fable 5 with just one single prompt. Access to the best model is never guaranteed. It disappeared once already this year. But you can use it forever. Here's how: 1. Extract the operating manual of Fable 5 2. Create an .md file and save it on your device 3. Create a new project "Fable 5 Brain" in Claude 4. Paste the instructions/ .md file straight into it 5. Run a pressure test to verify Save and bookmark this no matter what:

Aria Westcott

380,226 views • 2 months ago

A lot of people shat on GPT-5 when it came out All of those people are wrong. GPT-5 is actually insanely good. It just requires a different style of prompting than any other model If you prompt it correctly, it's the best AI model out there Here's exactly how to do that:

A lot of people shat on GPT-5 when it came out All of those people are wrong. GPT-5 is actually insanely good. It just requires a different style of prompting than any other model If you prompt it correctly, it's the best AI model out there Here's exactly how to do that:

Alex Finn

19,333 views • 1 year ago

Anthropic team: "Most people are prompting Claude wrong" They dropped a 24-minute workshop on how Claude prompts are actually built Free From the people who built the model There are 6 elements in a real Claude prompt Most people use 1 That is why their outputs feel generic Better wording is not enough Claude rewards structure, context, examples, constraints, and feedback I watched it twice Then built a Claude Skill that applies all 6 automatically You write normally The skill structures the prompt before Claude sees it Bookmark and watch this Then save the setup below

Anthropic team: "Most people are prompting Claude wrong" They dropped a 24-minute workshop on how Claude prompts are actually built Free From the people who built the model There are 6 elements in a real Claude prompt Most people use 1 That is why their outputs feel generic Better wording is not enough Claude rewards structure, context, examples, constraints, and feedback I watched it twice Then built a Claude Skill that applies all 6 automatically You write normally The skill structures the prompt before Claude sees it Bookmark and watch this Then save the setup below

rari

15,655 views • 3 months ago

Boris Cherny, the creator of Claude Code, just explained why the features most users never find are the ones that matter most in this podcast he breaks down not just how to use Claude, but what it all means for the next few years: > the right way to give Claude context before it starts working > why giving it too much information is just as bad as too little > how Claude Code is already changing how engineers build things > how the people who built Claude actually use it day to day based on this podcast and months of using Claude myself, I put together a guide on everything Claude can do that most people have no idea exists you can find it below

Boris Cherny, the creator of Claude Code, just explained why the features most users never find are the ones that matter most in this podcast he breaks down not just how to use Claude, but what it all means for the next few years: > the right way to give Claude context before it starts working > why giving it too much information is just as bad as too little > how Claude Code is already changing how engineers build things > how the people who built Claude actually use it day to day based on this podcast and months of using Claude myself, I put together a guide on everything Claude can do that most people have no idea exists you can find it below

Anatoli Kopadze

22,540 views • 4 months ago

This is one of the wildest things I have built with AI so far 😱 Asked Claude Fable 5 to create a fully interactive 3D crime investigation board using Three.js and it did it in ONE Prompt. It took one more prompt to give it a polished UI inspired by a reference design that I created with GPT Image. What surprised me most was not how it looked. It was how it worked. Fable built a complete Verlet rope physics system with 46 particles in every thread. It handled gravity, damping, distance constraints and all other features of file upload, text and everything. The threads/ropes even lift naturally with pinned evidence instead of clipping through it. I never asked it to implement any of that. I only described the experience I wanted. Maybe that's how we should work with AI. Instead of writing long long specs, we should explain what we want as an experience and let AI do its thing. Anyway, every day Fable 5 raises the bar for what I think AI can build. More to this Live: Code:

This is one of the wildest things I have built with AI so far 😱 Asked Claude Fable 5 to create a fully interactive 3D crime investigation board using Three.js and it did it in ONE Prompt. It took one more prompt to give it a polished UI inspired by a reference design that I created with GPT Image. What surprised me most was not how it looked. It was how it worked. Fable built a complete Verlet rope physics system with 46 particles in every thread. It handled gravity, damping, distance constraints and all other features of file upload, text and everything. The threads/ropes even lift naturally with pinned evidence instead of clipping through it. I never asked it to implement any of that. I only described the experience I wanted. Maybe that's how we should work with AI. Instead of writing long long specs, we should explain what we want as an experience and let AI do its thing. Anyway, every day Fable 5 raises the bar for what I think AI can build. More to this Live: Code:

The Bugged Dev

105,306 views • 2 months ago

Most people think prompting is just writing better sentences Anthropic shows why that's wrong This 32-minute workshop breaks down how prompts are built for production Not prompt hacks Not "act as" Not another $300 course Actual systems Evals Edge cases Model migration Agent loops Good prompt is not one message It's a workflow the model can follow, test and improve This matters because every new claude opus or sonnet will still reward the same rules Watch the prompting playbook Bookmark it before your next bad ai answer is just a bad setup

Most people think prompting is just writing better sentences Anthropic shows why that's wrong This 32-minute workshop breaks down how prompts are built for production Not prompt hacks Not "act as" Not another $300 course Actual systems Evals Edge cases Model migration Agent loops Good prompt is not one message It's a workflow the model can follow, test and improve This matters because every new claude opus or sonnet will still reward the same rules Watch the prompting playbook Bookmark it before your next bad ai answer is just a bad setup

rari

391,493 views • 4 months ago

Anthropic Engineer: "Fable 5 is back, and most people will use it wrong" "You can set up Sonnet 5 and Fable 5 properly in one afternoon and stop overpaying every single day" In 29 minutes, he breaks down each Claude model, why setup matters, and where Fable 5 fits Not every task needs the strongest model Some jobs need speed. Some need reasoning. Some need long agent loops Fable 5 is where the loop work gets interesting: planning, checking, fixing, and running again Most people will upgrade and keep the same messy workflow Power users will route the right task to the right model and save money daily Bookmark and watch this before everyone starts wasting Fable 5

Anthropic Engineer: "Fable 5 is back, and most people will use it wrong" "You can set up Sonnet 5 and Fable 5 properly in one afternoon and stop overpaying every single day" In 29 minutes, he breaks down each Claude model, why setup matters, and where Fable 5 fits Not every task needs the strongest model Some jobs need speed. Some need reasoning. Some need long agent loops Fable 5 is where the loop work gets interesting: planning, checking, fixing, and running again Most people will upgrade and keep the same messy workflow Power users will route the right task to the right model and save money daily Bookmark and watch this before everyone starts wasting Fable 5

rari

20,907 views • 3 months ago

Anthropic just dropped Claude Fable. Most powerful AI ever released to the public. Here's what we did with it in 24 hours: Asked it to map BTC's key support and resistance on the daily chart. It drew them itself. Live. Inside TradingView in 30 seconds. Old way: - Stare at the chart for an hour - Draw, second-guess, redraw - Still not sure if you got it right New way: - Open Claude Fable - Give it one prompt - Watch it happen in real time The game just changed. Most people haven't noticed yet. Learn more:

Anthropic just dropped Claude Fable. Most powerful AI ever released to the public. Here's what we did with it in 24 hours: Asked it to map BTC's key support and resistance on the daily chart. It drew them itself. Live. Inside TradingView in 30 seconds. Old way: - Stare at the chart for an hour - Draw, second-guess, redraw - Still not sure if you got it right New way: - Open Claude Fable - Give it one prompt - Watch it happen in real time The game just changed. Most people haven't noticed yet. Learn more:

AI Bulls

23,040 views • 3 months ago

Most people are using Fable 5 wrong & overpaying every single day. Anthropic's Head of Labs just showed how to use Fable 5 the right way. He shared the exact workflow they use internally: -Run parallel Claude sessions. -Fable only for planning. -Sonnet for quick questions. -Effort levels for simple work. -Verification loops that catch mistakes before they cost tokens. After this you will run Fable 5 like an Anthropic engineer. Bookmark this or keep burning your tokens.

Most people are using Fable 5 wrong & overpaying every single day. Anthropic's Head of Labs just showed how to use Fable 5 the right way. He shared the exact workflow they use internally: -Run parallel Claude sessions. -Fable only for planning. -Sonnet for quick questions. -Effort levels for simple work. -Verification loops that catch mistakes before they cost tokens. After this you will run Fable 5 like an Anthropic engineer. Bookmark this or keep burning your tokens.

Roan

19,661 views • 3 months ago

this is f**king gold someone just figured out how to run Claude Fable 5 and GPT 5.6 Sol in the same loop gpt-5.6 came out yesterday. fable 5 leaves in 48 hours. this window has never existed before and never will again. here is how to use it: 1. open claude code. install openai's codex plugin 2. type /model. choose fable 5. 3. drop one ROUTING.md in your repo root (full file in comments). 4.paste the prompt (in comments), write what feature you want. boom. save and bookmark this no matter what. it will be the most productive thing you do this weekend

this is f**king gold someone just figured out how to run Claude Fable 5 and GPT 5.6 Sol in the same loop gpt-5.6 came out yesterday. fable 5 leaves in 48 hours. this window has never existed before and never will again. here is how to use it: 1. open claude code. install openai's codex plugin 2. type /model. choose fable 5. 3. drop one ROUTING.md in your repo root (full file in comments). 4.paste the prompt (in comments), write what feature you want. boom. save and bookmark this no matter what. it will be the most productive thing you do this weekend

Avid

141,022 views • 2 months ago

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,292 views • 3 months ago

ANTHROPIC'S PRODUCT CHIEF HAS USED CLAUDE FABLE 5 FOR MONTHS BEFORE ANYONE ELSE. HERE'S WHAT HE LEARNED ABOUT THE MOST POWERFUL MODEL YET Mike Krieger co-founded Instagram and now runs product at Anthropic. He's had Claude Fable 5 for two months before the public, and his takeaway is that it changes how you have to work, not just how much you get done. Here's what stood out, and what to actually do with it 1. It holds the whole project, so stop chopping tasks small. The old habit was breaking work into model-sized pieces and stitching them. Fable keeps the whole thing in context. What to do: stop pre-slicing your prompts into tiny steps. Hand it the full goal and the intent behind it, the way you'd brief a senior engineer, and let it sequence the work itself 2. Delegate big, async, and overnight. He sets it on a hard task at night and wakes to it finished, including the model getting itself unstuck when a service died, scaffolding a workaround, and documenting it. What to do: stop babysitting one prompt at a time. Kick off long jobs and walk away. Run several sessions at once instead of one you watch 3. The skill is planning now, not typing. His day moved to long architecture conversations up front, then execution in chunks. What to do: spend your first prompts planning, not building. Then ask it to output an HTML page or markdown doc of the plan so your team aligns before any code is written. That early alignment is the new leverage 4. Match the effort level to the task. Fable's range is wide, so a heavy reasoning pass on a tiny UI tweak is overkill (and pricey). What to do: dial effort down for small jobs, save the deep thinking for hard ones. And don't use your most expensive model for quick questions, keep a fast model for those 5. Verification is the real bottleneck now. The hard part isn't getting output, it's trusting it. What to do: make every change ship with proof. Have Claude attach a screenshot or video of what it built, so you can see the result instead of reading the diff. Then stand behind the decisions yourself before you merge 6. Cost is per-result, not per-turn. Fable is expensive per call but often one-shots what other models need ten turns to get right. What to do: judge cost by what it takes to finish the task to your satisfaction, not the price of a single message. Give it a real task and see how far it gets before you jump in His bigger point: software engineering isn't over, it's different. The craft moved from writing code to owning intent, taste, and what actually ships. The floor rose so anyone can build, and the ceiling rose so experts go further than before Bookmark this

ANTHROPIC'S PRODUCT CHIEF HAS USED CLAUDE FABLE 5 FOR MONTHS BEFORE ANYONE ELSE. HERE'S WHAT HE LEARNED ABOUT THE MOST POWERFUL MODEL YET Mike Krieger co-founded Instagram and now runs product at Anthropic. He's had Claude Fable 5 for two months before the public, and his takeaway is that it changes how you have to work, not just how much you get done. Here's what stood out, and what to actually do with it 1. It holds the whole project, so stop chopping tasks small. The old habit was breaking work into model-sized pieces and stitching them. Fable keeps the whole thing in context. What to do: stop pre-slicing your prompts into tiny steps. Hand it the full goal and the intent behind it, the way you'd brief a senior engineer, and let it sequence the work itself 2. Delegate big, async, and overnight. He sets it on a hard task at night and wakes to it finished, including the model getting itself unstuck when a service died, scaffolding a workaround, and documenting it. What to do: stop babysitting one prompt at a time. Kick off long jobs and walk away. Run several sessions at once instead of one you watch 3. The skill is planning now, not typing. His day moved to long architecture conversations up front, then execution in chunks. What to do: spend your first prompts planning, not building. Then ask it to output an HTML page or markdown doc of the plan so your team aligns before any code is written. That early alignment is the new leverage 4. Match the effort level to the task. Fable's range is wide, so a heavy reasoning pass on a tiny UI tweak is overkill (and pricey). What to do: dial effort down for small jobs, save the deep thinking for hard ones. And don't use your most expensive model for quick questions, keep a fast model for those 5. Verification is the real bottleneck now. The hard part isn't getting output, it's trusting it. What to do: make every change ship with proof. Have Claude attach a screenshot or video of what it built, so you can see the result instead of reading the diff. Then stand behind the decisions yourself before you merge 6. Cost is per-result, not per-turn. Fable is expensive per call but often one-shots what other models need ten turns to get right. What to do: judge cost by what it takes to finish the task to your satisfaction, not the price of a single message. Give it a real task and see how far it gets before you jump in His bigger point: software engineering isn't over, it's different. The craft moved from writing code to owning intent, taste, and what actually ships. The floor rose so anyone can build, and the ceiling rose so experts go further than before Bookmark this

Yarchi

30,958 views • 3 months ago

The creator of Claude Code deleted his IDE in November 2024. In the last 30 days, 100% of his contributions were written by Claude Code. 259 PRs. His job is not prompting anymore. His job is writing loops that prompt Claude for him. Here is what that progression actually looks like: → stage 1: write code by hand with autocomplete → stage 2: run 5-10 claude sessions in parallel, prompt each one yourself → stage 3: write loops that prompt claude — you become the author, the model becomes a subroutine → the ralph loop (2025): bash one-liner, fixed anchor files, built a programming language for $297 → the 2026 loop: loops supervising loops, scheduling on infrastructure time, git-backed durable state → five building blocks: automations, durable state, validator split, loop orchestration, crash recovery Most developers are still in stage 2, prompting sessions by hand. The ones at stage 3 are writing the loops that do the prompting for them. Read this article to be ahead of the curve! Follow NeilXbt for more AI engineering intelligence that shows you exactly where the leverage moved and what building at that level actually looks like.

The creator of Claude Code deleted his IDE in November 2024. In the last 30 days, 100% of his contributions were written by Claude Code. 259 PRs. His job is not prompting anymore. His job is writing loops that prompt Claude for him. Here is what that progression actually looks like: → stage 1: write code by hand with autocomplete → stage 2: run 5-10 claude sessions in parallel, prompt each one yourself → stage 3: write loops that prompt claude — you become the author, the model becomes a subroutine → the ralph loop (2025): bash one-liner, fixed anchor files, built a programming language for $297 → the 2026 loop: loops supervising loops, scheduling on infrastructure time, git-backed durable state → five building blocks: automations, durable state, validator split, loop orchestration, crash recovery Most developers are still in stage 2, prompting sessions by hand. The ones at stage 3 are writing the loops that do the prompting for them. Read this article to be ahead of the curve! Follow NeilXbt for more AI engineering intelligence that shows you exactly where the leverage moved and what building at that level actually looks like.

NeilXbt

11,556 views • 3 months ago

Anthropic engineer: "Most people are using 10% of what Claude can do. The other 90% is Loops and Graphs." In 30 minutes he explains how Anthropic uses Claude, and why most people never get there. The missing piece most people skip: Claude isn't hard to use, loops and graphs are how you use it well. Watch it, then read what Claude is actually capable of below.

Anthropic engineer: "Most people are using 10% of what Claude can do. The other 90% is Loops and Graphs." In 30 minutes he explains how Anthropic uses Claude, and why most people never get there. The missing piece most people skip: Claude isn't hard to use, loops and graphs are how you use it well. Watch it, then read what Claude is actually capable of below.

Mahax

68,000 views • 1 month ago