Claude Fable 5 Is Finally Back: 5 Must-Try Use Cases Before July 7

Hey everyone. So, Claude Fable 5, the world's best AI model, is finally back after being banned by the US government for 18 days. I've been thinking about

Fable a lot, and I want to show you five use cases that I think is actually worth running Fable on. But first, let me catch you guys up. Fable is back, but there's a catch. is only available

through July 7th on your claw subscription and you can't use it anymore after you hit 50% of your weekly usage limits. After that, Fable will

usage limits. After that, Fable will only be available through pay as you go API credits. So, you have to be very

API credits. So, you have to be very very careful about how you use Fable for the next few days. All right, so without further ado, let me talk about five use

cases that I actually think are worth using Fable for. Using Fable to find Fable worthy work, getting life and business advice, making your project

ship ready, planning for the next big thing, and also refactoring a large codebase. Now, I'm going to do a live

codebase. Now, I'm going to do a live walkthrough of all five use cases and show you real fable output. Let's get

going. Okay, so this is my Clockco app and you can select Fable down here. Just

select Fable 5 and of course you can select uh the effort that you want Fable to go with. Now, personally like to stick to high effort because if you go all the way over here to Ultra Code,

your limits are going to run out super fast. All right, so let's start with the

fast. All right, so let's start with the first use case, which is using Fable to find Fable worthy work. Now, Fable is an amazing model and if you use Claw like I

do, it already has memory of all your past interactions. So, here's what I

past interactions. So, here's what I asked Fable. You are Fable 5, the most

asked Fable. You are Fable 5, the most capable AI model available. Look through

my projects and memory. List the top five tasks that require deep thinking that you think are generally worth running by you. Please do not share any confidential information because I'm

making this video and giving a demo. So,

here are Fable's five suggestions, right? Number one is H2 strategy stress

right? Number one is H2 strategy stress test. It found out in my memory that I

test. It found out in my memory that I recently left my job to work on my business full-time and it also found a bunch of skills that I built to get advice on my business. So, it wants to

do a strategy consultation which is exactly the second use case that I'm going to give a live demo of next. All

right. So, let's keep going down the list. So the next one is designing a new

list. So the next one is designing a new offer for a premium tier of the business. And you know this is the exact

business. And you know this is the exact kind of planning work that Fable is good at. It's great at pulling a bunch of

at. It's great at pulling a bunch of contexts from various sources to for example help me figure out here what my flagship creator offer should be. Number

three is content to conversion audit across every platform. So I publish across my newsletter, YouTube shorts and social channels. And I've also set up

social channels. And I've also set up APIs and MCPs for Fable to pull data from each source.

So what Fable can do is pull all this information and figure out where things are working well and where things still need work and give me the data analysis

and insights. LMS are very good at

and insights. LMS are very good at analyzing large corpus of data and Fable can take this to the next level. All

right, real quick on the last two. Mine

your archive into a content road map.

So, I've been publishing for over three years on the newsletter and about a year on the YouTube. And Fable is suggesting that it pulls the transcripts and text for all this stuff and figure out what

themes and things I can repurpose into shorts and other types of content. I

think it's a great idea, but it's probably going to burn my limit in one shot. So, I'm going to stay away from

shot. So, I'm going to stay away from that. And last but not least, uh it

that. And last but not least, uh it wants to audit my personal skill system.

So, I built over 40 AI skills to streamline my creative workflow and help me build. And having Fable clean up

me build. And having Fable clean up these skills is probably a great idea.

So, let's do that at the end of this video.

You can kind of see a common theme across these five examples that Fable suggested. It basically wants to look at

suggested. It basically wants to look at a large corpus of information and data and extract insights from it and take action from it, right? Which is exactly what a state-of-the-art AI model is

really good at. All right, now let's go ahead and explore this one, which is using Fable to stress test my business strategy. So before you ask Fable for

strategy. So before you ask Fable for life and business advice, you have to give it the right context. And as I shared in my previous video, I like to

give it a plan document that has a few different sections. So my overall goal

different sections. So my overall goal for the year, uh some principles I like to use to make decisions like go work, work feels like play, keep the main thing the main thing and so on. uh the

positioning of my business. So who is my target customer? What is my niche? What

target customer? What is my niche? What

is the pain point I'm trying to solve and how do I differentiate and then maybe list a few other players and you know what the differentiation and positioning is and then also have a

session about what gives me energy and what drains my energy and finally some additional context about my life and my financial situation. So that's number

financial situation. So that's number one. give it a high level plan doc and

one. give it a high level plan doc and you might have like different sections for this but these are sections that I like. Now number two is you should

like. Now number two is you should connect fable to a bunch of APIs and MCPs so that it can pulling additional information if it needs to. So for

example I have it connected to Mercury to get my bank information. Substack to

get my newsletter stats YouTube for my YouTube information. Verscell for my

YouTube information. Verscell for my website analytics. And last but not

website analytics. And last but not least, it's connected to Google Workspace because I like to write plans and stuff that I actually want to read in Google Docs and Google Sheets. Um,

and I want to make sure that Fable can also read this and update the plan as needed.

So this way, Fable has a point of reference, right? And it can pull in

reference, right? And it can pull in additional information if it needs to.

All right. After doing all this work, this is the prompt that I gave Fable Sladvisor take a detailed look at my plan document and my content schedule.

Feel free to pull other information as well. Then I want you to write a

well. Then I want you to write a detailed one pager assessing my business and what I should focus on for the next three months. Once again, you know, I'm

three months. Once again, you know, I'm making this video so I'm asking it not to share any confidential information and I'm asking and to put all this information in the plan document as a

new tab. Now uh you notice here that I

new tab. Now uh you notice here that I use the advisor skill, right? So the

advisor skill is a skill that I built for myself and this is totally optional but let's take a quick look at what's inside. Okay, so here is my advisor

inside. Okay, so here is my advisor skill and you can see here I've asked it to use the skill whenever I'm stuck on decision or asking for a gut check and

it has some basic context about my life and then it has one section about gathering live context. So I refer it to all the different MCPS and APIs that my

personal OS project is connected to so that I can pull in additional information as needed. And then it has a section about escalating to the council.

Now this is very very optional but I found it fun to build another council skill so that when my advisor is stuck it kind of escalates to the council and the council uh basically has three

different personas to have a conversation with each other. So, it has the actual customer I'm building for. It

has someone who pretends to be a skeptic about my plans. And it has an execution-minded operator. And just kind

execution-minded operator. And just kind of seeing these three personas talk to each other is very interesting and kind of causes additional insights. But

again, this is totally optional. And if

you keep scrolling down, it kind of just refers to my plan document and so on so forth, right? And last but not least,

forth, right? And last but not least, it's asking to uh proactively update the plan after every conversation I have with AI. And I'll say this again that

with AI. And I'll say this again that the skill is optional, but I built it because I'm asking for advice a lot and I found it useful to kind of frame it in these three areas. So let's go back to

Fable and let's see what Fable came up with. All right, so it said that it

with. All right, so it said that it created a one pager. So let's go to the Fable one pager here and let's see what it diagnosis is. Now, this is going to be a little bit weird because I've kind

of got rid of all the confidential information, but at a high level, it looks like the business is doing well.

I've already achieved my goal for the year. Uh, sponsorships, newsletter are

year. Uh, sponsorships, newsletter are making money. Uh, YouTube is growing

making money. Uh, YouTube is growing nicely and now we got to figure out how to retain pay subscribers and fulfill all the sponsor commitments that I have.

Right? And the focus for the next three months is fixing annual renewals of uh paid subscriptions uh shifting the content mix towards more builder tutorials and so on and so forth. Um I

feel like this is like semi- dumbed down already because the actual Fable output is extremely detailed with all the stats that I pulled from all my various channels. But the bottom line is I feel

channels. But the bottom line is I feel like the number one use case for fable that you have to try is to just use it to get life and business advice and to

do it in three steps. Right? So first of all create a highle plan like this.

Connect Fable to all the various sources of information that are relevant to the plan and then just ask it for advice and this is the highest leverage activity you can do with Fable because it's advice and stuff that can impact what

you do over the next three months, six months or even a year. So definitely

give this use case a try. All right,

let's go back to our list and now let's talk about making your project ship ready with Fable. So if you're like me, you probably have a bunch of vibe coded

projects that you want to ship eventually. And Fable, better than any

eventually. And Fable, better than any other model, is amazing at finding and fixing bugs and issues to get your project launch ready. So for example, I've been building this fitness app that

let me show you here. All right, it's a pretty simple fitness app. It lists my workout. There's a live workout screen

workout. There's a live workout screen where I can check off workouts as I complete them. U I can also edit how

complete them. U I can also edit how many sets I want to do and so on. And

after I check off all the workouts, I can say finish workout. It will show me an end workout screen with uh my progress and new PRs. And then there's

also tabs for a calendar view where I can see my past workouts. And finally,

if I click into a specific workout, I can see how things are changing over time in terms of weight and volume. All

right, so I mostly vibe coord this app with codeex and GPT 5.5. And I've been pretty much using this app for my own workouts over the past month. So it

should be in a pretty polished place, right? It seems to work fine and uh you

right? It seems to work fine and uh you know, things seems to be good. All

right, so this is what I did. So I asked Fable, I'm about to ship this fitness app that lets users track their workouts. I want you to find everything

workouts. I want you to find everything wrong with it. Read the whole codebase.

Look for real bugs, uh, broken edge cases, anything that fall over in front of a user and list all the things that you think need to be fixed and maintain a high quality bar.

All right, so Fable worked. Uh, it spun up five agents to find bugs. It ran all my unit tests and everything passed and things look good. But look at this. If I

scroll down here, so it found a bunch of pretty critical bugs. Um, number one, if you sign out

bugs. Um, number one, if you sign out involuntarily by, I guess, just shutting off the app, you could potentially leak one user's data into the next user's account. You know, this would have been

account. You know, this would have been disastrous. Uh, and then there's a bunch

disastrous. Uh, and then there's a bunch of other issues around sign out, around the MCP that I built so I can get agents to pull my workout information. uh

around edge cases like negative weights permanently breaking cloud sync and a bunch of other things. So let's see how many bugs it found. It found over 12 major bugs and a bunch of minor bugs.

And you know when I run the same prompt on uh GPD 5.5 or Opus um it does find a few bugs but nowhere near the amount that I found here. Right? So if you have

a bunch of vibe coded projects or even just real projects lying around, get Fable to check the code, find bugs and fix issues before you launch. I think

it's one of the highest leverage activities that you can do with this new model. Okay, so let's go back to our

model. Okay, so let's go back to our five use cases and now let's talk about planning the next big thing. You know, I found it really invaluable to use Fable

to do planning for a big feature and then hand it off to Opus or GPT to do the actual coding and execution. So, for

example, uh here I have a conversation with Fable again. I've forked the fitness app conversation and I basically ask Fable uh hey, I want you to draft a

detailed plan for a new nutrition tracking tab in this app. Please use

searches online to find relevant resources and then lay out the full plan, the key phases, the decisions we need to make, the risks and the open questions that I need to answer. Flag

anything that could sync the project if I get it wrong. Give me a plan clear enough that a cheaper or simpler model could execute step by step. And also uh

please write out the plan in HTML so that I can review it. So Fable worked uh through the plan. It looks like it found an API to pull food and nutrition data from the USDA from the government and it

went through everything. Now, let's take a look at the HTML that I created. All

right, so this is the HTML that I created. Uh, nutrition tracking tab, a

created. Uh, nutrition tracking tab, a fourth bottom tab that let you log meals in under 30 seconds.

All right, so it even mapped out what the tab could look like with the apple.

Let's see. Oh, it even created a proposed experience. That's pretty

proposed experience. That's pretty amazing, right? It actually created the

amazing, right? It actually created the design for the nutrition tab, which is like a delightful surprise to me. All

right, so it has a daily nutrition tracker. It's got food logging here.

tracker. It's got food logging here.

Pretty standard stuff. And let's keep going down here. And it has the architecture of how this thing should be designed. So we're going to use

designed. So we're going to use Superbase for a database again. And the

data model of what should be included.

And let's keep going down here. Some key

decisions that we need to make. All

right. All right. So, where are we going to get the food data source from? Right.

So, we can get it from the USDA FDC only. It's a free or we can get it from

only. It's a free or we can get it from some commercial thing or we can get it from open food facts. And looks like it's recommending USDA FDC own only.

It's asking what is a day and what is our cloud sync strategy and how we're going to log everything. And by the way, the HTML plan that they made here is made with lavish editor. If you just

tell Fable to make a HTML, it can make a pretty good one, too. But I'm using Lavish editor from my friend So let me pull it up. GitHub lavish. And

let's see if it found it. Here we are.

And this is like a free GitHub repo from my friend to get the HTML editor. So it

just like pastes URL into cloud or fable and ask it to use it. And the benefit of this is now I can leave comments. So for

example, if I want to say use US FDC only, I can just annotate this thing. I

say use a FDC only or I can leave comments throughout just like a Google doc and any kind of Q comments will be sent to Fable to uh work through. All

right.

Okay. And um you know everyone talks about loops and goals these days. If you

want to take this plan to the next level, you could potentially ask Fable to list some specific acceptance criteria. Like for example, give it some

criteria. Like for example, give it some images to work towards and just use slashgo to have it keep working until it actually reproduces the exact design that's shown here. Now, of course, if

you do this, you risk burning out your limits. So, personally, I would not do

limits. So, personally, I would not do it, but if you want to try it, you can.

Okay, so that is number four, which is planning the next big thing like the next big feature, next big app or the next big product that you want to build.

Again, once Fable drafts such a detailed plan, you can hand it over to GPT or Opus for actual implementation.

So, last but not least, let's talk about refactoring a large codebase.

For example, I came across this article about how Stripe used Fable to refactor 50 million lines of Ruby code and migrate it in a day where it could have

taken a whole team over two months to do. Now, I don't have a repo with 50

do. Now, I don't have a repo with 50 million lines of code, okay? But I do have my personal OS folder and it has over 40 skills that I built to

streamline all my creator work to build better apps and so on. So, let's take a look at this thing. So, here is the readme file for my personal OS repo. And

you can see here that I have a bunch of skills to help me edit my newsletter, remove AI slop, to prepare YouTube tutorials like this, to make shorts, and

uh prep the podcast and so on and so forth, right? There's a lot of different

forth, right? There's a lot of different skills here that I built for myself. And

let's go back to our very first Fable thread. So remember, Fable here

thread. So remember, Fable here suggested that it should audit and consolidate my skill system. So that's

exactly what I did. I asked it to take a look at all my user level skills and find opportunities, clean them up and make them more effective. Do a rigorous pass with skill editor, which is

actually a skill that I built to edit my skills to basically like cut out redundancies and make it more concise and you know just go ahead and find everything wrong with this personal OS

system that I have. So, Fable again spun five different agents to look through all this and it did a bunch of auditing and here is the fixes that I recommend.

So, it looks like for my council skill, there's a bunch of dead escalation block that's not really being used anymore.

For my edit document skill, there is a bunch of ambiguities.

Um, there's this pointer in my sponsor scale and there's a bunch of like temporary files that haven't been deleted and there's a bunch of other stuff around

routing and missing evals and so so it found like actually 13 things to improve through my skill system. And of course I want to audit a little bit more deeply to make sure that all these improvements

actually make sense. But with all this personal OS stuff, you want to build a system to help you do work, right? So

making sure that the system like all these skills and all these plugins actually work properly and actually give the AI the correct instructions is really important. So using a advanced

really important. So using a advanced model like Fable to fix all this stuff I think is definitely worthwhile. All

right, so let's close with three tips to get the most out of Fable. So tip number one is to prep with cheaper models. We

talked about getting a personal advisor, right? So use Opus or GBT to prep the

right? So use Opus or GBT to prep the right plan document and hook up all the APIs and MCPs to get things ready for Fable to work with you to explore the

solution space. Don't use Fable for

solution space. Don't use Fable for boring work like hooking up an MCP or API or like trying to get to draft a document. All right. And number two is

document. All right. And number two is plan with Fable and execute with another model. So, as we saw with the nutrition

model. So, as we saw with the nutrition tab plan, Fable is really great at making detailed plans. You can even make designs and architectural diagrams to supplement these plans. And once you

have a detailed plan, you can then pass this plan to another model that's cheaper to do the actual execution, right? And last but not least, consider

right? And last but not least, consider using lower effort with Fable and also babysit what Fable is doing. So, you

really don't have to run Fable with ultra high effort all the time. In fact,

if you do that, I feel like your limit is going to run out almost immediately.

So, consider using lower efforts, like high effort or even lower. And also

babysit what Fable is doing. You know,

Fable is really smart, but sometimes it can get into a rat hole and just keep looping and burning your tokens and you don't want that to happen since the tokens are so limited here on your subscription. Okay, so that's about it.

subscription. Okay, so that's about it.

Let me quickly recap the five use cases again. Use Fable to find Fable worthy

again. Use Fable to find Fable worthy work. Just ask it. You're a very smart

work. Just ask it. You're a very smart model. Look at my memory. Look at my

model. Look at my memory. Look at my files. Tell me what are some things that

files. Tell me what are some things that you think you can fix for me. Number

two, getting life and business advice.

Make a plan doc. Hook up all the APIs and MCPS and then ask Fable for long-term advice. Number three, make

long-term advice. Number three, make your project ship ready. So, you saw how many bugs uh Fable found in my vibe coded fitness app. Definitely get it to fix all the stuff before you ship

anything. Number four, plan for the next

anything. Number four, plan for the next big thing. Fable is really good at

big thing. Fable is really good at writing detailed HTML or markdown plans for another model to execute. And number

five, refactoring a large codebase for your personal work. Like you saw for me, it doesn't have to be a large codebase.

It can just be like your personal OS or something or like all of your skills that you can fix using Fable. Now, I

just want to remind all of you that Fable is back only until July 7th on your cloud subscription, which is actually two days before my birthday.

And that usage can run out super fast, right? So you have to make sure that you

right? So you have to make sure that you use it wisely. Don't yolo it with favable and don't waste this opportunity. And as always, my goal is

opportunity. And as always, my goal is to share practical no hype AI tutorials and interviews with you all. Now go out there and get the most out of Fable and I'll see you next time.