Claude Terminal Launch Checklist

Reference Sheet

npm install
npm run dev

The fix loop:

Reproduce bug locally →

Read console/terminal error →

Fix code →

Hot reload auto-applies →

Verify fix →

git push →

Vercel auto-deploys

Before pushing to vercel, run
npm run build
This catches 80% of vercel failures in advance

Claude Code Session Checklist

Run through this checklist at the start of every Claude Code session to ensure your environment, stack connections, and project context are fully aligned before work begins.

1. Project Setup

cd project root

Navigate to your working repository.

cd /path/to/project-root

verify directory

Confirm you are in the correct location.

pwd
ls

2. Launch Claude

start claude

Launch Claude Code inside the project.

claude

skip permissions (optional)

Launch Claude without permission prompts (advanced use only).

claude --dangerously-skip-permissions

enable voice mode

Enable spacebar voice dictation for faster interaction.

/voice

3. Git + Environment Checks

git status

Verify branch, changes, and repo state.

git status
git branch --show-current
git remote -v

github auth

Confirm GitHub CLI access.

gh auth status

runtime check

Confirm correct runtime versions.

node -v
npm -v
python --version

4. Stack Connections

vercel setup

Confirm Vercel project linkage.

vercel login
vercel link

vercel plugin

Enable Claude + Vercel integration.

npx plugins add vercel/vercel-plugin

supabase setup

Confirm Supabase CLI access.

supabase login
supabase status

5. Run Project

start dev server

Run the project locally before making changes.

npm run dev

6. Claude Kickoff Prompt

initial context prompt

Have Claude analyze the repo before starting work.

Review this repository and summarize:
- tech stack
- structure
- environment dependencies
- missing setup items