Module 1 · Kick off the build

The kickoff prompt

Now it comes alive. You are going to paste one prompt into Claude. It reads the kit, checks that every part arrived, starts keeping snapshots of your work, and tells you the whole plan back in its own words — then stops and waits for you.

Paste this into Claude

With your my-firm-website folder open on the Code tab and the kit dropped in, paste this and press Return:

You're going to help me build and launch a complete website for my law firm, step by step, over
several sessions. I'm an attorney, not a technical person, so keep everything in plain English and
do the technical parts for me.

To start:
1. Read your CLAUDE.md. Then look in the .claude/skills folder and LIST the six skills by name with
   a one-line purpose for each (brand-strategy, web-architecture, copywriting, frontend-design,
   compliance-check, deploy). If any of the six is missing, tell me plainly which one and stop, so
   I can fix it before we go any further.
2. Set up a clean starting point: initialize Git in this folder and make a first commit, so my work
   is saved from here on. We'll build the actual website in a later stage — for now just get the
   project ready.
3. In plain language, tell me back the 7 stages we'll go through together, so I know the plan.
4. Then stop and wait. I'll come back from the next course module and tell you when to begin.

What Claude will do

• Confirm it can see your CLAUDE.md and name all six skills back to you.
• Set up Git and save a first snapshot of your currently-empty project.
• Explain the seven stages in plain English.
• Stop, and wait for you. It will not start building on its own.

If it lists six skills and then pauses, everything worked. If it names five, or says one is missing, go back a lesson — the kit landed in the wrong place. That check is exactly why the prompt asks for the count.

The seven stages you are about to walk

Here is the plan the kit teaches Claude, so you can see it before Claude recites it. Stages 1 to 7 are Modules 2 to 8 of this course — one stage per module — and then one short module to get the firm found.

Snapshots, and why you can experiment fearlessly

A snapshot is a saved copy of your entire project at one moment — the kit tells Claude to take one at the end of every stage and before anything risky. You do not have to ask for them and you do not have to manage them. What matters is the consequence: if a change makes the site worse, you can always go back to a version that worked. Nothing you do here is permanent unless you want it to be.