WEBVTT

00:00:00.240 --> 00:00:02.640
I've been running the GSD,

00:00:02.720 --> 00:00:06.240
get shit done framework on my last two projects.

00:00:06.560 --> 00:00:07.600
And honestly,

00:00:07.680 --> 00:00:09.600
the results have been unreal.

00:00:10.000 --> 00:00:16.925
I'm shipping in about half the time it usually takes me instead of just messing around with Claude or ChatGPT

00:00:17.005 --> 00:00:18.605
in a endless vacuum.

00:00:18.925 --> 00:00:21.965
One of the things I really want to start exploring

00:00:21.965 --> 00:00:28.380
is how can we two x the two x. GSD really enables us to work faster.

00:00:28.860 --> 00:00:33.420
But I noticed when I first started going on with GSD, I was going in cold,

00:00:33.660 --> 00:00:35.580
and I was letting GSD

00:00:35.580 --> 00:00:37.900
essentially just guide me through the project.

00:00:38.595 --> 00:00:39.955
But I discovered

00:00:40.115 --> 00:00:44.595
if I prime GSD with really good research information,

00:00:45.155 --> 00:00:55.020
my projects were going a lot faster in the long run. So I think it's really, really important to shift our mindset from completely relying on AI tools

00:00:55.420 --> 00:01:02.140
and making ourselves more the architects and really thinking about how our project structure should be going forward.

00:01:02.460 --> 00:01:06.300
So today, I'm gonna show you how to prep a pre context file

00:01:06.485 --> 00:01:13.285
that turns your workspace into an execution machine and that really primes the get shit done methodology

00:01:13.525 --> 00:01:16.405
to enable you to just work even faster.

00:01:17.205 --> 00:01:19.125
So this is the

00:01:19.205 --> 00:01:21.045
get shit done GSD

00:01:21.320 --> 00:01:22.680
git repository.

00:01:23.000 --> 00:01:24.520
And I would highly recommend,

00:01:24.600 --> 00:01:26.680
if you don't know about this repository,

00:01:26.680 --> 00:01:31.560
you go in and you just take a look at and understand

00:01:31.560 --> 00:01:32.440
everything

00:01:32.680 --> 00:01:35.000
that's going on in this repository

00:01:35.315 --> 00:01:38.755
because it's really interesting how it's all put together.

00:01:38.995 --> 00:01:43.795
But in order to get started, there's there's a few really high level things that you need to know.

00:01:44.195 --> 00:01:50.595
Um, the first of all is, uh, part of the GSD framework is you need to run claw dangerously

00:01:50.860 --> 00:01:52.140
and skip permissions.

00:01:52.380 --> 00:02:03.500
This seems really, really scary at first, but I promise you it's not once you get in and you start using it. If you've done AI projects before, you know how much Claude code needs to get permissions.

00:02:03.500 --> 00:02:05.260
And for a lot of those permissions,

00:02:05.500 --> 00:02:19.655
if Claude code crashes for any reason, then what happens is when you reload into Claude code, you have to give it that the all those permissions again. So it can it can be really annoying. So just starting Claude code by skipping these permissions is totally part of this.

00:02:20.320 --> 00:02:28.080
There are alternative if you do want to monitor that a little bit more effectively, but I would recommend that's the big thing. And then always,

00:02:28.240 --> 00:02:37.815
whenever you're starting GSD and the for the purposes of this video, uh, GSD new project is how you just get started, and it does a really good job of guiding you through

00:02:37.975 --> 00:02:39.175
how to

00:02:39.335 --> 00:02:40.855
execute on that project.

00:02:41.335 --> 00:02:44.535
So let's go into what actually GSD

00:02:44.535 --> 00:02:46.910
is doing on a high level. So

00:02:47.150 --> 00:02:53.710
this is what your typical a new project looks like. Right? So you're you're like, okay. I have a client requirement,

00:02:53.870 --> 00:02:59.790
and you know what? I gotta start my new project. So first thing I'm gonna do is I'm gonna dive right into GSD.

00:02:59.790 --> 00:03:02.245
I'm gonna do slash GSD new project.

00:03:02.485 --> 00:03:07.445
And what I'm saying is you actually don't wanna do this. And then for those who don't know,

00:03:07.845 --> 00:03:18.450
essentially what GSD is when you start a new project, it'll ask you a bunch of questions and it's gonna create two main documents at least. The first the first big document it's going to create is

00:03:18.690 --> 00:03:22.210
the project road map or like a a PRD.

00:03:22.290 --> 00:03:28.050
And essentially in this project road map, what it does is it lists out all the phases,

00:03:28.050 --> 00:03:30.770
just very high level of what needs to be accomplished.

00:03:31.635 --> 00:03:40.435
And then the other thing it's going to do is get a technical state of the types of tech you want to do. So when you start a new project to ask you, okay, what do you wanna accomplish?

00:03:40.435 --> 00:03:46.195
What do you want your back end to be? Um, how do you wanna develop your front end? Like, it's going to ask you a bunch of those questions.

00:03:46.940 --> 00:03:52.940
And essentially what it's starting to prep is your context window primer

00:03:53.020 --> 00:04:10.665
so when you start to execute in these phases okay I need to set up the front end for my client like I need to get a new website set up and maybe I want like an AI chat bot or something. It's going to break that up into phases or it's gonna break that up to milestones and then inside those milestones it's gonna break it up into phases.

00:04:10.825 --> 00:04:13.385
And then what you do is you say execute phase one

00:04:13.625 --> 00:04:22.700
and what it will do is it'll shoot all of this information into the context window, and it'll shoot the technical state into the context window,

00:04:22.860 --> 00:04:30.300
and then the instructions on how to execute phase one. Like, really, really high level. That's essentially what GSD does in a nutshell.

00:04:30.940 --> 00:04:32.860
But the problem that

00:04:33.075 --> 00:04:38.355
not really a problem, but where I've really noticed we can get a lot more efficient

00:04:38.435 --> 00:04:40.435
is starting to prep

00:04:41.235 --> 00:04:42.435
GSD

00:04:42.675 --> 00:04:43.635
before

00:04:43.635 --> 00:04:51.840
we actually engage into project. So what does that look like? So if you look at any AI project or any project you wanna complete in general,

00:04:52.080 --> 00:04:58.160
there's a few high level things that we need to dig into. First of all, who are the stakeholders in the project?

00:04:58.960 --> 00:05:00.720
What are we trying to accomplish?

00:05:01.315 --> 00:05:04.755
What are our timelines? Like, project scope is is a really big

00:05:04.995 --> 00:05:11.395
is a really big topic. And then secondly, what are the discussions that we've had around this project?

00:05:11.955 --> 00:05:16.170
And so what I found is if we can essentially

00:05:16.250 --> 00:05:18.090
mark up and summarize

00:05:18.090 --> 00:05:23.610
all of this information into a single document and then use this document

00:05:23.770 --> 00:05:25.610
to feed GSD

00:05:25.610 --> 00:05:35.065
when we initially create our project, it's two x ing your two x. So what does that look like when we actually create a new project? Well, firstly,

00:05:35.305 --> 00:05:37.625
all of us are using notetakers nowadays.

00:05:37.865 --> 00:05:45.590
So having access to an API or having access to webhooks on our notetakers where we can download the transcripts

00:05:45.830 --> 00:05:54.150
and add them into our project folders is a hidden superpower. Secondly, we've if we're doing client work, we've created a lot of documents

00:05:54.385 --> 00:05:58.385
explaining what we're doing. We've created a project scope document

00:05:58.465 --> 00:06:07.230
that should be getting fed into your context, your pre context window. So this should actually be like a pre context window. And then secondly, the stakeholders,

00:06:07.230 --> 00:06:13.070
like, that's really important. Like, are we working with a project manager? Are we working with the CEO? Are we working with a VP?

00:06:13.390 --> 00:06:25.425
What do they have the power to do in this project? Are they like a decision maker or are they like an operator of it? We need to know that information because as we pushed our project forward,

00:06:25.585 --> 00:06:33.825
we wanna achieve success. So let's dig in now to how we can actually get these three things and create this pre context file.

00:06:34.920 --> 00:06:37.720
Okay. So this is Claude code,

00:06:38.120 --> 00:06:40.680
and I have it installed on WSL,

00:06:40.680 --> 00:06:47.880
which is a Linux image on my Windows machine, and I'm inside a cursor right now. I've done a little bit of prep to expedite this process.

00:06:48.435 --> 00:07:05.930
And, essentially, I've come in and I've run a slash init since I'm starting a new Claude project in Claude code. I've also logged in to Claude. Additionally, there's two more things that we need to focus on here, which is I have installed two MCP servers,

00:07:06.410 --> 00:07:07.450
which MCP

00:07:07.450 --> 00:07:09.690
essentially just allows us to

00:07:10.250 --> 00:07:13.530
have our Claude code agent communicate

00:07:13.610 --> 00:07:17.050
with their technology or we can communicate with their services.

00:07:17.575 --> 00:07:18.215
So

00:07:18.455 --> 00:07:20.615
my notetaker is TLDV.

00:07:20.615 --> 00:07:36.810
And then what's also going to be very important is API phi or Apify. There's so many different things you can call this. But essentially, this is just like a scraper. It's a scraper mechanism for us that we can essentially use to get this information.

00:07:37.050 --> 00:07:46.570
So now that I have my project initially set up, the slash in it creates the Claude MD file for me. And then from there, we installed the MCPs

00:07:46.570 --> 00:07:51.105
and away we go. So in order to prep this on the original

00:07:51.185 --> 00:07:54.625
document that we had, there's three main folders.

00:07:55.025 --> 00:08:02.810
So I'm going to add these folders into my into my project. We can call it like client research or project research.

00:08:03.530 --> 00:08:04.410
Project

00:08:04.410 --> 00:08:05.210
research.

00:08:07.450 --> 00:08:09.850
And then we have three subfolders in here

00:08:10.570 --> 00:08:15.290
that we want to add which is going to be project scope.

00:08:16.090 --> 00:08:17.210
There's going to be

00:08:17.965 --> 00:08:18.925
discussions.

00:08:19.725 --> 00:08:21.485
So first things first is

00:08:22.045 --> 00:08:22.765
like

00:08:22.925 --> 00:08:41.600
for discussions, there's a couple of ways to do this. You can just go in and create markdown files yourself and paste the transcriptions in there depending on if you just have a few meetings or if you wanna be really if you wanna do it the cool way, which I'm doing it, you can do it through API or MCP servers.

00:08:42.240 --> 00:08:51.325
So if you wanna do that, you can just copy the transcript and you can just say, like, hey Claude create a md file of this discussion

00:08:51.965 --> 00:08:54.445
and then you can paste the transcript in there.

00:08:54.925 --> 00:08:59.830
The other thing you can do is if you're used to using MCP servers is you can essentially

00:09:00.230 --> 00:09:05.190
if you're used to using APIs or MCP servers, you can essentially just grab

00:09:05.430 --> 00:09:13.485
like a you can give the agent context on the meetings. Like, you can say, I want you to grab all the transcripts

00:09:13.645 --> 00:09:17.405
with client x y z and move them into the discussions folder.

00:09:17.565 --> 00:09:22.605
Um, and I can show you exactly how this works after I've installed the TLDV MCP.

00:09:22.925 --> 00:09:25.485
I can say use the TLDV

00:09:25.485 --> 00:09:26.125
MCP

00:09:26.720 --> 00:09:35.600
and then I just use TLDV as my notetaker. There's so many other notetakers that have API access and MCP access.

00:09:35.760 --> 00:09:44.375
So, um, you can install those. And if you're interested in learning more about installing MCP servers, I can show more on this. But use that TLDV MCP

00:09:44.535 --> 00:09:45.575
to grab

00:09:46.215 --> 00:09:48.215
to grab my discussion

00:09:48.695 --> 00:09:50.055
from yesterday

00:09:54.135 --> 00:09:56.055
from yesterday named

00:09:56.530 --> 00:10:00.450
Traverse Weekly Call which is one of my one of my businesses

00:10:01.090 --> 00:10:04.290
and create a MD file

00:10:04.290 --> 00:10:05.890
in the discussions

00:10:06.530 --> 00:10:07.410
folder

00:10:07.730 --> 00:10:09.170
with the transcript.

00:10:11.365 --> 00:10:13.685
And since I have the TLDV

00:10:13.765 --> 00:10:14.325
MCP

00:10:14.645 --> 00:10:15.685
installed

00:10:15.845 --> 00:10:16.645
and

00:10:18.805 --> 00:10:20.325
since I have the TLDV

00:10:20.325 --> 00:10:29.220
MCP installed and the skills installed and clogged code, you can see right here, it's essentially just connecting directly to TLDV,

00:10:29.380 --> 00:10:35.780
and it's going to create that transcript for me. So you can start to see the power of context

00:10:36.100 --> 00:10:44.645
at work here. And this is the coolest thing ever because now if we go into my discussions tab, obviously, Claude is still doing its thing.

00:10:44.885 --> 00:10:49.605
Once this is finished, I'm going to have my transcript in the discussions tab.

00:10:49.685 --> 00:10:55.045
While that's going now, let's talk about stakeholders and project scope. So project scope

00:10:55.170 --> 00:10:58.290
is good to move all of your project

00:10:58.370 --> 00:11:07.410
details into this folder. So if you've created any sort of documents when you've done your sale for AI consulting or your AI agency,

00:11:07.490 --> 00:11:12.605
move those into the project scope folder. If you've done any sort of proposal

00:11:12.605 --> 00:11:17.885
for the client, move that into the project scope folder. And then lastly here,

00:11:18.045 --> 00:11:20.285
we have the stakeholders folder.

00:11:20.525 --> 00:11:27.510
The stakeholders folder is essentially what I would really recommend you do is you essentially

00:11:27.830 --> 00:11:29.110
scrape your

00:11:29.750 --> 00:11:30.710
clients'

00:11:31.110 --> 00:11:32.710
LinkedIn profiles

00:11:32.870 --> 00:11:35.670
and do a little bit of a write up on each stakeholder.

00:11:36.055 --> 00:11:36.855
Additionally,

00:11:36.855 --> 00:11:41.895
another really good thing I do with the a the API fi MCP

00:11:42.215 --> 00:11:42.855
is

00:11:43.575 --> 00:11:46.535
I love to do competitor research.

00:11:46.775 --> 00:11:52.580
Um, I do a lot of high level AI consulting projects, and competitor research is really necessary.

00:11:52.740 --> 00:11:54.980
So we can use the APIify

00:11:54.980 --> 00:11:55.940
MCP

00:11:55.940 --> 00:11:58.180
to scrape LinkedIn profiles,

00:11:58.180 --> 00:12:03.300
and then we can also use it to scrape the websites and scrape the profiles

00:12:03.795 --> 00:12:15.555
of our of their competitors and add it into this project research folder. It's super powerful. So we'll do a little bit of that once this finishes. So I'm gonna let this finish now.

00:12:16.035 --> 00:12:18.915
Okay. So now we can see the TLDV

00:12:19.120 --> 00:12:19.920
MCP

00:12:19.920 --> 00:12:24.800
did its it connected to my TLDV account, grabbed that transcript,

00:12:25.040 --> 00:12:29.040
and it created a discussion markdown file that you can see right here,

00:12:29.360 --> 00:12:30.320
um, above

00:12:30.640 --> 00:12:37.585
that, um, is in our discussion. So you can obviously take this now and you can apply this to multiple discussions.

00:12:37.905 --> 00:12:52.810
Um, you can even search by email or name inside of the TLDV MCP or if your notetaker has a particular MCP or API, you can do that as well. All these notetakers are the same nowadays anyways and they all have the same kind of accessibility

00:12:52.810 --> 00:12:59.450
into them. Or again, you can just move the transcripts in. So next we wanna move on to project. We wanna move particularly

00:12:59.450 --> 00:13:00.250
into

00:13:00.570 --> 00:13:11.705
the, um, discussions tab and you can see here Claude just made another discussions folder. So I'll just move that in there and then I'll I will just, uh, delete that because I don't need that anymore.

00:13:12.105 --> 00:13:12.665
Um,

00:13:13.145 --> 00:13:20.480
you can see we have project scope and we have stakeholders right now. And really what I just wanna show off very quickly is

00:13:21.440 --> 00:13:28.400
how can we use the MCP servers to build this context. So first of all, I've connected APIify

00:13:28.400 --> 00:13:29.200
into

00:13:29.405 --> 00:13:32.445
I've connected into the APIify MCP server.

00:13:32.605 --> 00:13:37.965
And so I have all of the if if we if you don't know what APIify is, it's essentially a

00:13:38.525 --> 00:13:43.965
scraping service that has a variety of different scrapers where you can scrape LinkedIn, you can scrape websites,

00:13:44.205 --> 00:13:51.320
you name it. And it's MCP is extremely powerful. As an example, what I will do now is I will run

00:13:51.480 --> 00:13:53.960
I will grab my own LinkedIn profile

00:13:53.960 --> 00:13:58.920
and I will say let's say I'm one of the stakeholders for this project. I can say,

00:13:59.715 --> 00:14:02.195
please use the a API

00:14:02.195 --> 00:14:04.675
five MCP server to

00:14:05.075 --> 00:14:06.595
research a

00:14:07.155 --> 00:14:08.675
research a

00:14:09.315 --> 00:14:10.195
LinkedIn

00:14:10.595 --> 00:14:13.475
profile public profile scraper

00:14:15.690 --> 00:14:17.050
and scrape

00:14:17.850 --> 00:14:19.050
our client's

00:14:19.690 --> 00:14:20.490
profile

00:14:21.050 --> 00:14:21.930
which

00:14:21.930 --> 00:14:23.770
is my LinkedIn profile.

00:14:24.090 --> 00:14:33.055
So API Fi is going to now provide is going to do its thing and it's going to scrape that profile and I'm just gonna say add the

00:14:33.295 --> 00:14:34.815
scraped

00:14:35.375 --> 00:14:36.815
MD file

00:14:36.815 --> 00:14:38.895
into the stakeholders

00:14:39.935 --> 00:14:40.895
folder.

00:14:41.695 --> 00:14:54.590
K. And it's a you can always you can always just add a command into Cloud Code as you go on, um, and it'll take that additional context and it'll go. So you can see it's found an API scraper and now it's added it into the stakeholders.

00:14:55.175 --> 00:14:58.375
It looks like it's created another folder. That's okay.

00:14:58.775 --> 00:15:01.975
And it it'll add that at in a markdown into that folder.

00:15:02.375 --> 00:15:05.415
Additionally, what we can do with APIify

00:15:05.415 --> 00:15:08.055
is we can also scrape websites.

00:15:08.430 --> 00:15:10.510
We can scrape our client's website,

00:15:10.670 --> 00:15:20.430
and we can also scrape competitors' website. If you're a AI consultant or an AI agency, you should be doing this as part of setting up all your project. You know? And then we can say, like,

00:15:21.215 --> 00:15:27.055
we'll wait for this to finish, but we'll run a scrape of our website and we'll add that into the markup

00:15:27.215 --> 00:15:29.295
folder. And while this is running,

00:15:30.015 --> 00:15:40.430
we also have the project scope tab on the right here. And essentially what the project scope tab on the right is is what we should add in is any project folders

00:15:40.510 --> 00:15:53.505
that we've come up with up until this point. So I'm talking about if you've created any proposal documents for your clients, if you've done any pitch decks as part of signing the business, or if you have a project scope document.

00:15:53.665 --> 00:16:04.040
All of that should be added into the project scope regardless of what format they're in PDF or anything like that because what we're going to do is when we collect all of this information,

00:16:04.120 --> 00:16:08.120
you'll see that we now have we now have

00:16:08.440 --> 00:16:11.400
enough information to make that pre context.

00:16:12.040 --> 00:16:14.680
We're able to prime the primer essentially.

00:16:14.760 --> 00:16:30.945
So here you can see Claude code made a little bit of a mistake, not a big deal though. But you can see my LinkedIn profile here. Um, it's completely scraped and it's it's in the context of our project folder now. And then lastly, what we'll do is we will create a in the stakeholders tab,

00:16:31.265 --> 00:16:32.625
um, we will copy

00:16:33.080 --> 00:16:34.200
the path

00:16:34.680 --> 00:16:35.560
and then

00:16:35.960 --> 00:16:37.720
we can ask Claude code,

00:16:37.960 --> 00:16:40.040
hey, can you scrape

00:16:40.280 --> 00:16:43.240
our client's website for context

00:16:43.240 --> 00:16:45.560
and add it to this

00:16:46.285 --> 00:16:48.605
location in a md file.

00:17:07.660 --> 00:17:13.020
Okay. And now you can see that our our website scrape has been

00:17:12.705 --> 00:17:13.985
added into

00:17:15.425 --> 00:17:18.305
our project folder, our project research folder.

00:17:18.465 --> 00:17:20.225
So once we've

00:17:20.465 --> 00:17:21.425
identified

00:17:21.425 --> 00:17:25.265
and we've added in all our project research into the scope,

00:17:26.030 --> 00:17:29.630
we want to now prime our GSD.

00:17:29.950 --> 00:17:32.510
So very easily we can say

00:17:32.750 --> 00:17:34.430
we can say, Claude,

00:17:34.510 --> 00:17:38.670
please look over my project research folder

00:17:39.215 --> 00:17:40.335
and create

00:17:40.415 --> 00:17:42.175
a comprehensive

00:17:43.455 --> 00:17:44.975
markdown folder

00:17:46.015 --> 00:17:47.615
that summarizes

00:17:47.775 --> 00:17:49.375
all the information

00:17:49.775 --> 00:17:51.455
we have between

00:17:52.175 --> 00:17:53.055
project scope,

00:17:54.790 --> 00:17:55.590
oops,

00:17:55.750 --> 00:17:57.030
project scope,

00:17:58.630 --> 00:17:59.830
the discussions,

00:18:00.950 --> 00:18:02.230
and the stakeholders.

00:18:02.870 --> 00:18:08.390
Um, Additionally, if you've done another great thing you can do with the API Fi MCP

00:18:08.765 --> 00:18:09.965
is you can

00:18:11.565 --> 00:18:13.965
you can do competitor research in there

00:18:14.925 --> 00:18:16.845
and create a

00:18:18.125 --> 00:18:19.485
and stakeholders

00:18:19.485 --> 00:18:21.005
to create a

00:18:21.485 --> 00:18:22.525
pre context

00:18:24.150 --> 00:18:25.510
pre context

00:18:25.510 --> 00:18:26.870
MD file

00:18:26.870 --> 00:18:30.230
that we will use to get our GSD

00:18:30.230 --> 00:18:31.030
project

00:18:31.030 --> 00:18:31.910
launched

00:18:32.070 --> 00:18:33.430
with maximum

00:18:34.790 --> 00:18:35.830
efficiency.

00:18:36.150 --> 00:18:44.785
Then what I would just recommend you do is, like, I'm just trying to do this very quickly right now. But once we create that initial folder,

00:18:44.865 --> 00:18:47.265
you do wanna go in into this markdown

00:18:47.345 --> 00:18:49.665
file and you want to

00:18:50.385 --> 00:18:55.960
really, really dial in on it. That's the best way to really, really get the most out of this.

00:18:56.440 --> 00:18:59.960
Um, and then what's gonna happen after all of this takes place

00:19:00.120 --> 00:19:02.760
is we're then going to finally

00:19:02.760 --> 00:19:04.520
initiate GSD.

00:19:04.760 --> 00:19:06.520
So really exciting.

00:19:06.600 --> 00:19:10.565
Claude has collected all the context for a pre context folder.

00:19:10.725 --> 00:19:13.525
It's gonna be spitting that out any second now.

00:19:13.845 --> 00:19:15.365
And then from there,

00:19:15.685 --> 00:19:20.245
we're going to be able to engage GSD and get our project started.

00:19:20.805 --> 00:19:24.440
At which point, we would go slash GSD

00:19:24.600 --> 00:19:25.400
new

00:19:25.480 --> 00:19:26.200
project.

00:19:26.440 --> 00:19:28.360
And then once it starts

00:19:28.680 --> 00:19:29.480
inquiring

00:19:29.480 --> 00:19:33.160
about us or once it starts inquiring about the project,

00:19:33.320 --> 00:19:37.160
what we wanna do is we wanna reference this pre context folder

00:19:37.355 --> 00:19:46.475
and answer its questions so you'll just have a solid context for your for your new project and you have been set up in the best way possible

00:19:46.955 --> 00:19:49.435
like a professional AI consultant.

00:19:50.500 --> 00:19:52.500
So what we explored today

00:19:52.580 --> 00:19:57.700
was we got an understanding for how we wanna start setting up our AI projects.

00:19:57.860 --> 00:20:00.420
We wanna use frameworks like GSD,

00:20:00.420 --> 00:20:07.305
but what's really important is how we set those frameworks up. We utilized MCP servers

00:20:07.305 --> 00:20:12.825
to make the process of gathering all of our project context in the most efficient way,

00:20:13.145 --> 00:20:17.385
but we also understand there's manual backups if we're not that advanced yet or

00:20:17.730 --> 00:20:19.330
we don't have MCP

00:20:19.330 --> 00:20:20.770
or API

00:20:20.770 --> 00:20:23.730
access into the project context that we need.

00:20:24.130 --> 00:20:26.050
And we understand now

00:20:26.210 --> 00:20:28.130
how to make a pre

00:20:28.370 --> 00:20:30.305
project context file

00:20:30.305 --> 00:20:34.545
so when we start engaging our project frameworks like GSD,

00:20:34.705 --> 00:20:37.185
we can do so in the most efficient way possible,

00:20:37.265 --> 00:20:41.105
which in the long run will end up saving us a lot of time.

00:20:41.837 --> 00:20:49.677
So if you have any questions, leave a comment below. I'd be more than happy to answer. Please like and subscribe if you'd like to see more of this content.

00:20:49.917 --> 00:20:51.117
I'll catch you guys around.
