§ 01 · The Hook
The bait, then the rug-pull.
Snowflakes fall across the presenter via AR overlay before the camera cuts clean to a warm studio Christmas scene and a claim that lands like a whisper from a private Slack: Anthropic has been shipping Claude Code features quietly, and if you were not on the right Twitter accounts, you missed all of them.
What the video promised.
stated at 00:22 "Whether you are a beginner or a pro, you will be using Claude Code completely differently after these 10 updates." delivered at 13:40
Where the time goes.
00:00 – 00:45
01 · Hook + Promise
FOMO open: 10 secret updates, explicit beginner-to-pro promise, description CTA established
00:45 – 01:58
02 · 1. Resume Sessions
claude --resume opens a picker of all past sessions for the project; demo on a Kanban project management app
01:58 – 03:18
03 · 2. Visualize Context (/context)
/context shows a breakdown of what is filling the context window (system prompt, tools, messages); /clear to free up the messages portion
03:18 – 04:17
04 · 3. Usage Stats (/stats)
/stats shows token usage, streaks, active days, peak hours, and model breakdown; community engagement hook: share your streak in comments
04:17 – 05:44
05 · 4. Name Sessions (/rename)
/rename <name> tags the session so --resume picker shows meaningful names; demo: calling a session Kanban
05:44 – 07:14
06 · 5. Rewind (Double Escape)
Double-press Escape triggers a rewind picker showing all recent checkpoints; select one to restore code and conversation state
07:14 – 08:55
07 · 6. UltraThink
Add the word Ultrathink to any prompt to trigger extended thinking; renders in rainbow colors in the terminal; recommended for complex tasks and initial build phases
08:55 – 10:47
08 · 7. Custom Memories (#)
Type # to enter memory mode; specify user memory or project memory; recommended homework: always use the design skill when changing the UI
10:47 – 11:39
09 · 8. YOLO Mode (--dangerously-skip-permissions)
claude --dangerously-skip-permissions disables permission prompts; recommended only for experienced users; enables long-running autonomous tasks
11:39 – 13:00
10 · 9. Plugin Store (/plugins)
/plugins opens a discoverable store of skills, plugins, and MCPs; top pick: frontend design skill
13:00 – 13:40
11 · 10. Stash Prompts (Ctrl+S)
Ctrl+S stashes the current prompt draft; after a quick command the stash auto-restores to the input line
13:40 – 14:27
12 · Outro + CTA
Subscribe, notifications, like; livestreams Mon/Wed/Fri 11AM PST; engagement question: which update will you use?
Visual structure at a glance.
Named ideas worth stealing.
01:58
model
Context Management Loop
- Run /context to see what is filling the window
- Identify the biggest culprit (usually messages at 32%)
- Run /clear to reset messages, or trim CLAUDE.md if system prompt is the issue
Three-step mental model for diagnosing and fixing Claude hallucination caused by context overflow
Steal for Any Claude-getting-worse troubleshooting content or CLAUDE.md hygiene post
07:14
concept
UltraThink Trigger Word
Adding the literal word Ultrathink to a prompt activates extended reasoning mode; renders in rainbow in the terminal; best for complex tasks and initial app scaffolding
Steal for Complex task prompts, initial app scaffolding, deep bug-dives
10:00
concept
Design Skill Memory Shortcut
- Type # to enter memory mode
- Say: always use the design skill when changing the UI
- Choose project memory
One-time memory instruction that permanently gates all UI changes through the frontend design skill for the project
Steal for Any Claude Code workflow tutorial; a JoeFlow CLAUDE.md tip
Lines you could clip.
02:00
"I hear a lot of people on X complaining right now, oh, Claude's getting worse. No. That's a skill issue. They're just not managing their context well."
10:47
"Claude for me hasn't made mistakes in months. And I know that might sound crazy..."
07:14
"UltraThink is totally back into Claude code, and you need to be using it."
How they spent the runtime.
Hook length45s
Info densityhigh
Filler8%
How they asked for the click.
13:40
subscribe
"Make sure to stay on top by subscribing, turning on notifications, and leaving a like down below."
Clean outro with livestream schedule (Mon/Wed/Fri 11AM PST). Engagement question asked before the CTA keeps retention high through the pitch.
Word for word.
HOOK opening / re-engagementCTA the pitch
00:00HOOKOver the past month, Anthropic has released a ton of secret updates to Claude Code that you would only find out about if you were following specific Twitter accounts. In this video, I'm gonna go over all those secret updates that you probably missed that will completely change how you use Claude Code and make it way better. If you use Claude Code, this is gonna be the most important video you watch this month. I promise you, whether you're a beginner or a pro, you will be using Claude Code completely differently after these 10 updates. Let's get into it. So this one is a great one, and that is the ability to resume past Claude code sessions. If you're anything like me, you've had tons of conversations with Claude code that has context you don't wanna miss out on. You reset your computer and all that context disappears.
00:45Well, no more. If you type into your terminal claud dash dash resume, hit enter, it will bring up all your past sessions you had with claud code for the project you're working on. So for the sake of demonstration of this video, I'm gonna show you this project management tool I'm building out right now. It helps me manage all my projects in Claude code. So I have all my past sessions here that I've had with Claude. What So I'm gonna do is I'm gonna hit resume on my past session, and all the context I had and all the conversation I had from that session is now completely resumed.
01:20So now I don't have to go back and fill in Claude code with all the past context every time I reset my computer or my Visual Studio code. This is massive, and this is gonna make it so much easier to get back into past conversations you have and not miss out on any of the context you had before. I put the command to resume your sessions down below in the description. All the commands and all the changes I go over will be down in the description below, so feel free to pause and copy and paste that into, like, your Apple notes. Okay. So say we resumed our past session and there's a ton of context in there. When you get a lot of context into Claude code and starts filling up your window, it actually can make Claude
01:58hallucinate a lot more than it does before. I hear a lot of people on x complaining right now, oh, Claude's getting worse. No. That's a skill issue. They're just not managing their context well. But how do you manage your context better if you start seeing worse performance with Claude? Well, what you wanna do is use their brand new slash command slash context.
02:16This is going to help you visualize what is currently in your context right now. So I'm gonna run that. And, again, slash context, I'll put down below. And you'll be able to see here now in this really nice visualization what is taking up your entire context window. So you can see here the system prompt is taking up a good amount of context. That's because I have a ton of clawed rules. All the tools we're using,
02:38the messages we've done so far, this is actually taking up the most context with 32% is the past messages. So if I wanted to free up context right now, I would just go in here and I would do slash clear, and that would clear the message history since right now it's taking up the most context.
02:53So if you start to see degraded performance in Claude, do slash context, see what's taken up all the space. Maybe it's your system message. Maybe it's your past messages in the conversation, and then you can take care of it from there. If it's the past messages, just do slash clear just like I did here, which takes me to the next big update that they released in the last few weeks, and that is slash stats. It's another brand new slash command.
03:18So one of the biggest complaints I hear about Claude as well is people don't know how many tokens they've used up in their plan. Are they getting to the end of their plan? Are they gonna have upgrade to a more expensive plan? Well, now you'll be able to see exactly how much usage you've had in your plan. If you do slash stats, it will show you all your usage for that time period. You can see all your interesting stats here, how many tokens you've used. Are you getting to your limit on tokens?
03:41Your streaks, how many sessions you've had, your active days, your peak hours. You can even tap and see the different models you've been using. As you can see, once Opus dropped, it was game over. I was using Opus tremendously more. So you can see a lot of your usage here, how many tokens you've used, and if you're getting up to your current limits and if you need to upgrade or not. Slash stats, keep tabs on that. It's also just fun to see your numbers and see how much you're using Claude and which models you're using. If you run slash stats right now, let me know down below what your usage looks like. How many days in a row have you used Claude code? I'd be really curious to see. So second ago, we were talking about resuming
04:17sessions. This is something you need to be doing often because if you're anything like me, you're also doing multiple sessions at once. I like to have multiple Claude codes open so I can work on different features at the same time. Well, one really awesome thing they just added in their recent holiday updates is the ability to actually name sessions so that when you resume old sessions like I showed you at the beginning of this video, you can see very clearly what you were doing in each session because you can give it those custom names. All you need to do to name your sessions is do slash rename and then give it a name for your session. So for this one, I was working on the Kanban board of our project management, so I'm gonna call it Kanban.
04:57And I'm gonna hit enter, and now our session is now called Kanban. So if I go to a new terminal here and I do Claude slash slash resume and hit enter, we can see our new name session Kanban that we were using just a second ago with all 246 messages. So this is really important to do. If you're doing multiple sessions, which I think you should be doing when you're waiting for one session to build out a feature, it's really good not to get distracted, not to look at TikTok. Open up another session. Start working on another feature. Make sure to give it its own name with slash rename. And, again, all these slash commands, all these updates down below in the description you don't have to forget any of these. The next update they made is great if you often make mistakes when working with Claude code. This is something I do a lot. I do a lot of experimentation.
05:44I have a change around features to see how it works, and sometimes I mess up and I give it a bad command. So for instance, in this project management tool, I wanted to experiment with the colors and notes. I made it blue. I don't like the blue. It's not really standing out against the black background. So let's rewind this. In a brand new update to Claude code they just released, you can now rewind
06:03super easily any changes you made that were mistakes. You do this by hitting escape twice. Double escape, and it goes back and it gives you these rewind options. And what I can do is I can go back and I can say rewind to the rename Kanban, which was one step before the changing of the colors of the notes. I'm gonna hit enter on that, and I'm gonna say restore
06:24the code and the conversation. So it's gonna forget any of the conversation after, and it's gonna restore all the code. And I'm gonna hit enter, and boom. Just like that, we are back. And it's at the rename Kanban, and I can hit enter on that. And we are back to that one step before changing all the colors to blue. This is amazing. If you make mistakes often, if you experiment, you should be experimenting a ton. Ever since they released this double escape feature, it's given me a lot more freedom to try new things. So double escape, an awesome way to rewind if you make any mistakes at all. The next update is a big one, and it brings back a much loved feature that's kind of been experimented with, taken out, put back in. Well, it's fully back. UltraThink is totally back into Claude code, and you need to be using it. What UltraThink is is the ability to force Claude code to work extra hard on tough problems.
07:14And I've been using this a lot, and let me tell you, you get way better results when using UltraThing. So as you can see here, I wanna add a calendar to our app. I want it to be beautiful. I want Claude to work extra hard on it. So I said, add a beautiful calendar section to our app using the design skill. Ultrathink about this. And for the record, if you don't have the design skill yet, I'll put a link down below. You need to install the Claude design skill. I'm thinking about doing an entire video dedicated to Claude skills. If you want that, let me know down the replies as well. But the key here is I said Ultrathink. And as you can see, they put it in, like, the rainbow colors. All you need to do in any of your messages is type the term Ultrathink,
07:51and it will force Claude code to think very, very hard about what it's doing and put more effort in the creation. Hitting enter on that will start the process, and it is going to make sure that this calendar looks way better than it would before. I wouldn't use UltraThink on every single prompt you do. It's gonna take a lot longer, and you're probably gonna burn a lot more tokens than you need to. But any prompts you give where you're doing a complex task or you're solving a complex bug, I would a 100% use UltraThink because you're going to get noticeably better results. This is a really good feature to use when you're kinda building out the base of your app after the first planning phase because you're gonna get a way better base to your app. Use UltraThink, again, down below in the description. The next big feature they released over these last few weeks that I absolutely love is the ability to create custom memories. So before anytime you wanted Claude to remember something, you had to go into your Claude rules and put it there. But that could be challenging at times. I don't always remember to put things into Claude rules, or Claude rules can get very crowded and disorganized
08:55if you're adding a ton in there. So what I like to do when I have small things I want Claude to remember in its process is to create custom memories for it. So for instance, I want Claude to use the design skill anytime it changes the UI, and I want it to remember that for the rest of the time that I'm working on this app. So what you wanna do to create custom memories for Claude is you're gonna do the hashtag,
09:20which changes you to memory mode. So you can say add to memory. And then we're gonna say, always use the design skill when changing the UI. And I'm gonna hit enter. And now it's going to memorize this. I wanna put it into the project memory, so you can do user memory or project memory. I want it to remember it just for this project. I'm gonna hit enter there. And now anytime
09:42we change the UI in this project, it is going to use that design skill. I actually highly recommend you copy exactly what I just did now. Go pause this video. Go into Claude code. Do hashtag, and then type in use the design skill anytime you change the UI because the design skill is so freaking good. It's gonna make your app look so much better. So custom memories, anytime you want Claude to remember something that does every single time in its process,
10:07make sure to use custom memories. I highly recommend you do the design skill memory I just did, and you can use it moving forward. This next update is a tip for the risk takers out there, but this is putting Claude into YOLO mode. This is the mode it goes into when you don't want to ask you for permission anymore. I'm gonna be completely honest with you. Claude for me hasn't made mistakes in months. And I know that might sound crazy, but when you get so used to Claude code that you know how it works, you know how it operates, you know how to talk to it, you really don't mess up with it anymore. Opus four five has gotten so smart, I don't mess up. So I like to use YOLO mode. And the way to do that is you put in this command, Claude dash dash dangerously
10:47skip permissions, And then you hit enter on that, and that's going to put Claude in YOLO mode. I'm gonna hit accept on this. I would only recommend using this if you are super used to Claude codes. If you're on the pro side of Claude code, I would do this. This saves me a ton of time. I like to give Claude long running tasks where I can hit enter and walk away, and I don't have to keep hitting accept, accept, accept over and over again. This allows me to just do that and treat Claude as an independent employee. I put the command down below. If you're Claude pro, copy that. If you're an amateur or you're a beginner, I'd say spend a month or two getting used to Opus and how it works and the right prompts to give it. And then when you're comfortable, you can use this command. I'll put that down below. Claude YOLO mode, really, really helpful for saving time. The next big update, and this is a huge one, basically adds an entire app store to Claude code, is slash plugins. If you do slash plugins,
11:39hit enter, you now have an entire, basically, store of skills and plugins and MCPs you can put right into Claude code very, very easily. I would highly recommend, if you haven't yet, go in here, do slash plug ins, and go down to front end design. This is the plug in you need if you're building any sort of app. My UIs with my apps I built are a thousand times better because of this skill. So if you haven't installed this yet, do slash plugins,
12:07go in Discover, go down to front end design, and install that. But there's so many other ones. If you use GitHub a ton, if you use any of these others, Figma, Linear, Notion, you have a ton of plug ins and MCPs. You can get installed with one click that will make it so much easier to work between all your different tools. I couldn't recommend enough. Check out the plug in store and see if you use any of these integrations inside the plug in store. At the very least, get the front end design skill installed. The last update we'll go over here is saving your prompts. If you're anything like me, you come up with an idea, you write a prompt out, and then right before you hit enter, you realize you need to do something else right before you send that prompt, and then you sit there and you hold backspace for five minutes while it deletes your prompt. You don't have to do that anymore. Say you write out a prompt. I want you to build out a calendar,
12:57and I realize I need to do something else first. You can now hit control s. That will stash your prompt. And now after I say something like add a light mode to the app and hit enter, it will take my stash prompt and put it back into the line here so I can send it after. No more sitting there and hitting back space for five minutes at a time to get rid of your prompts. Now you can just stash your prompt,
13:26CTAgo in, write whatever else you need to do, and then your stash prompt will then automatically be placed inside your command line so you can use it again. This has saved me so much time. I will put that down below as well. Control s to stash your prompt. Those were the big changes from the last month, and they're adding a ton more as we speak. They've been adding new ones every single day. I'm gonna keep an eye on them. I'm going to create more follow-up videos over the next few weeks going over all the additional changes they're coming out with. Make sure to stay on top list by subscribing,
13:57CTAturning on notifications, and leaving a like down below. I also livestream Monday, Wednesday, Friday at 11AM Pacific Standard Time. If you wanna see me build apps out in real time with Claude Code as well. So appreciate if you watch the video. Let me know in the replies which of these updates will be the most helpful for you. I'm curious which ones you're going to use. Thank you so much for watching the channel. Every single view and like and all that means the world to me. It's an honor to be creating you educational content. I will see you in the next video.
— full transcript
§ 05 · For Joe
Ten commands. One demo project. One format you can steal today.
JoeFlow / builder playbook
The numbered-overlay listicle with a single live demo project running the whole video is the most efficient format for developer tutorial content — low production cost, high completion rate, every tip in real context.
- Use the # memory trick right now: add 'always use the design skill when changing the UI' to any Claude Code project you are actively building.
- Build your next tutorial around one project you are already working on — every tip demonstrates on real code, not contrived examples.
- Put chapter numbers as text overlays in the top-left corner — it functions as a visible table of contents and keeps viewers oriented without YouTube chapters.
- Drop every command in the description and say 'all down below' repeatedly — it trains viewers to keep the description open and drives the engagement signal YouTube rewards.
- The YOLO mode segment is the one to clip for shorts — confident, polarizing, repeatable format: 'I know this sounds crazy, but [strong claim].'
- UltraThink is worth a standalone JoeFlow demo: trigger extended thinking, show the rainbow rendering, compare output quality on a real build task.
