
Build
Something
Three guides. Real commands. Working results. Start at the top and work down, or jump to what you need.
Set Up Your AI Agent
We'll set up Claude Code — Anthropic's agentic coding tool. It runs in your terminal, reads your entire codebase, and writes real code. You need Node.js 18+ and an Anthropic API key.
brew install nodeOn macOS with Homebrew. For other systems, visit nodejs.org.
npm install -g @anthropic-ai/claude-codeexport ANTHROPIC_API_KEY=sk-ant-your-key-hereGet your key from console.anthropic.com. Add this to your shell profile (~/.zshrc or ~/.bashrc) to persist it.
cd your-project && claudeThat's it. The agent starts, reads your project, and waits for instructions.
"Read the README and summarize what this project does"Start simple. As you build trust, give it bigger tasks: "Add a dark mode toggle", "Write tests for the auth module", "Refactor this component to use hooks".
The agent learns your codebase as it works. It reads files, checks types, runs tests. It's not generating code in a vacuum — it's working inside your project.
Install & Use Skills
Skills give your agent specialized capabilities. A skill for deployment knows the exact steps. A skill for testing knows the framework conventions. Skills are loaded on demand — they don't bloat your agent when unused.
James walkthrough
Install your first skill
A voiced Remotion walkthrough using James's ElevenLabs clone — one outcome, one skill, one live operator loop.
~/.claude/skills/ — Global skills, available in every project
.claude/skills/ — Project-local skills, scoped to this repo
# ~/.claude/skills/deploy.md
---
name: deploy-to-vercel
description: Deploy the current project to Vercel
---
When asked to deploy, run `npx vercel --prod`.
Confirm the deployment URL with the user.
If it fails, check for build errors first.
/deployType the slash command in Claude Code. The agent loads the skill and follows its instructions. You can also just say "deploy this project" and the skill activates by matching the trigger.
Community skills are markdown files you download and drop into your skills directory. Browse curated collections, copy the file, and the capability is available immediately.
Good skills are specific and opinionated. "Deploy to Vercel" is better than "deploy anywhere". The specificity is what makes the agent reliable.
Connect MCP Servers
MCP servers give your agent access to external tools — databases, APIs, browsers, file systems. Once connected, the agent can use these tools as naturally as reading a file.
claude configOr edit ~/.claude/settings.json directly.
{
"mcpServers": {
"github": {
"command": "npx",
"args": [
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_TOKEN": "ghp_your_token"
}
}
}
}Exit and re-launch Claude Code. It discovers MCP servers on startup. You'll see the server's tools listed in the available tools.
"List my open pull requests on this repo"The agent calls the GitHub MCP server's tools automatically. No special syntax needed — just describe what you want.
Popular MCP servers to add:
filesystem — Read/write files outside the project
postgres — Query and manage databases
supabase — Full Supabase platform access
browserbase — Cloud browser automation
Each MCP server you add expands what your agent can do. Start with one or two and add more as you need them. The configuration is the same pattern every time.