antrix.dev
Free guide

Setting Up Claude & Claude Code

Get started with Claude for planning, writing, and building. Set up Claude Code for terminal-based development with AI.

Reading this alone?

Do it with peers — bi-weekly calls, $29/mo founding.

Join →

What it does

Claude is your AI development partner. It comes in two forms: Claude.ai is the web app for conversations, planning, brainstorming, and content work. Claude Code is a CLI tool that lives in your terminal — it reads your entire codebase, makes changes to files, runs commands, and iterates based on your feedback. Together, they cover every phase of building a product.

The range of tasks it handles is staggering. Architecture planning — describe what you're building and Claude maps out the pages, database schema, and API routes. Debugging — paste an error and it traces the root cause across your codebase. Code generation — describe a feature and it writes the implementation. Content writing — marketing copy, docs, email templates. Code review — it spots bugs, security issues, and performance problems. Refactoring — it restructures code while preserving behavior. Test writing — it generates test cases that cover edge cases you wouldn't think of. One tool, every phase.

Why we use it

Claude has the best reasoning of any AI model for code generation. It doesn't just autocomplete lines — it understands full project context, can plan architecture, write components, debug complex issues, review code for problems, and iterate based on your feedback. It's the difference between a spell-checker and a thinking partner. You describe what you want, Claude figures out how to build it, and you refine the result together.

Whole-codebase context is the key differentiator. Claude Code reads your entire project — every file, every import, every relationship between components. When it makes a change, it accounts for the full picture: how your database schema connects to your API routes, how your API routes feed your components, how your components share state. Autocomplete tools suggest the next line of code. Claude understands the whole system and makes changes that fit within it. That's the leap from AI assistance to AI collaboration.

Setup checklist

1

Create a Claude account

Go to claude.ai and sign up. Start with the Pro plan ($20/mo). Pro gives you extended thinking (Claude reasons through hard problems step by step), file uploads, project memory, and enough usage for daily building. If you find yourself hitting usage limits regularly, the Max plan ($100/mo) removes those caps. But start with Pro — you can always upgrade later.

2

Set up your first Claude Project

Projects give Claude persistent context across conversations. Click Projects in the sidebar, then Create Project. Name it after your product. Upload key documents — your README, architecture notes, brand guidelines, database schema, anything Claude should always know about. Every conversation inside this project will have access to those files. Create one project per major product you're building.

3

Learn conversation patterns

Be specific about what you want. Instead of “build me a dashboard,” say “build a dashboard page that shows monthly revenue, active users, and churn rate, using Recharts for the graphs.” Share screenshots for UI work — Claude can read images and match designs. Use “think step by step” for complex problems where you want to see the reasoning. Ask Claude to explain its choices. And always iterate — the first response is a strong starting point, not the final answer. Push back, refine, and the output gets dramatically better.

4

Install Node.js (required for Claude Code)

Claude Code runs on Node.js, so you need it installed first. The cleanest way is through nvm (Node Version Manager), which lets you switch between Node versions easily. Run: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash then open a new terminal window and run nvm install --lts. Verify it worked with node --version — you need 18 or higher.

5

Install Claude Code

Run npm install -g @anthropic-ai/claude-code in your terminal. This installs the claude command globally. You can now run it from any directory. If you get a permissions error, you may need to run with sudo or fix your npm global directory permissions (nvm avoids this issue).

6

Authenticate Claude Code

Run claude in any directory. The first time, it will open your browser and prompt you to log in with your Anthropic account. This links the CLI to your subscription — your Pro or Max plan covers both the web app and Claude Code usage. Once authenticated, you won't need to log in again.

7

Connect to your project

Navigate to your project directory in the terminal and run claude. It automatically indexes your codebase — it reads your file structure, understands your tech stack, and is ready to work. Ask it questions about your code: “What does the checkout flow look like?” Request changes: “Add a loading spinner to the submit button.” It edits files directly and shows you exactly what changed.

8

Learn key Claude Code patterns

Use /plan to have Claude think through complex tasks before writing code — this prevents it from going down the wrong path on big features. Ask “What does this file do?” to understand existing code before modifying it. Give feedback like “That's close but change X” to iterate — Claude remembers the conversation context and refines its approach. It edits files in place, runs your tests, and can even commit changes to git.

9

Set up a CLAUDE.md file

Create a file called CLAUDE.md in your project root. This is Claude Code's instruction manual for your project — it reads it automatically at the start of every session. Include your tech stack, coding conventions, environment setup instructions, common commands (how to run dev server, run tests, deploy), and things to avoid. The more specific your CLAUDE.md, the less you have to repeat yourself. Think of it as onboarding docs for your AI pair programmer.

10

Master the workflow

The most productive pattern: start each session with a clear goal. Use Claude.ai for research and planning first — hash out the approach, think through edge cases, decide on the architecture. Then switch to Claude Code for implementation — it works faster when the direction is clear. Review what it produces, give feedback, and iterate. Commit frequently so you can roll back if something goes wrong. Treat it like pair programming with a very fast colleague who never gets tired.

Pro tips

Split planning and implementation — use Claude.ai for brainstorming and planning, Claude Code for implementation. They complement each other perfectly.

Upload screenshots for visual debugging — Claude can read images and diagnose issues visually, which is faster than copying stack traces.

Break down stuck problems — when Claude gets stuck or goes in circles, give it more context or break the problem into smaller pieces. Focus beats scope.

Save prompts to CLAUDE.md — useful prompts become persistent instructions so you don't repeat yourself every session.

Sample CLAUDE.md for your project

# Project: [Your Project Name]

## Stack
- Next.js 16 (App Router)
- Supabase (PostgreSQL + Auth)
- Stripe (Payments)
- Tailwind CSS
- Vercel (Hosting)

## Conventions
- Use Server Components by default, "use client" only when needed
- All API routes in app/api/
- Environment variables in .env.local (never commit)
- Commit messages: feat:, fix:, chore:, refactor:

## Key Files
- lib/supabase.ts — Supabase client
- lib/stripe.ts — Stripe client
- config/site.ts — Site configuration

## Rules
- Always use RLS policies on Supabase tables
- Never expose STRIPE_SECRET_KEY to client code
- Run npm run build before pushing

AI prompt to get started

I'm starting a new project. Here's what I'm building: [describe your product]. Help me plan the architecture — what pages do I need, what's the database schema, what API routes, and what should I build first? Think through this step by step.

Mistakes to avoid

  • Using Claude as Google — give it context about YOUR project, don't ask generic questions you could search for
  • Not iterating — the first response is a draft, push back and refine to get dramatically better output
  • Dumping huge tasks without breaking them down — Claude works best with focused, clear requests, not "build me an app"
  • Forgetting to set up CLAUDE.md — without project context, Claude gives generic answers instead of ones tailored to your stack
  • Not reading what Claude produces — always review the code before committing, especially around security and data handling
  • Not using Claude Projects for persistent context — every new conversation starts from scratch without a Project. Upload your README and key docs so Claude remembers your setup

Reading this and want to actually do it with others?

The community is bi-weekly live calls, async accountability, and a group of builders shipping in parallel. Founding seats are $29/mo.

[ 01 ] the community · waitlist open

Build next to people who actually ship.

AI isn't going to make you money. Products do. Clients do. Real businesses do. AI is the unfair advantage — wire it into how you build, sell, and serve, and you move faster than everyone still doing it by hand.

operator:youwaitlist:openfleet:yours to installcalls:weekly liveprice:$29/mo founding

Is this you?

$ qualify --you

  • You live in Claude Code (or Codex) all day — and you're still the one doing every task, one prompt at a time.
  • You bill by the hour, and you can feel the ceiling. You want agents doing the repeatable work.
  • You're shipping your own thing — and want the whole business automated, not just the code.
  • You're senior and employed — and want this leverage running before your industry expects it.
  • You'd rather install the system than watch one more video about it.
  • Not for the make-money-online crowd. Not for day-one beginners. This is for people who already ship.

What you get

os/

Antrix OS — your fleet's control room

The system I run on real client work, installed where you build — not a video walkthrough.

Claude Code core MCP servers + hooks subagents + worktrees one dashboard

skills/

ax-* skill packs + installers

Drop-in capability. The packs and one-command installers that do the repeatable work.

  • ax-audit, ax-deliver, ax-simplify, ax-content
  • Ship Your Product — installer
  • Run the Machine — installer
  • Overnight pipelines: issues → PRs

setups/

Wired-up service setups

The integrations already configured the way production needs them.

  • Stripe — billing + webhooks
  • Supabase — auth + data
  • Vercel — deploy + edge
  • Resend — transactional email

access/

Direct access — to me and the network

When you're mid-build and stuck, you post and get an answer from someone who's shipped it.

  • Live working calls every week — builds, teardowns, Q&A
  • Architecture + payment reviews on your code
  • A peer network of operators who ship, not spectate
  • First look at overflow client work
Antrix OS — projects across every company, with live agents and open tasksAntrix OS — the agent roster: system agents, PMs, personas, and workers

← drag to explore the dashboard

The control room you'll run your fleet from — every project, agent, skill, schedule, and secret in one place. Members get the codebase.

$ fleet --ships

IG carousels, drafted overnightLead lists scraped for consultingClient reports + invoices, generatedContent research, done by morningOvernight PRs from open issuesWeekly ops digest, auto-assembled

[ 03 ] work with me directly

Hire me, and you get me — not an agency.

Don't want to run the fleet yourself — or need senior hands on your product now? I take a few clients each quarter, working direct on your codebase, your stack, your business. No junior handoffs, no account managers. Best fit if you're already shipping something real.

You're stuck on the hard part

We pair and ship it — the product, the agent, or the integration that's been blocking you — in the session, not in a follow-up doc.

AI is still just a chat window for you

I wire agentic workflows, multi-agent pipelines, and scheduled jobs into your business — turning AI from a tab you open into real leverage on revenue work.

You shipped it but you're not sure it holds

I review architecture, AI usage, and payments, then tell you what to keep, what to rip out, and what to ship next. Straight, no hedging.

You want to run it yourself

Sometimes you don't need me to run it — you need me in the room while you do. I set up the system and hand you the keys.

Specialty — payments & billing

If your product touches money, that's where I help most — subscriptions, marketplaces, and migrations at Babbel scale, Stripe-certified. Those engagements run through my consulting practice at invocation.io.

Tell me what you're building.

I reply within 24 hours.