WEBVTT

1
00:00:00.000 --> 00:00:07.360
I brought on one of the best vibe coders on the planet to teach you how to squeeze the most out of

2
00:00:07.360 --> 00:00:12.720
Claude, cursor, and all these vibe coding tools. We're talking about which models to pick,

3
00:00:12.720 --> 00:00:20.240
how to use MCPs properly, the exact servers to run them on, and a hack that gets you 20% more output

4
00:00:20.240 --> 00:00:26.880
from cursor. There's even a single keyword that you can type that literally makes Claude code

5
00:00:26.880 --> 00:00:34.480
work harder. I'd never heard of it. If you want to get the most out of vibe coding platforms,

6
00:00:34.480 --> 00:00:40.000
this is the closest thing to multiplying yourself, the full breakdown is inside this video,

7
00:00:40.000 --> 00:00:47.360
and it's a lot of tangible tips and tricks how to get the most out of vibe coding.

8
00:00:48.000 --> 00:01:01.120
Chris, welcome back to the pod by the end of this episode. What are people going to learn?

9
00:01:01.840 --> 00:01:07.120
Yeah, so I'm full first. Thanks so much for having me, Greg. What I hope people learn is just what

10
00:01:07.120 --> 00:01:11.280
my AI coding workflow is, because I know a lot of people are getting into AI and there's

11
00:01:11.280 --> 00:01:14.960
a thousand tools out there. There's a thousand different ways to do this, and I want to show them

12
00:01:14.960 --> 00:01:20.080
what I'm using to build my apps, and then I'm also going to show some tips and tricks that I have

13
00:01:20.080 --> 00:01:25.040
that will probably help level up anyone who is doing AI coding. Correct me if I'm wrong, but you're

14
00:01:25.040 --> 00:01:31.120
doing thousands of dollars at MRR with your apps. You've got a portfolio of successful apps,

15
00:01:31.120 --> 00:01:37.920
some beautiful looking things, so you're going to basically show us tips and tricks and your workflow

16
00:01:37.920 --> 00:01:43.280
so that people can copy it and do a similar thing. Yeah, exactly. That's what we're going to do.

17
00:01:44.000 --> 00:01:49.760
All right, let's get into it. Okay, cool. So I'll just give a little bit of context for anyone

18
00:01:49.760 --> 00:01:53.760
who doesn't know me. My name is Chris. I build productivity apps, and then I document everything

19
00:01:53.760 --> 00:01:59.040
on YouTube, so I teach people how to build apps and just show what it actually looks like behind

20
00:01:59.040 --> 00:02:04.080
the scenes of doing it myself. I have a bunch of different apps that I've built, and the reason I'm

21
00:02:04.080 --> 00:02:09.280
showing them, it's not to plug them, it's really to show that these are very substantial apps.

22
00:02:09.280 --> 00:02:13.520
Some of them, or most of them, people are always surprised when they hear that it's just me

23
00:02:13.520 --> 00:02:19.920
building them, and to be honest, this would not be physically possible for a single person to do

24
00:02:19.920 --> 00:02:25.680
if it wasn't for AI. So that is my secret to being able to build all of these things and just

25
00:02:25.680 --> 00:02:30.240
sustain all this stuff myself, and just to leverage AI coding tools like CloudCodingCursor,

26
00:02:30.240 --> 00:02:35.600
like we're going to talk about, to be able to do this. So this is a little bit of context here.

27
00:02:35.840 --> 00:02:45.360
Let's just jump into it. So there are two tools that I'm currently using, and again, I don't

28
00:02:45.360 --> 00:02:50.480
want this to be an episode to just kind of show how to use Cursor or how to use CloudCode or

29
00:02:50.480 --> 00:02:53.920
anything, because there are so many better videos out there, and there's a bunch on my YouTube

30
00:02:53.920 --> 00:02:58.160
channel as well if you want to check them out. But I did just want to show what I'm doing,

31
00:02:58.160 --> 00:03:03.040
and then some rapid fire quick tips so that you guys can maybe apply this stuff to your own

32
00:03:03.040 --> 00:03:09.840
coding workflow. But there are two tools that I'm currently using, and it's CloudCode and Cursor.

33
00:03:09.840 --> 00:03:15.520
And what's surprising to most people is I am actually using both at the same time. And so usually

34
00:03:15.520 --> 00:03:20.560
people are like, I just have to choose one, and then I got to stick with it. But what I found is

35
00:03:20.560 --> 00:03:25.840
they have different strengths and weaknesses, and that's why I choose to use both. And I'll

36
00:03:25.840 --> 00:03:30.320
actually show you this is kind of the setup. So this is what it looks like for me. So I have cursor

37
00:03:30.320 --> 00:03:35.840
open. So this is cursor. And typically what I do is I have a terminal on the right. So typically

38
00:03:35.840 --> 00:03:39.440
the terminal thing is on the bottom, and you can just drag it to the right. And then I just run

39
00:03:39.440 --> 00:03:45.600
Claude inside on the right here. So now Claude is running. And then if I want to use cursor and

40
00:03:45.600 --> 00:03:51.120
their AI agents, I just have to change tabs. And then now here I'm using cursor. So I am frequently

41
00:03:51.120 --> 00:03:56.400
switching between both CloudCode and Cursor all the time for different purposes. And we'll get

42
00:03:56.480 --> 00:04:02.160
into why that is. But this is how I'm setting it up. And this is actually also how I do the iOS

43
00:04:02.160 --> 00:04:07.120
projects as well. Because a lot of people are always asking, how are you doing this with Xcode?

44
00:04:07.120 --> 00:04:12.000
Because I am using Xcode to do the iOS projects. What I'm doing is I'm just opening the folder and

45
00:04:12.000 --> 00:04:17.680
the files in cursor. And now when I make changes here, it'll automatically reflect in Xcode,

46
00:04:17.680 --> 00:04:22.320
and then I can run the app and everything. So this is the current, these are the current two tools

47
00:04:22.320 --> 00:04:27.600
that I'm using. It's CloudCode and Cursor. In terms of the actual strengths and weaknesses of

48
00:04:27.600 --> 00:04:35.280
these, this is why I'm using it. So Claude code is extremely good. I'm actually using this model

49
00:04:35.280 --> 00:04:39.680
called Opus 4.1. This is my favorite model. It's probably the most powerful model the best model

50
00:04:39.680 --> 00:04:46.160
there is for coding. But it is super limited. They changed their pricing since Claude code came out.

51
00:04:46.160 --> 00:04:51.760
It used to be unlimited usage. Now it's very limited to the point where I probably can exhaust

52
00:04:51.760 --> 00:04:57.120
the Opus limit for the week in maybe three or four hours, maybe less actually. So I try to use it

53
00:04:57.120 --> 00:05:02.400
very sparingly only for very, very complex problems. So for very complex problems, I'm using Claude

54
00:05:02.400 --> 00:05:07.600
code with Opus. And then, but if I'm not allowed to use it because I've exhausted the limit,

55
00:05:08.240 --> 00:05:14.080
what I'm doing for very complex problems is I'm using cursor specifically with plan mode.

56
00:05:14.720 --> 00:05:21.280
Sam Altman, the co-founder of OpenAI, just said that it is the era of the idea guy. And he

57
00:05:21.280 --> 00:05:26.640
is not wrong. I think that right now is an incredible time to be building a startup. And if you

58
00:05:26.640 --> 00:05:31.520
listen to this podcast, chances are you think so too. Now, I think that you can look at trends

59
00:05:32.480 --> 00:05:38.240
to basically figure out what are the startup ideas you should be building. So that's exactly why

60
00:05:38.240 --> 00:05:44.480
I built idea browser.com. Every single day, you're going to get a free startup idea in your inbox.

61
00:05:44.480 --> 00:05:51.680
And it's all backed by high-quality data trends. How we do it? People always ask,

62
00:05:51.680 --> 00:05:57.280
we use AI agents to go and search, what are people looking for? And what are they screaming for

63
00:05:57.280 --> 00:06:03.360
in terms of products that you should be building? And then we hand it on a silver platter for you to

64
00:06:03.360 --> 00:06:10.720
go check out. We do have a few paid plans that take it to the next level, give you more ideas,

65
00:06:10.720 --> 00:06:16.320
give you more AI agents and more, almost like a chat GPT for ideas with it. But you can start for

66
00:06:16.320 --> 00:06:20.480
free idea browser.com. And if you're listening to this, I highly recommend it.

67
00:06:21.440 --> 00:06:26.160
And I'm using, and this is what plan mode looks like. You can choose between agent mode and plan

68
00:06:26.160 --> 00:06:29.600
mode in cursor. Plan mode just means that it's going to actually plan out its steps and thinking

69
00:06:29.600 --> 00:06:36.480
and you'll approve it. And here's the hot take I'm going to have here. I am using GPT 5.1

70
00:06:36.560 --> 00:06:45.680
high for plan mode. And typically, I'm seeing people using sonnet or they're using even GPT 5 codex.

71
00:06:45.680 --> 00:06:49.600
But for some weird reason, and this is a tip I got from a developer friend of mine, he was like,

72
00:06:49.600 --> 00:06:56.960
you need to try GPT 5.1 high with planning. It's just for some reason so good. My hypothesis is that

73
00:06:56.960 --> 00:07:02.000
it was not technically built for coding, but it's really good for writing. And when you're doing

74
00:07:02.000 --> 00:07:06.160
planning and doing a lot of critical thinking and you're trying to plan out steps, maybe a writing

75
00:07:06.240 --> 00:07:10.640
model is actually better than a coding model at doing that. And then for the execution, when I'm

76
00:07:10.640 --> 00:07:16.640
done planning, I do use sonnet 4.7, I think. So I use the sonnet model to actually execute. So that's

77
00:07:16.640 --> 00:07:22.000
a configuration that I have running right now. It's I use cursor plan mode. That's the important

78
00:07:22.000 --> 00:07:28.960
model. It has to be plan mode with GPT 5.1 high. Sonnet for the execution. And then if it can't get

79
00:07:28.960 --> 00:07:33.920
it, I use clawed 4.1 opus, which again, I don't have much of that. So I try not to do it. And then I

80
00:07:34.000 --> 00:07:41.360
just switch between clawed code, sonnet 4.7, so not opus model, and then cursor plan mode. I just

81
00:07:41.360 --> 00:07:46.640
switch between them depending on depending on the task. And then the reason, and here's when I

82
00:07:46.640 --> 00:07:52.000
would use which one as well. So if you're using, if you're doing something very, very complex,

83
00:07:52.000 --> 00:07:58.160
like really complex, like it's a bug, I actually think clawed for claw or I actually think cursor

84
00:07:58.160 --> 00:08:02.320
with plan mode is better. If you're doing something massive, like you're trying to architect a whole

85
00:08:02.320 --> 00:08:07.600
app in like three or four prompts, clawed is actually really good at doing that. And then if it's

86
00:08:07.600 --> 00:08:11.520
just really small details, you can get away with with either. If it's not like something complex.

87
00:08:11.520 --> 00:08:16.080
And then I just switched depending on what it is. And then for some reason, clawed is just

88
00:08:16.080 --> 00:08:21.920
better at UI stuff. So this is the configuration that I have going. And I have tried codex, I've tried,

89
00:08:21.920 --> 00:08:26.480
I've tried almost all the coding tools. Right now at this moment of recording, these are currently

90
00:08:26.480 --> 00:08:32.720
the best ones. The other thing that I'll throw in here is if you don't have any coding experience,

91
00:08:32.720 --> 00:08:36.880
people are always asking me what should I use, I use cloud code, I should use cursor. To be honest,

92
00:08:36.880 --> 00:08:42.000
my recommendation is to use a not don't use these platforms. It's actually to really start with

93
00:08:42.000 --> 00:08:47.360
something like create anything.com for example, you can also get away using v0 or bolts or something

94
00:08:47.360 --> 00:08:52.480
else. But what I found if you want to do mobile apps specifically, I've tested all of them.

95
00:08:53.120 --> 00:08:57.600
Create anything is probably the best one at mobile specific. It's just really good at design,

96
00:08:57.600 --> 00:09:02.000
it's really good at following instructions. So my recommendation is to use a platform like that first.

97
00:09:02.000 --> 00:09:06.720
And then if you hit the limits, go graduate to something like cloud coding cursor. And by that point,

98
00:09:06.720 --> 00:09:11.040
you should have a better understanding of how to work with AI and how to prompt it to actually use

99
00:09:11.040 --> 00:09:16.320
these tools. But this is the tool set. This is what I recommend. This is what I'm actually using.

100
00:09:16.320 --> 00:09:23.840
I got to ask, because the vibe coding mobile app space is the next big thing.

101
00:09:24.800 --> 00:09:28.320
There's definitely a lot of opportunity there. A lot of people want to be able to do it.

102
00:09:29.360 --> 00:09:36.640
Rork and there's the vibe code app are two of the popular ones. In addition to anything.

103
00:09:38.640 --> 00:09:41.600
Have you seen them? Have you played with them? Any thoughts?

104
00:09:42.320 --> 00:09:48.480
Honestly, I've played with them. I still think, at least at the time recording, anything is a bit

105
00:09:48.480 --> 00:09:53.360
better. And the reason is, for some reason, the design sense is a little bit better. And its

106
00:09:53.360 --> 00:09:59.920
ability to follow instructions is it's so good. It's so good compared to the other platforms.

107
00:09:59.920 --> 00:10:03.920
But again, you can get away with using any of them. They're all using the same models under the hood.

108
00:10:03.920 --> 00:10:09.280
I believe they're all probably using the cloud models under the hood. It's really just also

109
00:10:09.280 --> 00:10:15.280
down to preference, I think. If you prefer the style choice that vibe code or Rork has,

110
00:10:16.080 --> 00:10:21.920
for sure, you can totally do it. But then, at least for me, subjectively, I did the designs

111
00:10:21.920 --> 00:10:27.680
that I was getting with them. Fair enough. I can actually show you, too. This is an example of,

112
00:10:28.240 --> 00:10:32.400
here was something that I actually did create an anything to show what you can do.

113
00:10:34.000 --> 00:10:38.160
This was something I fully designed in anything with the custom illustrations and interactions.

114
00:10:39.280 --> 00:10:45.360
Price people, when I tell them that something like this, and again, these are custom interactions

115
00:10:45.360 --> 00:10:50.240
that are happening here. These aren't components or anything. All of this stuff was built

116
00:10:50.240 --> 00:10:56.480
in anything, I think less than 24 hours. That was built. This was design and built in 24 hours.

117
00:10:56.480 --> 00:11:02.160
Yeah. This one, yeah. This one, fully working. The AI actually works. This one's like an AI

118
00:11:02.160 --> 00:11:06.640
calorie tracking app that I wanted to prototype. You take photos of your food and it'll just

119
00:11:06.640 --> 00:11:11.360
immediately scan and figure out the calories and everything. Fully built. This one was using

120
00:11:11.360 --> 00:11:18.240
anything 24 hours. Cool. That's my recommendation on the tooling and then in terms of models,

121
00:11:18.240 --> 00:11:25.440
we kind of went over this. We could go into a quick example of just kind of what it looks like,

122
00:11:25.440 --> 00:11:29.920
like what it actually looks like to vibe code something. I know in another episode that we talked

123
00:11:30.720 --> 00:11:37.440
about, we were looking at interactions and animations. Something that I kind of went semi-viral in

124
00:11:37.440 --> 00:11:46.160
my opinion for was the animation for my calorie tracking app, Amy. When you search in Amy,

125
00:11:46.160 --> 00:11:51.440
it's kind of like typing in Apple notes. Then on the right, the AI is going to calculate all the

126
00:11:51.440 --> 00:11:56.080
calories for you and it'll just appear there. But there's this really nice animation that I have

127
00:11:56.080 --> 00:12:02.160
here where you can see that it kind of drops down. There's going to be this little shiny effect

128
00:12:02.160 --> 00:12:07.680
that's going on and it shows the sources. So what I wanted to do is kind of show you guys what it

129
00:12:07.680 --> 00:12:12.320
looks like, like how I actually code this stuff really quickly. So we can kind of go into that and

130
00:12:12.320 --> 00:12:18.320
then after that, we'll just do some rapid fire tips on how I do this. So I have a blank Xcode

131
00:12:18.320 --> 00:12:23.760
project. This is just the starting Xcode project. When you run the app, it's just a simple

132
00:12:23.840 --> 00:12:29.520
hello world app that should build. So we see it's a hello world app. And again, I have this open

133
00:12:29.520 --> 00:12:34.960
in cursor and cloud code. So what I'm going to do is I'm actually going to, let's see how far,

134
00:12:34.960 --> 00:12:39.600
or let's just for a little bit, we don't have to do the full thing here. But let's try to replicate

135
00:12:40.480 --> 00:12:46.960
what I have here where let's just replicate the animation part because the searching,

136
00:12:46.960 --> 00:12:51.200
the calculating, all that stuff, let's try to do that so you guys can see what this looks like.

137
00:12:51.200 --> 00:12:55.440
So the way that I would start is I actually, let's just use cloud. You can, again,

138
00:12:55.440 --> 00:12:59.920
you can either use cursor plan mode or cloud, let's just use cloud for this case. And one of the tips

139
00:12:59.920 --> 00:13:03.760
that I have is I dictate everything. Just I get way more detailed prompts this way. And I'm using

140
00:13:03.760 --> 00:13:07.360
a tool called whisper flow as well to do this. So what I'm going to do is I'm going to say,

141
00:13:08.320 --> 00:13:16.240
can you modify this so that there's a button? And when I click it, I want an animation to run.

142
00:13:16.800 --> 00:13:24.800
It's to simulate an AI searching for nutrition info and calories. So first I want, when you click it,

143
00:13:24.800 --> 00:13:31.120
I want it to say searching and I want to have this shimmering text animation. Then after one second,

144
00:13:31.120 --> 00:13:38.240
I want that to drop down. And then I want the text to say analyzing. And I want that to drop

145
00:13:38.240 --> 00:13:43.760
from the top and replace it. And it's going to take its place. And then still with the shimmering

146
00:13:43.760 --> 00:13:50.560
effect, then after that, I want it to say found 10 sources and then just put three circles to the

147
00:13:50.560 --> 00:13:56.720
left of it. And maybe just find some random websites or just put, I don't know, YouTube, New York

148
00:13:56.720 --> 00:14:02.880
Times, Google, just so we can get the Favocons for those. Make those the sources on the left. And then

149
00:14:02.880 --> 00:14:09.280
after show calculating, then after that show some sort of hard coded calories, all just to show

150
00:14:09.280 --> 00:14:14.400
the animation, we just need to hard code everything. And then make sure that when the replacement

151
00:14:14.400 --> 00:14:22.000
happens during the animation, maybe we can make it so that it's cut off. So it's all contained on

152
00:14:22.000 --> 00:14:29.360
one line. This is the level of detail that I go with my prompts. And then I just ask Cloud

153
00:14:29.360 --> 00:14:33.680
Code to do this. So again, that's why I dictate because it would have taken me like five minutes to

154
00:14:33.680 --> 00:14:38.960
type this all by hand. And this is, this is kind of how I, this is how I scaffold apps. This is

155
00:14:38.960 --> 00:14:43.120
how I'm making my edits. It's just dictating everything. And I do the same thing in cursor

156
00:14:43.120 --> 00:14:49.120
plan mode. I'll just show you two. If we do the same thing in cursor plan mode, we won't run it

157
00:14:49.120 --> 00:14:55.760
there, but I can copy and paste what I just, what I just dictated here. I'll run it in plan mode

158
00:14:55.760 --> 00:15:00.560
in parallel. So we can see what this looks like. Okay, so now cloud code, we're back in cloud

159
00:15:00.800 --> 00:15:04.880
code. And it's saying, I'll help you make the sequence. This will include this. Do you want to do

160
00:15:04.880 --> 00:15:09.120
it? So it's asking permission if it can change the files. I'm just going to say, yes, go ahead and do

161
00:15:09.120 --> 00:15:15.760
it. So now it's running its editing files. And then we have a cursor with plan mode. It's starting

162
00:15:15.760 --> 00:15:19.520
to plan out its steps. Again, we're not going to use this one. I just want to show you what plan

163
00:15:19.520 --> 00:15:23.600
mode looks like because it's pretty interesting. Okay. And then cloud code is done. So it says that

164
00:15:23.600 --> 00:15:29.920
it did it. So let's just run it and let's just see what happens. Hopefully this is okay. Okay,

165
00:15:29.920 --> 00:15:36.080
nice. So okay, so it did actually make this animation, which is interesting, obviously not to the

166
00:15:36.080 --> 00:15:41.040
level of polish that we need here. So I might make some quick modifications. So I'm looking really

167
00:15:41.040 --> 00:15:44.880
closely. And here's a pro tip when you're doing animations and interaction stuff. If you're running

168
00:15:44.880 --> 00:15:50.320
the simulator, you can actually click at the top. It says slow animations. It will run it. I think

169
00:15:50.320 --> 00:15:56.960
half speed or slower. So you can actually see what's going on here. So I can see here. Okay,

170
00:15:57.040 --> 00:16:04.320
now there's even something going on when I do that. Like I don't like how it's dropping down

171
00:16:04.320 --> 00:16:09.200
and then going back up. It looks like. So what I'll tell it is something that's wrong with the animation

172
00:16:09.200 --> 00:16:13.920
is when something is leaving focus, it's shooting back up. Can you make sure that it drops down?

173
00:16:13.920 --> 00:16:18.880
Also increase the time to two seconds for each of the animations so they can show. Let's also make

174
00:16:18.880 --> 00:16:26.000
the shimmering effect a little more extreme. So we'll let this run. And then here's cursor with

175
00:16:26.000 --> 00:16:30.240
plan mode doing the same thing. What I love about cursor with plan mode and why I think it's better

176
00:16:30.240 --> 00:16:34.960
at very complex problems is it's really good at following up. It's really good at asking questions.

177
00:16:34.960 --> 00:16:39.200
So here it's asking should the button be usable multiple times. So we'll just say no, we just want

178
00:16:39.200 --> 00:16:44.560
to re actually, yeah, replay on every tap for the three sources. Are you okay with stabilized

179
00:16:44.560 --> 00:16:49.360
placeholders? Yeah, sure. Let's do that. So it's asking permissions on like what it should do.

180
00:16:50.320 --> 00:16:57.440
And then we have cloud code still running here. Okay, so now this is done. So let's see

181
00:16:58.240 --> 00:17:01.600
how much closer it got. And again, I don't think we're going to get as close as we want because I

182
00:17:01.600 --> 00:17:05.440
think it took me like 20 prompts to get to the level I needed to go, but

183
00:17:07.840 --> 00:17:12.320
okay, you can see it's a little bit better. It's already looking better already. Yeah.

184
00:17:12.320 --> 00:17:17.760
And then again, if you just do this a few more times, it's inevitable you can get to the level

185
00:17:17.760 --> 00:17:22.560
that I have here. That's exactly what I did here. I think it did take again 10 to 20 prompts to

186
00:17:22.560 --> 00:17:28.080
be able to get it here, but that's like an hour or two of time to get it to this level. And it's

187
00:17:28.080 --> 00:17:32.160
such a big difference. Compared to if we don't have it, here's what it looked like before I added it.

188
00:17:32.720 --> 00:17:36.960
Again, there's no, like it just kind of just says calculating, there's still kind of a shimmer effect

189
00:17:36.960 --> 00:17:41.760
and then it shows the calories, but it makes such a big difference. So yeah, that's some,

190
00:17:42.720 --> 00:17:46.800
that's that's currently how I'm doing it. Let's just go back to plan mode. So I'll just show you

191
00:17:46.800 --> 00:17:50.800
what this looks like. So when you're using cursor with plan mode, it will actually build out this

192
00:17:50.800 --> 00:17:54.800
plan for you. And so it's actually saying what it's going to do. It says step one, it's going to do

193
00:17:54.800 --> 00:17:59.600
this step two, it's going to wait two seconds, say analyzing, and then you can review this plan,

194
00:17:59.600 --> 00:18:05.280
and then when you're ready, you can build it. And then here I chose 4.5 Sonnet as the model to build it.

195
00:18:05.280 --> 00:18:09.360
And then when you click build, it's actually going to go ahead and do it. So that's that's actually

196
00:18:09.360 --> 00:18:15.120
actually I'm kind of curious what we can do is I'm going to completely restore this. So I'm

197
00:18:15.120 --> 00:18:19.840
basically just undoing everything Claude did. Let's just let cursor go ahead and build it.

198
00:18:20.560 --> 00:18:25.440
And let's just see what it comes up with. So we can compare to see kind of what the differences

199
00:18:25.440 --> 00:18:30.320
between the two are. And then maybe you'll kind of see why I switch between them so frequently

200
00:18:30.320 --> 00:18:34.880
and why I'm not just sticking with one. I love having them sometimes do the exact same task

201
00:18:34.880 --> 00:18:38.960
and then just comparing and seeing which one is better. But that's who do you think who do you think

202
00:18:38.960 --> 00:18:47.200
is going to win? I actually think Claude code will win because I found that when it comes to

203
00:18:47.920 --> 00:18:52.000
design and interactions and animations, it does have a little bit of an edge. Even if you're

204
00:18:52.000 --> 00:18:56.800
using the Sonnet model in cursor, for some weird reason, I think it is. Let's see if I'm wrong,

205
00:18:56.800 --> 00:19:03.760
though. Let's see. I'm actually curious. While we wait for this to go, though, what I'll do is

206
00:19:03.760 --> 00:19:08.320
let me let me give you a few more. We can just kind of hop into some tips. I know this one takes

207
00:19:08.320 --> 00:19:14.640
a little bit of time. So again, these are the tools. I'm swapping between the two. These are the

208
00:19:14.640 --> 00:19:23.040
models I'm using Opus 4.1, GPT-5 high, and then Sonnet for the actual execution. Here are the tips

209
00:19:23.040 --> 00:19:28.560
that I have that really I think, like when I've shared these tips, people are like they usually

210
00:19:28.560 --> 00:19:31.280
pick something up from here where they add it to their workflow and they're like this actually

211
00:19:31.280 --> 00:19:35.120
made a difference. So the first one, oh, actually, you know, this is done. Let's just see what's going

212
00:19:35.120 --> 00:19:39.200
on here. Okay, so cursor is done. Let's see what I was able to do.

213
00:19:43.360 --> 00:19:49.760
That's actually not bad. First try. Actually, you know what? If we're comparing just the first shot,

214
00:19:49.760 --> 00:19:53.120
because again, that original first shot for Claude was a little bit more choppy,

215
00:19:53.920 --> 00:19:59.040
this one was actually really good. You can tell, though, it's so fascinating that it kind of came

216
00:19:59.040 --> 00:20:03.520
to the same conclusion. I think it's because again, we're using the same model here. When I'm using

217
00:20:03.520 --> 00:20:09.360
Claude code, it's using Sonnet 4.5. When I'm using the model here, I'm using Sonnet 4.5 for the

218
00:20:09.360 --> 00:20:15.760
execution. So that's why they look so, so, so similar. But it is actually interesting that we got

219
00:20:15.760 --> 00:20:20.720
a slightly better result when we did the plan mode first with cursor. So that's actually, I think I do,

220
00:20:20.720 --> 00:20:28.400
I would choose this one over the other one. I think it's not bad. Objectively, this one was better

221
00:20:28.480 --> 00:20:33.840
than the other one first from first from. So I think so too. I think so too. Okay, so this is a

222
00:20:33.840 --> 00:20:38.800
prime example of like, even if you're using the exact same model, if you just use plan mode,

223
00:20:38.800 --> 00:20:44.080
for example, versus no plan mode on course on Claude code, you can get pretty different results.

224
00:20:44.080 --> 00:20:48.160
And that's a big reason why I think you should try to actually, you know,

225
00:20:48.160 --> 00:20:51.760
test it with a bunch of different tools, maybe have two AI tools that you're using for different

226
00:20:51.760 --> 00:20:57.280
scenarios. Yeah, this is a very fascinating one. Okay, so we'll go into like, to be honest,

227
00:20:57.280 --> 00:21:01.680
the rest of my workflow that this is kind of what I do. I just dictate everything. I'm constantly

228
00:21:01.680 --> 00:21:07.600
trying things. Let me go into some rapid fire tips on how to get the most out of the AI coding

229
00:21:07.600 --> 00:21:11.920
tools. This is exactly what I'm doing in my workflow. And then if you need to basic tutorial on

230
00:21:12.480 --> 00:21:17.280
cursor and Claude code, there's so many great ones out there. So the first one is, as we saw,

231
00:21:17.280 --> 00:21:24.160
there is a difference when you use plan mode. 100%. Every action that you take, use plan mode. You get,

232
00:21:24.160 --> 00:21:30.000
it's almost like you give the AI time to think and you will get better results. So I already showed

233
00:21:30.000 --> 00:21:34.320
you what it looks like in cursor when you do plan mode, all you have to do is toggle plan mode here.

234
00:21:34.320 --> 00:21:39.440
And it's going to give this beautiful plan on the left. And when you can review it, ask for changes,

235
00:21:39.440 --> 00:21:44.640
and then when you're ready, you click build. Unfortunately, it's not as beautiful in Claude code. So let's,

236
00:21:44.640 --> 00:21:49.600
let me show you what this looks like. You can actually hit shift tab and it'll change it to plan mode

237
00:21:49.600 --> 00:21:54.640
here. And now when you ask Claude code to do something in plan mode, it's going to kind of do

238
00:21:54.640 --> 00:21:59.360
the same thing that cursor does where it's going to think through, come up with a plan and ask you

239
00:21:59.360 --> 00:22:05.600
to review it. But what I have found, at least at the time of recording, cursor's plan mode is stronger

240
00:22:05.600 --> 00:22:11.440
than Claude code, which is why I use cursor plan mode for insanely complex problems. It just

241
00:22:11.440 --> 00:22:15.840
somehow thinks about it a little bit better. It asks better follow up questions. But that is tip

242
00:22:16.800 --> 00:22:20.720
number one. And then here's Claude code asking for thing. It's like, yeah, here's my plan.

243
00:22:20.720 --> 00:22:24.880
You can already just tell, like, oh, actually, this is not fair because it's looking at the current

244
00:22:24.880 --> 00:22:29.120
code right now. But typically, this is what happens. It tells you it's plan and then it's up to you

245
00:22:29.120 --> 00:22:33.760
to just review and approve it. It will not be as detailed as cursor's plan. Like, cursor's plans

246
00:22:33.760 --> 00:22:38.080
are just so detailed. They're very, very good. So that's tip number one. It's used plan mode.

247
00:22:38.800 --> 00:22:43.920
I'm pretty sure if you do this, the output will probably at least increase by 20% at minimum if

248
00:22:43.920 --> 00:22:48.080
you just do this. So 100% do this. It's also good to just review what it's about to do as well.

249
00:22:48.080 --> 00:22:51.920
Like, it's better than just letting it run, you know, run through your code base. And then you

250
00:22:51.920 --> 00:22:56.240
have to retroactively go, uh, yeah, you have to go back and try to fix it. This is just a way

251
00:22:56.240 --> 00:23:03.040
better way to do it. Um, second tip, this is specifically with Claude code. It's to use the keyword

252
00:23:03.040 --> 00:23:10.560
ultra think. So this one is actually a special keyword that Claude code has. And I'll show you,

253
00:23:10.560 --> 00:23:18.480
if you type in, can you fix this issue and you type in ultra think, it actually changes colors

254
00:23:18.480 --> 00:23:23.360
because it is doing something. When you type this in, Claude code is actually going to think a

255
00:23:23.360 --> 00:23:28.720
little bit harder about the problem. I'm assuming that it uses up more tokens and more usage when

256
00:23:28.720 --> 00:23:34.400
you do this. But to be honest, I think I use ultra think in 90% of my messages. And I have not

257
00:23:34.400 --> 00:23:39.920
really found that it's impacted my token usage versus if I don't do it, it seems like it's about

258
00:23:39.920 --> 00:23:43.760
the same. So there's no reason not to do it. So when you're stuck on a complex problem,

259
00:23:43.760 --> 00:23:49.520
just type ultra think and Claude will think maybe I'm assuming it seems like it takes twice as long.

260
00:23:49.520 --> 00:23:54.160
So maybe it thinks twice as hard or something. But this is a keyword I'm very surprised people

261
00:23:54.160 --> 00:23:58.240
don't know about. So you will get a lot better results when you do this. I don't think there is one

262
00:23:58.240 --> 00:24:02.640
in cursor. It doesn't highlight. But I think you can still say like ultra think in cursor. If you're

263
00:24:02.640 --> 00:24:08.400
using Sonnet as the model, I think it will work too. But there's no nice color animation or color

264
00:24:08.480 --> 00:24:12.720
thing here to show that it is actually doing something. So that's the that's my second tip.

265
00:24:13.760 --> 00:24:21.920
The next tip is in Claude code, you can actually run background tasks. So this is where you can tell

266
00:24:21.920 --> 00:24:25.760
Claude code, can you run the server in the background for me? This is something I think they only

267
00:24:25.760 --> 00:24:30.800
added in the last month. So this is a relatively new thing. But what this does is Claude code will

268
00:24:30.800 --> 00:24:34.880
literally run your server in the background. So it's running just like you would in the terminal.

269
00:24:34.880 --> 00:24:39.920
But the important part is it now has access to your server logs. So when you're running and when

270
00:24:39.920 --> 00:24:44.640
you're coding with Claude code, it can now access this during debugging. So if you're like,

271
00:24:44.640 --> 00:24:48.880
hey, why is this not working? It will then you don't have to copy and paste things and say, hey,

272
00:24:48.880 --> 00:24:53.440
the server is crashing. Take a look at this. It just has access to it. And this is a massive one,

273
00:24:53.440 --> 00:24:57.600
which I just don't see people doing either. I think it's probably because it's a recent thing. But

274
00:24:57.600 --> 00:25:01.600
I'm constantly telling it, hey, run, all you have to do is say, run the server in the background

275
00:25:01.600 --> 00:25:05.600
for me. And you'll see this thing that says one background task. And it's basically running it.

276
00:25:05.600 --> 00:25:12.080
So I'm constantly using this. This is another big one. The next one is MCP servers. So last time I

277
00:25:12.080 --> 00:25:18.560
came on the podcast, I was not using MCP servers. And to be honest, I didn't understand like what

278
00:25:18.560 --> 00:25:23.440
the whole hype was about with MCP servers. I now understand like where they're useful, especially for

279
00:25:23.440 --> 00:25:28.080
coding. So there's two MCP servers that I'm currently using. The first one's called contact seven.

280
00:25:28.080 --> 00:25:34.480
It's a free MCP server. Basically, it just lets you access the latest version of a lot of different

281
00:25:34.480 --> 00:25:40.160
documentation. And it's very compressed and very well formatted for an LLM. So instead of what I

282
00:25:40.160 --> 00:25:44.800
typically would do is I would just get the documentation for something like let's say I wanted to integrate

283
00:25:44.800 --> 00:25:49.600
post hog analytics into my app. I would typically say, by the way, here's the link to post hog,

284
00:25:49.600 --> 00:25:54.400
go implement it for me. But the problem with that is it now has to go scrape it. Maybe it doesn't

285
00:25:54.400 --> 00:26:00.160
do it correctly. Or you can use contact seven, hook up the MCP server and you're basically giving

286
00:26:00.160 --> 00:26:06.560
cloud code and cursor tools. And now it has access to contact seven, which now I can just say,

287
00:26:06.560 --> 00:26:11.520
oh, make sure to use the latest documentation for post hog. Please use the contact seven MCP.

288
00:26:11.520 --> 00:26:16.240
And when you do this, it's going to use the contact seven, pull the latest documentation,

289
00:26:16.240 --> 00:26:22.720
really compressed, really, really more digestible for a cloud coder cursor. And it will just

290
00:26:22.880 --> 00:26:26.640
it will just use it way better than you trying to feed it in through a URL or something. So that's

291
00:26:26.640 --> 00:26:33.920
the first one. Second one I'm using now is super base. So this one is I'm probably going to get

292
00:26:33.920 --> 00:26:38.480
some heat for this. But because a lot of developers are probably going to say, oh, this is not secure,

293
00:26:38.480 --> 00:26:44.000
why are you doing this? But in my experience, this MCP and you can use this for fire base, you can

294
00:26:44.000 --> 00:26:50.000
use for whatever database you're using is so powerful to correctly set up a project for you. So I'm

295
00:26:50.000 --> 00:26:55.040
constantly using this to set up projects from scratch. Because before I would have cloud code

296
00:26:55.040 --> 00:26:58.880
do all the coding and everything, but then I would have to manually go set up my database, make

297
00:26:58.880 --> 00:27:06.240
sure I'm configuring rules correctly. I would argue that if you are using a tool like super base MCP

298
00:27:06.240 --> 00:27:10.880
where cloud code has full access to super base, it can spin up everything for you. It actually might

299
00:27:10.880 --> 00:27:15.680
be more secure because it has caught things that I have manually configured wrong. Like it has set

300
00:27:15.760 --> 00:27:21.040
up the security rules better than I would have done to be honest. And so this is something where

301
00:27:21.040 --> 00:27:26.000
I actually do recommend if you're a beginner or if you're a seasoned developer, it's really helpful

302
00:27:26.000 --> 00:27:30.160
to use this. And if you're a developer and you don't trust it, at least use the super base MCP

303
00:27:30.160 --> 00:27:34.880
to read your configuration and just double check your work. So you can just say, hey, I set up the

304
00:27:34.880 --> 00:27:39.040
super base server, I set it all up, I hooked it up, can you just double check that I set it up

305
00:27:39.040 --> 00:27:43.680
correctly, check all the security rules, check all this stuff, check the indexes so the performance is

306
00:27:43.680 --> 00:27:48.000
good. This is a really powerful MCP. And again, you can do this for Firebase, you can do this

307
00:27:48.000 --> 00:27:54.240
for AWS, they have an MCP, I believe as well. And it's just such a powerful way, just give

308
00:27:55.280 --> 00:28:00.240
give cloud coder cursor access to these tools. And anything you can do in the UI, they'll be able

309
00:28:00.240 --> 00:28:05.360
to do. When I'm in production though, I will say I'm way more cautious about using it because it

310
00:28:05.360 --> 00:28:09.680
could just delete your entire server if it wanted to and just delete the database. So I am a

311
00:28:09.680 --> 00:28:14.640
little bit more cautious, but I still do run this in production though because it is it's just so

312
00:28:14.640 --> 00:28:19.440
much faster for my workflow to use this. So those are the only two that I'm seriously using right

313
00:28:19.440 --> 00:28:23.200
now. I'm sure that's going to change in a few months though. Like I'm going to probably play with

314
00:28:23.200 --> 00:28:29.840
the Figma MCP now and test this out more, but yeah, these two are very good. The next one is

315
00:28:30.480 --> 00:28:36.560
this is a very this is a very big one for solar developers or anyone that has no coding experience.

316
00:28:37.360 --> 00:28:45.200
Right now, there are a couple of AI coding tools that can review your code for you. And specifically,

317
00:28:45.200 --> 00:28:49.280
if you open a pull request in GitHub, so let's say you make a bunch of changes and you

318
00:28:49.280 --> 00:28:53.680
open up like like if you if you have any coding experience, you know that the proper way to do

319
00:28:53.680 --> 00:28:58.800
something is you add your code to GitHub and then another developer reviews it before it gets

320
00:28:58.800 --> 00:29:02.800
merged into production. If you're a solar developer, you have you don't have that luxury.

321
00:29:02.880 --> 00:29:08.320
There's really no one who can review your code. So I'm using tools like Bugbot and Cloud

322
00:29:08.320 --> 00:29:14.720
Code has one as well where it can actually live inside of your code base. And anytime you open

323
00:29:14.720 --> 00:29:19.840
up a pull request or you want someone to review your code, it will do it for you. And I will say

324
00:29:20.480 --> 00:29:26.240
these tools, when you hook them up, it is so much better than trying to do this inside of cursor

325
00:29:26.240 --> 00:29:30.400
or cloud code itself because I think these are maybe custom models or something, but they're

326
00:29:30.400 --> 00:29:35.840
specifically trained to identify security issues and bugs. And so what I'm doing is I have them

327
00:29:35.840 --> 00:29:40.960
hooked up to all my repos and it has caught so many things for me. And again, it's stuff that I am

328
00:29:40.960 --> 00:29:45.840
a pretty experienced developer, I believe, but I mean, I'm working so fast, I'm moving so quickly,

329
00:29:45.840 --> 00:29:49.760
it's just inevitable that bugs will be introduced, security vulnerabilities will be introduced.

330
00:29:49.760 --> 00:29:54.000
It gives me so much peace of mind. And I think the cursor one is just $40 extra per month,

331
00:29:54.640 --> 00:29:58.240
totally worth it, totally worth it for peace of mind, especially from the security

332
00:29:58.720 --> 00:30:04.000
perspective. So I recommend hooking this up. It's a hack for solo developers and for vibe

333
00:30:04.000 --> 00:30:08.960
coders who are really worried about security, best $40 you'll probably ever spend to be able to

334
00:30:08.960 --> 00:30:14.800
sleep at night knowing it's everything is secure. The next thing which is then the next thing is

335
00:30:14.800 --> 00:30:21.680
dictation. This is as you saw when I was dictating when I was trying to use cloud code, I was dictating

336
00:30:21.680 --> 00:30:26.560
my prompt. It's because you can just get way more detailed prompts and then that will help steer

337
00:30:26.560 --> 00:30:31.600
the AI in a way better direction. I actually didn't think this was a big deal, but then when people

338
00:30:31.600 --> 00:30:36.240
started seeing me do this in my videos, I didn't know people weren't doing this. And that was

339
00:30:36.240 --> 00:30:41.440
something where people were like, wow, I just downloaded this. Yeah, my AI coding has dramatically

340
00:30:41.440 --> 00:30:46.240
improved because I'm dictating everything now. So that's another hack, 100% recommend dictating.

341
00:30:46.240 --> 00:30:50.080
You can use whisper flow like I'm using. There's also some other tools, but whisper flow is really

342
00:30:50.080 --> 00:30:54.480
great because it has built in developer terminology. So you can say developer terms and it kind of

343
00:30:54.480 --> 00:31:03.120
understands it already too. The last tip that I have is to use cloud for deep research on

344
00:31:03.120 --> 00:31:07.280
technical issues. So something a lot of people don't know is that if you are paying for cloud

345
00:31:07.280 --> 00:31:13.920
code, you also have increased usage inside of cloud desktop, like the chat app. And you can actually

346
00:31:13.920 --> 00:31:20.000
use it to do deep research for you. And so what I'm doing frequently is I'm actually asking it,

347
00:31:20.000 --> 00:31:24.160
hey, this is what I'm about to do in my app. So I'm again, I'm a pretty experienced developer,

348
00:31:24.160 --> 00:31:28.800
I think. So I ask it, what's the best way to store data? I'm looking for something similar to this

349
00:31:28.800 --> 00:31:35.040
in React. What do you think? And it will go and it will look for 12 minutes straight and look

350
00:31:35.040 --> 00:31:39.360
through all of the documentation and try to find the best way to do this. And then it'll just

351
00:31:39.360 --> 00:31:43.600
summarize everything for me. And then I can just take that and then review it obviously. And then

352
00:31:43.600 --> 00:31:47.200
I'll send it over to cloud code and say, hey, can we actually do it this way? Because I think this

353
00:31:47.200 --> 00:31:52.880
is a better way. So this is a great way. If you're a developer to double check, are you implementing

354
00:31:52.880 --> 00:31:56.800
them correctly? Learn some new concepts. And then if you're just getting started out, this is

355
00:31:56.800 --> 00:32:01.200
also a great way. If you can just ask it, hey, I've never done this before. What is the best way

356
00:32:01.200 --> 00:32:05.920
for me to store data? So this is something that I am very surprised. I don't see a lot of people

357
00:32:05.920 --> 00:32:10.080
taking advantage of, especially non technical people, especially people who are just starting to

358
00:32:10.080 --> 00:32:14.320
vibe code. You like, you don't have to call your developer friends anymore and say, hey, how do I

359
00:32:14.320 --> 00:32:17.680
set up this? Like, how should I structure my app? Just use cloud, especially if you're paying

360
00:32:17.680 --> 00:32:22.000
for cloud code already. And then obviously double check it. And if you don't know what you're doing,

361
00:32:22.000 --> 00:32:25.600
you can ask it follow a question. So you can say, why did you choose this pattern? Okay, what other

362
00:32:25.600 --> 00:32:30.720
patterns exist? There's also a great way to learn as well. So this is probably it's a win-win if you

363
00:32:30.720 --> 00:32:35.200
use something like this. And then you can just feed it into cursor and cloud code. And then it has

364
00:32:35.200 --> 00:32:40.800
access to this. It's able to implement it for you. And yeah, I've just I found so many things that

365
00:32:40.800 --> 00:32:47.360
I've done not wrong, but I could have done better because I use clouds deep research. So I know

366
00:32:47.360 --> 00:32:54.080
this wasn't a full-on coding tutorial, but these were just a couple of things that I've been telling

367
00:32:54.080 --> 00:32:58.960
people in my YouTube videos. And I've gotten a lot of comments saying, yeah, these are very helpful

368
00:32:58.960 --> 00:33:02.880
tips. Like, people did not know bugbed exists. People did not know deep research existed. So

369
00:33:02.880 --> 00:33:07.120
hopefully there's some cool stuff that you can take and apply to your own AI coding workflow.

370
00:33:07.600 --> 00:33:12.720
I appreciate you. I think we're all trying to get the most out of these vibe coding platforms and

371
00:33:13.600 --> 00:33:20.720
little tips and tricks help like this, especially a lot of us are, you know, solo builders, solo

372
00:33:20.720 --> 00:33:28.720
developers, right? So it's not like we have people in real life to talk to. So this is helpful. And

373
00:33:28.720 --> 00:33:33.520
I'd like to thank you for coming on and spreading that, spreading the sauce with us and

374
00:33:34.400 --> 00:33:40.960
I'll include where you can go find Chris and get more of him in the show notes. So you can check

375
00:33:40.960 --> 00:33:45.760
check that out there. And Chris, don't forget about us. Come back on again. For sure, for sure. Yeah.

376
00:33:45.760 --> 00:33:49.280
Thanks so much for having me Greg. Really appreciate it. All right.