Claude Code, Day-to-Day (second edition)
Why this guide exists
You can use Claude Code every day and still miss what it added last month. You may never try the features that would help you most. Claude Code ships fast. This guide keeps you current, a few new techniques a day, so you do not get left behind and you use Claude Code the way it is meant to be used.
Who it is for
Claude Code, Day-to-Day (second edition) is a 28-day guide to Claude Code for developers who are new to it. The first edition stays at Claude Code, Day-to-Day (first edition).
How it works
You build one small project, Ticket Triage, across every day. Each day starts where the day before ended and takes 20 to 40 minutes. Start here is a real lesson that ends in a result you can check, such as a passing test. Going deeper holds the details and edge cases for when you have more time.
What you will learn
- Let
npm testrun without a prompt (Day 4). - Prove that a new session follows a CLAUDE.md rule (Day 5).
- Write a
/shipskill and run it (Day 10). - Format every edit with a hook (Day 11).
- Connect an MCP server and watch Claude call it (Day 13).
- Run two sessions in worktrees and merge one (Day 16).
- Run
claude -pfrom a script as a test gate (Day 24).
The 28 days fall into five stages: getting started (Days 1 to 3), control and context (Days 4 to 8), extending Claude Code (Days 9 to 14), parallel and remote work (Days 15 to 22), and automation and reference (Days 23 to 28).

How it was tested
Every Start here step ran live on macOS, in auto mode and in Manual mode. Days 1 to 22 ran on Claude Code 2.1.326, and Days 23 to 28 ran on 2.1.327. A step that was not run for this guide says so in the text.
Get the code
Day 1 builds Ticket Triage by hand. The code is in the ticket-triage-day-by-day repository on the claude-code-daily branch, with one tag per day, claude-code/day-00 to claude-code/day-28. Use a tag to catch up on any day.
Start
Start at Day 1, one part a day.
Also in this series: Cursor, Day-to-Day, OpenAI Codex, Day-to-Day, OpenCode, Day-to-Day, Pi, Day to Day, and GitHub Copilot, Day-to-Day.
The parts
- Install Claude Code, Then Make It Prove Its First Change
- Steer, Check, Rewind: The Four-Move Loop That Runs Your Whole Day in Claude Code
- The Cheapest Bug Fix Is the One You Make in a Plan
- Read Every Edit Claude Makes, and Never Approve npm test Again
- You Told Claude Yesterday. It Forgot. Put the Rule Where It Loads Every Time.
- Claude Is Not Getting Tired. Its Context Window Is Getting Crowded.
- Leave the Desk, Keep the Session: Claude Code Remote Control in One Tested Afternoon
- The Prompt That Types Itself: Running Your Tests Every Minute with Claude Code /loop
- I Measured What a Claude Code Subagent Costs, and on Small Files It Lost
- Stop Retyping the Same Prompt: Build a Tested /ship Skill in Claude Code
- Stop Asking Claude to Format Your Code: Make a Hook Do It Every Time
- Your Tests Pass. Claude Says It Is Fixed. Now Ask Who Checked the Fix.
- Did Claude Look It Up or Make It Up? Connect Your First MCP Server and Watch It Call
- Install a Claude Code Plugin and Prove It Loaded
- Move a Claude Code Session from the Terminal into the Desktop App
- Run Two Claude Code Sessions at Once, Then Keep Only One
- Let One Claude Code Session Message Another
- Give Claude Code a Finish Line with /goal
- Send a Message into a Running Claude Code Session from a Browser Tab
- Start a Claude Code Task from Your Phone and Check It at Your Desk
- Run Claude Code on a Schedule, Even with Your Computer Off
- Hand the Plan to a Script: Your First Claude Code Dynamic Workflow
- Stop Pasting Scrollback: Publish Your Claude Code Test Report as an Artifact
- Make Claude Code Fail the Build: Headless claude -p as a Test Gate
- Let the Exit Code Decide: Build a Claude Code Retry Loop Around a Test Gate
- One Ticket In, One Reviewed Branch Out: Build a Software Factory with Claude Code
- The Mistakes That Break Nothing Today: A Claude Code Pitfall Checklist
- Look Up Any Claude Code Term Three Ways: The Glossary, /help, and the Docs Server