WEBVTT

00:00:00.080 --> 00:00:04.059
So with that Spec.md file set up,
I wanna continue.

00:00:04.080 --> 00:00:07.920
And as a next step,
I wanna leverage the fact that I'm a

00:00:07.960 --> 00:00:11.880
developer and I know things about setting
up projects

00:00:11.900 --> 00:00:15.630
and writing code. Specifically,
I wanna do certain things

00:00:15.880 --> 00:00:19.860
I know need to be done where I don't wanna
rely on the

00:00:19.940 --> 00:00:23.620
AI to do it right if I know how to do it
right.

00:00:23.700 --> 00:00:27.340
Specifically,
that means I wanna install some packages,

00:00:27.440 --> 00:00:31.200
I wanna install the betterauth package,
which I'll do with bun add

00:00:31.260 --> 00:00:35.170
here. I'll also install the sod package,
which is a package that will

00:00:35.200 --> 00:00:38.750
help me with validating user input,
and for that

00:00:38.920 --> 00:00:42.840
Tiptap rich text editor which I wanna use,
I also

00:00:42.860 --> 00:00:46.260
wanna follow the official instructions on
installing the relevant

00:00:46.400 --> 00:00:50.240
packages. So I'll copy these too
and also install those

00:00:50.320 --> 00:00:54.240
into that project. By doing that manually,
I ensure that

00:00:54.300 --> 00:00:57.800
I'm definitely installing the right
packages with their latest

00:00:57.900 --> 00:01:01.380
versions because whilst AI can also
install

00:01:01.460 --> 00:01:05.319
packages, sometimes in my experience,
it does that by editing

00:01:05.360 --> 00:01:08.700
this dependency management file,
this package.json file in

00:01:08.780 --> 00:01:12.120
JavaScript's case,
and by then inserting some old

00:01:12.540 --> 00:01:14.860
packaged versions in there, which I,
of course, don't want.

00:01:14.900 --> 00:01:18.399
That's why I'd rather do it myself because
I know which packages I'll need

00:01:18.480 --> 00:01:22.300
anyways. Now, there also
is one other package I need to install

00:01:22.360 --> 00:01:26.220
here and that's a development-only
dependency, the bun-types

00:01:26.340 --> 00:01:30.220
package,
which will avoid certain typescript errors

00:01:30.300 --> 00:01:34.040
APIs. With that out of the way,
I'll open Cloud

00:01:34.120 --> 00:01:38.070
Code again and I'll start a new session
because I wanna get rid of

00:01:38.160 --> 00:01:40.500
all the old context that was in there.

00:01:40.580 --> 00:01:44.560
And in that new session,
there's one thing I also wanna

00:01:44.660 --> 00:01:48.500
do whenever I start working on a new
project with Cloud Code, and

00:01:48.580 --> 00:01:51.520
new does not necessarily mean new app.

00:01:51.560 --> 00:01:55.260
It can be an existing app,
an existing code base, it just means a

00:01:55.320 --> 00:01:58.240
project where I haven't used Cloud Code
before.

00:01:58.300 --> 00:02:02.280
I wanna run the slash init command in
there because slash

00:02:02.440 --> 00:02:06.020
init does one important thing.
It gets Cloud Code to

00:02:06.060 --> 00:02:09.500
thoroughly analyze this code base so
that also

00:02:09.538 --> 00:02:13.220
includes the dependencies that
are installed, which

00:02:13.240 --> 00:02:16.900
them manually,
and it takes a look at all the different

00:02:16.940 --> 00:02:20.769
there to understand this project and

00:02:20.800 --> 00:02:23.200
understand what we're doing in there.

00:02:23.260 --> 00:02:27.000
It should also detect this Spec.md file,
for

00:02:27.060 --> 00:02:30.660
example, and then based on all
that information it

00:02:30.760 --> 00:02:34.520
gathered,
and here it's asking me for some

00:02:35.840 --> 00:02:39.720
to explore the content of a folder,
based on all

00:02:39.760 --> 00:02:42.989
that information it gathered,
it will create a

00:02:43.060 --> 00:02:46.960
Cloud.md file. And that is a

00:02:47.040 --> 00:02:50.810
very important file which
was created here, so let's take a

00:02:50.840 --> 00:02:52.120
closer look.