Project Kickoff
The complete checklist for going from zero to building. Follow these steps in order every time you start a new project.
The Kickoff Sequence
1. Create your project folder
Make a new folder for your project. This is where everything lives — code, assets, and configuration.
mkdir my-projectWhy: Every project gets its own folder. Keeps things organized and gives Claude Code clear boundaries for what it’s working on.
2. Start Claude Code
Open your terminal, navigate to the project folder, and launch Claude Code.
cd my-project
claudeWhy: Claude Code works within whatever folder you start it in. Starting it here means it knows this is the project root.
3. Create your CLAUDE.md
This is your project’s brain — the file Claude reads every time it starts a conversation. It tells Claude what you’re building, what tech you’re using, and how you want things done.
Pick a template from this section and fill it in, or ask Claude to help you write one.
See Your Project’s Brain for a full walkthrough of what goes in this file and why it matters.
Why: Without a CLAUDE.md, Claude starts every conversation with zero context. With one, it picks up exactly where you left off.
4. Add relevant skill files
Skill files give Claude specialized abilities — like knowing how to build a web app with proper responsive design, or how to set up a specific API integration. Drop the ones that match your project into the folder.
Browse available skill files at Skill Files.
Why: Skill files save you from repeating the same instructions every time. They encode best practices so Claude follows them automatically.
5. Write your first prompt
Now tell Claude what you’re building. Be specific about the outcome — what does the user see and do?
Copy this template, fill in the brackets, and paste it into Claude:
I want to build [type of app] that [main thing it does].
Platform: [macOS / iOS / web]
When you [main interaction], it should [main result].
Key features:
- [Feature 1]
- [Feature 2]
- [Feature 3 if applicable]
Keep it simple to start. We can add more later.Why: A clear first prompt gets you to working code faster. Vague prompts lead to back-and-forth. Specific ones lead to results.
6. Initialize git
Once Claude has created your initial files, set up version control so you can track changes and roll back if needed.
git init
git add .
git commit -m "Initial project setup"Why: Git gives you a safety net. If something breaks, you can always go back to a version that worked. Commit early, commit often.
First Prompt Examples
Menu Bar App
I want to build a macOS menu bar app that shows my next calendar event.
Platform: macOS
When you click the menu bar icon, it should show a small popover with:
- The event name
- Time until it starts
- A button to open the event in Calendar
Key features:
- Menu bar presence with icon
- Shows next event from Apple Calendar
- Updates automatically
Keep it simple to start. We can add more later.iOS App
I want to build an iOS app for tracking daily water intake.
Platform: iOS
When you open the app, it should show today's water intake and let you quickly add glasses.
Key features:
- Today view showing glasses consumed vs. goal
- Quick-add button (+1 glass)
- Simple history view
Keep it simple to start. We can add more later.Simple Utility
I want to build a macOS app that converts colors between formats.
Platform: macOS
When you paste a color (hex, RGB, or HSL), it should show the color and all format conversions.
Key features:
- Input field for pasting colors
- Visual preview of the color
- Copy buttons for each format
Keep it simple to start. We can add more later.Tips
- Start with the outcome — What does the user see and do?
- Be specific about the main interaction — “When you X, it should Y”
- Limit initial features — 3 is usually enough to start
- Say “keep it simple” — Explicitly ask for simplicity
- Let Claude ask questions — You don’t need to specify everything upfront
After the First Response
Claude will likely:
- Create the basic project structure
- Ask clarifying questions
- Show you initial code
From there, iterate:
- “Now add [next feature]”
- “The [element] should [adjustment]”
- “Can you make [improvement]”
The project develops through conversation.