Guide

Your first projectwith Claude Code.

Pick a small goal, set up git, and check each result. This is the order that avoids the usual first week mess.

// the steps

Six steps

01 Pick one small goalChoose something you can finish in a day: one page, one script, one tool. Write the goal in a sentence and what done looks like.
02 Make a clean folder with gitCreate a new folder and run git init before the first prompt. Commit the empty start so you can always get back to it.
03 Describe the job, not the codeSay who it is for and what it must do. Leave out implementation unless you have a firm preference.
04 Work in small stepsAsk for one change at a time. Read what changed after each, and commit when it works. Small commits are your undo.
05 Run it and look at itOpen the result yourself. Click the buttons, resize the window, break the input. Do not rely on the AI saying it works.
06 Keep a notes fileWrite down what you decided and what is left. The next session starts blank, and a short file brings it up to speed.
// with adams

Where Adams fits

Free guards from the first commitLiteInstall Adams Lite once and your first project has secret, git and leak guards from the start. Run adams doctor to check the setup.
// faq

Questions

Do I need to know how to code?

You need to read what changes and run the result. You do not need to write the code, but you do need to check it.

What should the first project be?

Something small with a clear end, such as a landing page or a simple tool for yourself.

When should I commit?

Whenever the project works after a change. Frequent commits make mistakes cheap.

// related

Keep reading