So now with the Claude.md file set up, it's finally time to get
our hands dirty and start working on the actual code and
project. And, therefore, I cleared my session here again
with /clear to make sure that we got an empty context
window again, and here's the first prompt I'll send to
Claude Code. And it's up to you how complex your tasks
be. In my experience, having smaller, focused tasks can
lead to better results, but that is up to you, and you can, of course,
run multiple Claude Code instances in parallel if you wanna work on multiple
tasks at the same time. But here, I'll start with one simple
task, which is to set up the core route
the pages that make up this project, and I tell it to
not implement authentication yet, and I also tell
it to not actually include the actual page content yet, but just
some, uh, dummy message on each page.
And then I'll switch to plan mode. Plan mode is
another mode supported by Claude Code, and you switch between modes by
hitting shift tab. And here's a simple
recommendation. For the vast majority of tasks, you
should start in plan mode, even if they seem simple.
Plan mode is a mode where Claude Code will first gather
some relevant information before starting work,
and it will ask you for clarification questions if more
clarification is needed. It can help you turn
average prompts into good prompts, essentially, and it
allows you to be a bit more lazy, though ideally you're
not lazy, but you're turning good prompts into
Either way, using plan mode is a pretty good default, and
indeed my default for most prompts I send to Claude Code.
If you send a task in plan mode to Claude Code, it
can't edit files yet. It doesn't have the permissions for
when using that mode. Instead, it starts by exploring
your project and by then creating a plan on
how to tackle the task you gave it, and it may
also ask for further clarification
depending on your prompt and the task you gave
it. It also saves those plans locally
temporarily so that it always has access to them even in
situations where your context window should clutter up and needs to be
cleared. Even then, it would still be able to refer back to
But we'll get back to full context windows a little bit later.
Now, it will then tell you about the plan it
So here it describes which routes it wants to set up,
and it then gives you more details here, and then
gives you a couple of options. It may also ask some questions here
depending on how well-written your prompt was, how
complex the task was, and simply also some randomness.
Now, at the point of time where I'm recording
I can accept that plan, clear the context, and auto-accept
edits, which is the first option. Clearing the context, of course, does
not mean that the plan gets thrown away.
That is remembered, but everything before the plan gets thrown
case you had a longer conversation here, you would start with an
almost empty context window again, which only includes the
plan. You can also not clear the context window
and, uh, continue by manually approving edits
clear the context window and auto-accept edits.
I'm not sure what that option should be about.
Sounds similar to the second one to me.
But then you also got a fifth option where you can give Claude more
information. And, for example, here I'm not happy about that.
I want one single authentication route.
And I also noticed that I wanna be clear about the fact that
in my authentication setup, I only want a single
authentication route. So I'll say I only want a single slash
authenticate route which supports
only email plus password auth. And I'll submit this, and
this does then not start the implementation, but instead Claude goes
back into planning mode and revises and updates its plan.
The same would happen if it asked you some questions.
And now with that, I'll indeed then clear the context and
auto-accept all edits to let it do that route setup work.
Now here it then wants to run linting to check for linting errors.
I'm happy with that, so I'll allow that and tell it to not ask me for
again. And then it wants to build to check
I'll also let it do that. And here we go.
It's done, and now, of course, I can start my development server with
dev command here, and actually I'll need to switch the port
I have something else running on this port, but that's just my personal setup
here. If I visit this site here, I
can navigate between different routes, I can go
to the dashboard page here, and I got that dummy content on
these pages, which is exactly what I asked for.