Chris Raroque

So that's tip number one.

It's use plan mode.

I'm pretty sure if you do this, the output will probably at least increase by 20% at minimum if you just do this.

So 100% do this.

It's also good to just review what it's about to do as well.

It's better than just letting it run through your code base and then you have to retroactively go back and try to fix it.

This is just a way better way to do it.

Second tip, this is specifically with Claude Code.

It's to use the keyword UltraThink.

So this one is actually a special keyword that Claude Code has.

And I'll show you, if you type in, can you fix this issue?

And you type in UltraThink, it actually changes colors because it is doing something.

When you type this in, Claude Code is actually going to think a little bit harder about the problem.

I'm assuming that it uses up more tokens and more usage when you do this.

But to be honest, I think I use UltraThink in 90% of my messages.

And I have not really found that it's impacted my token usage versus if I don't do it.

It seems like it's about the same.

So there's no reason not to do it.

So when you're stuck on a complex problem, just type UltraThink and Claude will think

maybe I'm assuming it seems like it takes twice as long.