Working With Claude Code

# Working With Claude Code Claude Code is an AI that works inside your project. It reads your files, runs commands, opens your app in a browser and writes code. Your job changes from typing code to deciding what gets built and checking that it was built right. You won't start from a blank folder. The [Braintied starter](https://github.com/braintied/idea-to-mvp) is a working app: a landing page with a waitlist, sign-in, a CRM, AI follow-ups and a daily email digest. Today you make it yours. ## Get the starter On GitHub, open `braintied/idea-to-mvp`, press **Use this template**, and create your own repository. If you made it private, sign Terminal in to GitHub first (`gh auth login`, or GitHub Desktop), or the clone stops at a username prompt. Clone it, then in the folder: ```bash pnpm install cp .env.example .env.local ``` Open the folder in Claude Code. Say yes when it asks to trust the folder, install the **braintied** plugin and turn on the MCP servers. Then send your first message. Something like: > Read CLAUDE.md and docs/architecture.md, then explain this app to me in five sentences. To complete this lesson, press **Start free** on the course page, run `npx @braintied/academy login`, then `npx @braintied/academy signal claude_code_first_message`. Or tell Kit you sent your first message. ## Six habits **1. CLAUDE.md is its memory.** Claude reads it at the start of every session. It holds your idea, your brand and your rules. When Claude makes the same mistake twice, add a line. **2. Plan before building.** Press Shift+Tab for plan mode. Claude researches and proposes without changing anything. Read the plan, push back, then approve. Most bad results come from skipping this. **3. Small steps, checked.** One feature at a time. After each one, `pnpm check` passes and you see it working in the browser. **4. Skills are saved know-how.** Type `/design`, `/explain`, `/next`, `/ship-it`. They come from the Braintied plugin and improve without you doing anything. **5. Subagents are specialists.** The repo ships a `planner`, a `reviewer` and a `designer`. Ask for one by name. **6. Hooks and MCP are guardrails and tools.** Hooks stop Claude from reading your keys. MCP servers let Claude look at your database, read current library docs and open your app in a browser. ## Your idea, in one paragraph Ask Claude to interview you: > Interview me about my idea, two questions at a time, then fill in "The idea" in CLAUDE.md. Push for specifics. "Everyone" is not a customer. "A yoga teacher in Goa with 40 regulars" is. ## Go deeper - In your repo: `docs/learn/01-claude-code.md` - On Academy: Build a Real App, lessons 2 to 4 (installing Claude Code, CLAUDE.md, skills) - Ask Kit on Telegram, or type `/explain plan mode` in Claude Code