Claude Code, Day-to-Day (second edition)

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 test run without a prompt (Day 4).
  • Prove that a new session follows a CLAUDE.md rule (Day 5).
  • Write a /ship skill 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 -p from 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).

Claude Code, Day-to-Day (second edition) roadmap: Getting started, Day 1 Install Claude Code, Day 2 The daily loop and Day 3 Plan before you code. Control and context, Day 4 Permissions and auto mode, Day 5 Memory that loads every time, Day 6 What Claude can see, Day 7 Remote Control and Day 8 Scheduled tasks. Extending Claude Code, Day 9 Subagents, Day 10 Skills, Day 11 Hooks, Day 12 Verification, Day 13 MCP and Day 14 Plugins. Parallel and remote work, Day 15 Where Claude Code runs, Day 16 Worktrees, Day 17 Parallel sessions, Day 18 Autonomous runs, Day 19 Channels, Day 20 Dispatch and Claude Tag, Day 21 Routines and Day 22 Team scale. Automation and reference, Day 23 Share results, Day 24 Headless Claude Code, Day 25 Loop engineering, Day 26 The software factory, Day 27 Pitfalls and personas, Day 28 Reference and glossary.

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

  1. Install Claude Code, Then Make It Prove Its First Change
  2. Steer, Check, Rewind: The Four-Move Loop That Runs Your Whole Day in Claude Code
  3. The Cheapest Bug Fix Is the One You Make in a Plan
  4. Read Every Edit Claude Makes, and Never Approve npm test Again
  5. You Told Claude Yesterday. It Forgot. Put the Rule Where It Loads Every Time.
  6. Claude Is Not Getting Tired. Its Context Window Is Getting Crowded.
  7. Leave the Desk, Keep the Session: Claude Code Remote Control in One Tested Afternoon
  8. The Prompt That Types Itself: Running Your Tests Every Minute with Claude Code /loop
  9. I Measured What a Claude Code Subagent Costs, and on Small Files It Lost
  10. Stop Retyping the Same Prompt: Build a Tested /ship Skill in Claude Code
  11. Stop Asking Claude to Format Your Code: Make a Hook Do It Every Time
  12. Your Tests Pass. Claude Says It Is Fixed. Now Ask Who Checked the Fix.
  13. Did Claude Look It Up or Make It Up? Connect Your First MCP Server and Watch It Call
  14. Install a Claude Code Plugin and Prove It Loaded
  15. Move a Claude Code Session from the Terminal into the Desktop App
  16. Run Two Claude Code Sessions at Once, Then Keep Only One
  17. Let One Claude Code Session Message Another
  18. Give Claude Code a Finish Line with /goal
  19. Send a Message into a Running Claude Code Session from a Browser Tab
  20. Start a Claude Code Task from Your Phone and Check It at Your Desk
  21. Run Claude Code on a Schedule, Even with Your Computer Off
  22. Hand the Plan to a Script: Your First Claude Code Dynamic Workflow
  23. Stop Pasting Scrollback: Publish Your Claude Code Test Report as an Artifact
  24. Make Claude Code Fail the Build: Headless claude -p as a Test Gate
  25. Let the Exit Code Decide: Build a Claude Code Retry Loop Around a Test Gate
  26. One Ticket In, One Reviewed Branch Out: Build a Software Factory with Claude Code
  27. The Mistakes That Break Nothing Today: A Claude Code Pitfall Checklist
  28. Look Up Any Claude Code Term Three Ways: The Glossary, /help, and the Docs Server