The Day-One Claude Code Setup: Exactly What I Tell Every Beginner to Do First

Almost everyone who tries Claude Code for the first time does the same thing: they open it, type a couple of questions, get a decent answer, and then have no idea what to do next. It feels like a smarter chat window, so they use it like one. The power - Claude actually building things in your project - stays hidden because nobody set the thing up to reach it.

I've onboarded a lot of beginners now, and the ones who stick are never the ones who found a clever trick. They're the ones who spent their first twenty minutes on setup instead of jumping straight into a big task. That setup is what I call the Day-One Stack, and it's deliberately small - a plan, an app choice, and two files. Get those in place and Claude is useful in your first real session instead of your tenth.

If you're new, start with the Claude Code desktop app. I know the terminal has a reputation as the 'real' way to use it, and plenty of experienced developers live there. But for someone getting started, the desktop app removes a whole category of friction - no command-line syntax to learn before you've done anything useful, a real window to see your project and Claude's work side by side, and a much gentler on-ramp.

The terminal is not going anywhere. When you want it - for scripting, for speed, for fitting Claude into an existing command-line workflow - it's right there and you'll pick it up easily once you already understand what Claude Code does. But learning the tool and learning the terminal at the same time doubles the difficulty for no reason on day one. Pick the app, get a win, add the terminal later if you ever want it.

Don't agonize over the plan on day one. The 20-dollar Pro plan is the right starting point for nearly everyone - enough capability to do genuine work, cheap enough that it's not a real decision. People burn surprising amounts of energy trying to pick the perfect tier before they've built anything, which is exactly backwards. You can't know what you need until you've done real work, and Pro is more than enough to do that first real work.

This is the single highest-leverage thing a beginner can do, and almost nobody does it early. A CLAUDE.md is a plain text file in your project folder that Claude reads automatically at the start of every session. It's a standing brief - what the project is, what tools it uses, and the rules you care about. Write it once and every future session starts with Claude already oriented, instead of you re-explaining the basics each time.

The second file is about you, not the project. A short standing note of your preferences - how you like explanations, how much Claude should ask before acting, the tone you want - saves you from re-establishing the same things in every session. Do you want Claude to explain its reasoning or just do the task? Should it check with you before large changes or move fast? Write it down once and it applies going forward.

This is the difference between a tool that adapts to you and one you have to re-train daily. It doesn't need to be long. A handful of lines about how you like to collaborate is enough to make every session feel like Claude already knows how you work, because now it does.

With the Day-One Stack in place - app, plan, and two files - pick a small, real task, not a tutorial. Something you actually want done: add a feature to a side project, clean up a file, write a script you've been meaning to write. Small enough to finish in one session, real enough that finishing it teaches you something. That first real win is what turns Claude Code from a curiosity into part of how you work.