Private Access

Dave's Toolkit

Enter the code to continue

Step 1 of 12
Let's Get Started

Welcome to
Claude Code

~20 minutes. One command at a time. Copy, paste, move on.

  • Claude Code — AI that builds, edits, and manages projects for you
  • Browser preview — Claude can open web pages and show screenshots
  • GitHub — Google Drive for code, with version history
  • Starter prompt — best practices from day one

You don't need to understand the commands. Just copy and paste them.

01
Step 1

Open Terminal

Terminal is a built-in Mac app where you type commands.

  1. Press Cmd + Space
  2. Type Terminal
  3. Press Enter

You'll see a window with a blinking cursor (something like dave@MacBook ~ %). That's it.

Keep Terminal open for the rest of this guide. Paste commands with Cmd + V.
Can't find Terminal?

Alternative method: Open Finder → Go to Applications → Utilities → double-click Terminal.

Still stuck? Try clicking the magnifying glass icon in the top-right corner of your screen (that's Spotlight) and type "Terminal".

02
Step 2

What Kind of Mac?

Your Mac has one of two chip types. Copy and paste this into Terminal to check:

$ uname -m

What did you see? Click the one that matches:

arm64
Apple Silicon
(M1, M2, M3, M4 — most Macs from 2021+)
x86_64
Intel
(Macs from 2020 and earlier)
I see something different

Alternative way to check: Click the Apple menu (top-left corner of your screen) → About This Mac.

If it says Chip: Apple M1/M2/M3/M4 → click arm64 above.

If it says Processor: Intel → click x86_64 above.

03
Step 3

Install Homebrew

Homebrew is an app store for developer tools. Copy and paste this into Terminal:

$ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
It will ask for your Mac password. Nothing appears while you type — that's normal. Type it and press Enter.

Takes 1–5 minutes. Let it finish.

Apple Silicon only. After Homebrew finishes, paste each of these into Terminal (one at a time, press Enter after each):
$ echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
$ eval "$(/opt/homebrew/bin/brew shellenv)"

Now paste this to verify Homebrew installed:

$ brew --version
What you should see

Homebrew 4.x.x — any version number means it worked.

Something not working?

"command not found: brew" — If you're on Apple Silicon (arm64), make sure you ran the two extra commands above. If you already did, close Terminal completely (Cmd+Q) and reopen it, then try brew --version again.

A popup says "Install Xcode Command Line Tools" — Click "Install" and wait for it to finish (can take 5–10 min). Then run the Homebrew command again.

"Already installed" — Great! Skip to verification.

Password not working — It's your Mac login password (the one you use to unlock your computer). Remember: no characters appear while typing.

04
Step 4

Install Node.js

Claude Code needs Node.js to run. Paste this into Terminal:

$ brew install node

Takes ~1–2 minutes. Then paste this to verify:

$ node --version
What you should see

v20.x.x or higher — any version number means it worked.

Something not working?

"brew: command not found" — Go back to Step 3 and make sure Homebrew is installed.

"already installed" — Perfect. Skip to verification.

05
Step 5

Install Claude Code

The main event. Paste this into Terminal:

$ npm install -g @anthropic-ai/claude-code

~30 seconds. Then paste this to verify:

$ claude --version
What you should see

A version number like 1.x.x. Any number means success.

Something not working?

"EACCES: permission denied" — Try with admin privileges:

sudo npm install -g @anthropic-ai/claude-code

(It'll ask for your Mac password again.)

"npm: command not found" — Node.js didn't install properly. Go back to Step 4.

06
Step 6

Set Up Your Account

  1. Go to claude.ai → Sign up (or log in)
  2. Pick a plan:
Pro ($20/mo) — good to start
Max ($100/mo) — recommended for daily use
Max ($200/mo) — unlimited

Start with Pro. Upgrade anytime.

Now connect Claude Code to your account. Paste this into Terminal:

$ claude

Your browser will open — click Allow. Back in Terminal, you'll see a > prompt. Type exit and press Enter (we have a few more things to set up).

> exit
Something not working?

Browser didn't open — Look in Terminal for a URL. Copy it and paste it into your browser manually.

"not authenticated" error — Make sure you're logged in at claude.ai first, then try running claude again.

07
Step 7

Set Up GitHub

GitHub backs up your code and tracks every change. Create an account at github.com (free plan, personal email). Skip if you have one.

Then install the GitHub command-line tool. Paste into Terminal:

$ brew install gh

Now sign in. Paste this:

$ gh auth login

It asks a few questions. Choose: GitHub.com → HTTPS → Login with a web browser. Copy the one-time code, paste in browser, authorize.

Then paste this to verify:

$ gh auth status
What you should see

Logged in to github.com as your-username

Something not working?

It asks about "Enterprise" — Choose "GitHub.com" (the first option).

Browser didn't open — Copy the URL from Terminal and open it manually.

Two-factor authentication required — If you set up 2FA on GitHub, you'll need your authenticator app. Follow the prompts in the browser.

08
Step 8

Create Your Workspace

Create a folder for all your projects. Paste into Terminal:

$ mkdir -p ~/Desktop/Projects

A Projects folder now exists on your Desktop. Navigate into it:

$ cd ~/Desktop/Projects
No output? That's normal. In Terminal, silence means success. "No news is good news."

Every time you use Claude Code, start with cd ~/Desktop/Projects.

09
Step 9

Install Browser Preview

Lets Claude open a browser, preview websites, and take screenshots. Paste into Terminal:

$ claude mcp add playwright -- npx @playwright/mcp@latest
What you should see

A confirmation that the MCP server was added. Something like Added playwright MCP server.

That's it. The browser tool will be available automatically whenever you use Claude Code. No further setup needed.
Something not working?

"claude: command not found" — Go back to Step 5 and make sure Claude Code is installed.

Some error about npx — Make sure Node.js is installed (Step 4). Try: npx --version

10
Step 10

Configure Git

Tell Git who you are. Paste each command (use your own email for the second one):

$ git config --global user.name "David Mait"
$ git config --global user.email "your-email@example.com"
Use your GitHub email for the second command — the one you signed up with in Step 7.
11
Step 11

Your First Session

Everything's installed. Time to launch Claude Code.

1. Go to your Projects folder:

$ cd ~/Desktop/Projects

2. Start Claude Code:

$ claude

3. Customize your prompt below, then copy and paste it into Claude Code:

Starter Prompt Builder
Adjust these to personalize your setup. The prompt updates live.

4. Paste it into Claude Code (Cmd + V) and press Enter. Say y when it asks permission.

5. When it says setup is complete, you're ready.

Claude created a CLAUDE.md file with your preferences and tested the browser. Every future session in this folder follows those rules automatically.
12
Final Step

Get Your Websites

When Andres shares a GitHub repo with you, come back here. Enter the repo name and copy the prompt:

Website Setup Prompt
Enter the repo name Andres sends you.

How to use it:

  1. Open Terminal
  2. cd ~/Desktop/Projects
  3. claude
  4. Paste the prompt above and press Enter
Quick Reference

Day-to-Day Commands

Start Claude Code
cd ~/Desktop/Projects && claude
Start in a specific project
cd ~/Desktop/Projects/my-project && claude
Update Claude Code
npm update -g @anthropic-ai/claude-code
Get help inside Claude
/help
Start a fresh conversation
/clear
Cancel a running command
Ctrl + C
Exit Claude Code
exit
Pro tip: Just describe what you want in plain English. Claude will figure out the technical parts. For example: "Build me a one-page pitch deck website for our new ACO product" or "Create a competitive analysis spreadsheet of VBC platforms."
Workflow Guide

Using Claude & Gemini

Stellar uses Gemini because Google provides HIPAA compliance. Claude doesn't have that agreement. But Claude is significantly better for creative, strategic, and technical work. Here's how to use both safely.

The Simple Rule

Before typing anything into Claude, ask yourself: "Does this contain or reference a specific individual's health information?"

Does it contain PHI? Patient names, health records, member IDs, individual health outcomes
YES
Gemini Only Keep within Stellar's HIPAA workspace
NO
Claude is Fine Marketing, strategy, websites, public data
Not sure? → Use Gemini. Err on the safe side.

What Counts as PHI?

Protected Health Information is anything that identifies a specific person AND relates to their health:

  • Patient or member names, dates of birth, member IDs
  • Individual health records, diagnoses, treatment plans
  • Provider performance data tied to named providers and their specific patients
  • Member enrollment lists or claims data
  • Specific care outcomes for identifiable individuals

What's NOT PHI

  • Aggregated statistics (e.g., "our ACO saved $5M in Medicare")
  • Marketing copy about Stellar's products (no specific patients)
  • Industry research and competitive analysis
  • Public information about healthcare policy or VBC trends
  • Your own career strategy and planning
  • Website designs, pitch decks with de-identified examples
  • General go-to-market frameworks and messaging

At a Glance

Safe for Claude

  • Marketing strategy and messaging
  • Website and landing page design
  • LinkedIn posts and thought leadership
  • Competitive analysis of VBC platforms
  • Presentation templates and frameworks
  • Email copy and campaign strategy
  • Content writing (blogs, one-pagers)
  • Data analysis with aggregated numbers
  • Go-to-market playbooks

Must Use Gemini

  • Provider quality scorecards (named)
  • Member enrollment data or lists
  • Individual patient outcome reports
  • Claims data with identifiable info
  • Internal docs referencing specific cases
  • Provider panel details
  • Any screenshot of PHI-containing screens
  • Responses about specific patient panels

Handoff Patterns

The best workflow uses each tool for what it's best at. Here are three proven patterns:

Template on Claude, Fill on Gemini

Use Claude to build the structure and framework. Switch to Gemini to add real data.

Build a QBR presentation template on Claude (structure, messaging, design) → Open Gemini and say "Fill in the performance data from our Q4 results"

Strategy on Claude, Execution on Gemini

Use Claude for planning and creative work. Use Gemini for internal docs that reference real data.

Write marketing strategy and positioning on Claude → Draft internal launch brief with provider-specific data on Gemini

Clean Handoff

When moving work between tools:

Claude → Gemini: Copy Claude's output, open Gemini, paste with context: "Here's a framework I built. Continue this using our internal data about [topic]."

Gemini → Claude: Strip any PHI (names, IDs, specific health outcomes tied to individuals), then paste the de-identified content into Claude for refinement.

Real Examples

You're building a pitch for McLaren

On Claude: "Build me a strategic partnership brief for a large health plan. Include sections on VBC alignment, platform capabilities, and projected impact. Use a premium, data-driven design."

On Gemini: "Update this brief with McLaren's specific quality metrics and our actual performance data from the partnership."

You're writing a LinkedIn post

All on Claude: "Write a LinkedIn post about what I learned about provider incentives at Stellar. Make it personal and insightful, not corporate. Keep it under 200 words."

No PHI involved → Claude is perfect for this.

You're preparing a QBR deck

On Claude: "Create a QBR presentation template for a VBC company. Include: executive summary, performance metrics placeholder, growth pipeline, and next quarter strategy."

On Gemini: "Fill in the actual numbers from our Q4 data. Here are the metrics: [paste internal data]."

Why Both?

You might wonder: why not just use Gemini for everything?

Claude is significantly better at:

  • Building websites, presentations, and visual assets from scratch
  • Strategic thinking and nuanced marketing strategy
  • Writing that sounds human (not corporate AI-speak)
  • Following complex, multi-step instructions precisely
  • Code generation and technical implementation
  • Creative work that requires a distinctive voice

Gemini is better at:

  • Accessing Google Workspace data directly (Docs, Sheets, Slides)
  • Working within Stellar's HIPAA-covered environment
  • Quick lookups across your Google ecosystem

Use each for what it does best. The 30 seconds it takes to switch tools is worth the quality difference.