All Days
Day 32

The Claude Code Playbook

Playbook / 30 Days / Claude Code

Claude Code: Zero to Operating System

30-day progression from first install to running sales, content, outreach, and engineering from one terminal. Each day builds on the last.

Walid Boulanouar  |  AY Automate  |  2026

10
levels
30
days
59+
skills
1
terminal
Foundation
LEVEL 0Install + First SessionDays 1–3

Install Claude Code, run your first session, understand how it differs from claude.ai. Terminal-native AI with full codebase access and real file editing.

Content Angle

"I gave Claude Code access to my entire codebase. Here's what happened."

"90 seconds. That's how long it took Claude to understand a 50k-line project."

Key Concepts

  • Terminal-native AI
  • Full codebase access
  • Real file editing (not suggestions)
  • Git-aware out of the box

Build Examples

  • First commit made entirely by Claude Code
  • Codebase architecture review
  • Automated bug fix from error log
# Install
npm install -g @anthropic-ai/claude-code

# Open a project and start
cd your-project && claude

# Ask it to explain the architecture
> Explain this project's architecture. Read every file you need.

Do This

Install Claude Code. Open a project. Ask it to explain the architecture. Watch it read every file. Then ask it to make a small fix and commit it.

Tools:TerminalVS Code / CursorGit
Foundation
LEVEL 1CLI MasteryDays 4–6

Plan mode, extended thinking, ultrathink, piping, permission modes. Most people use 1% of what the CLI can do.

Content Angle

"Most people use 1% of Claude Code's CLI. Here's the other 99%."

"Type 'ultrathink' in any Claude prompt. Watch what happens."

Key Concepts

  • Plan mode: think before executing
  • Extended thinking / ultrathink
  • Piping output into Claude
  • Permission modes (yolo, ask, deny)

Build Examples

  • Pre-commit AI linter
  • Real-time log anomaly detector
  • Build script with AI quality gate
# Pipe logs through Claude for real-time analysis
tail -f /var/log/app.log | claude -p "alert me on errors above WARN"

# Use plan mode for complex tasks
> /plan Refactor the auth system to use JWT refresh tokens

# Extended thinking on architecture decisions
> ultrathink: Should we use a monorepo or separate repos?

Do This

Try plan mode on your next complex task. Use ultrathink for architecture decisions. Pipe your test output through Claude and ask it to summarize failures.

Tools:ShellGit hooksstdin/stdout pipes
Context
LEVEL 2Memory ArchitectureDays 7–9

CLAUDE.md hierarchy, MEMORY.md auto-persistence, rules files. The 4-layer memory system that makes Claude Code remember everything.

Content Angle

"Claude has memory. Here's how to actually use it."

"I tell Claude three things in CLAUDE.md and it never makes those mistakes again."

4-Layer Memory System

  • ~/.claude/CLAUDE.md (global identity)
  • project/CLAUDE.md (project rules)
  • .claude/rules/*.md (path-scoped)
  • MEMORY.md (auto-persisted learnings)

Build Examples

  • Personal AI identity system
  • Client context auto-loader
  • Monorepo path-scoped rules
# ~/.claude/CLAUDE.md -- global identity
I am Walid. I build AI automation systems.
Never use emojis. Always be direct. Code in TypeScript.

# project/CLAUDE.md -- project-specific rules
This is a Next.js 15 app using App Router.
Database: Supabase. Auth: Clerk.
Always use server components by default.

# .claude/rules/api.md -- path-scoped (src/api/**)
All API routes must validate input with Zod.
Always return consistent { data, error } shape.

Do This

Create your first CLAUDE.md. Tell it who you are, how you code, what to avoid. Watch consistency improve immediately. Then add one rules file scoped to your API directory.

Tools:CLAUDE.md.claude/rules/MEMORY.md
Context
LEVEL 3Context EngineeringDays 10–12

@-imports, custom instructions per file type, context window management. The most important AI skill nobody teaches.

Content Angle

"Context engineering is the most important AI skill nobody teaches."

"I import my client list, API spec, and style guide into every session automatically."

Key Concepts

  • @-imports: load live data into context
  • Scope rules to file path globs
  • Token budget management
  • Dynamic context from external files

Build Examples

  • Auto-loading API specs per directory
  • Dynamic context from databases
  • Smart context pruning strategies
# In CLAUDE.md -- reference external files
@clients/active-clients.md
@api/openapi-spec.yaml
@brand/style-guide.md

# .claude/rules/frontend.md -- scoped to src/components/**
Always use our design system tokens from @brand/tokens.ts
Follow the component pattern in @docs/component-guide.md
Never inline styles. Use Tailwind classes only.

Do This

Create 3 rules files scoped to different parts of your codebase. Watch Claude behave differently in each directory. Import one external reference file and see it used in context.

Tools:@path imports.claude/rules/ with globsContext window
Automation
LEVEL 4Custom Slash CommandsDays 13–15

Build your own /commands, parameterized prompts, skill creator. Turn repetitive workflows into one-word triggers.

Content Angle

"I type /proposal and Claude generates a full client proposal in 30 seconds."

"6 commands replaced 6 hours of weekly manual work."

Key Concepts

  • Reusable workflows as commands
  • Argument passing with $ARGUMENTS
  • Command chaining
  • Shared vs personal commands

Build Examples

  • /content — LinkedIn posts in your voice
  • /proposal — Client proposals with ROI
  • /sop — Standard operating procedures
  • /client-prep — Meeting preparation
# .claude/commands/content.md
Generate a LinkedIn post about: $ARGUMENTS

Rules:
- Use my voice from @CLAUDE.md
- 1000-1300 characters max
- Include specific metrics
- End with a clear CTA
- No emojis. No fluff. No corporate speak.

# Usage:
> /content how we saved a client 20 hrs/week with one workflow

Do This

Identify one thing you do every week. Turn it into a /command. Measure time saved. Then build two more. The compound effect is immediate.

Tools:.claude/commands/$ARGUMENTS
Automation
LEVEL 5Hooks SystemDays 16–18

Pre/post tool hooks, notification hooks, automated guardrails. The invisible layer that makes everything safe and observable.

Content Angle

"Claude Code hooks: the feature that makes everything else 10x more powerful."

"I set up a hook that prevents Claude from ever committing secrets. Took 2 minutes."

Key Concepts

  • Run scripts before/after Claude acts
  • Enforce rules automatically
  • Pre-tool and post-tool hooks
  • Notification on file changes

Build Examples

  • Pre-commit security scan
  • Auto-notification on file changes
  • RTK token optimization hook
  • Auto-format on save hook
# .claude/settings.json -- hook configuration
{
  "hooks": {
    "PreToolUse": [{
      "matcher": "Bash",
      "command": "bash .claude/scripts/check-secrets.sh \"$INPUT\""
    }],
    "PostToolUse": [{
      "matcher": "Write|Edit",
      "command": "bash .claude/scripts/notify-change.sh \"$FILEPATH\""
    }]
  }
}

Do This

Add one hook: a post-commit notification that tells you what Claude changed. Start small. Then add a pre-tool hook that blocks dangerous commands. Build guardrails, not gates.

Tools:settings.jsonShell scriptsPreToolUse / PostToolUse
Integration
LEVEL 6MCP ServersDays 19–21

Connect Claude to external APIs — CRM, LinkedIn, email, Slack. The Model Context Protocol gives Claude Code hands to touch the real world.

Content Angle

"Claude Code just got hands. MCP servers let it touch the real world."

"Claude just sent a Slack message, updated my CRM, and drafted a LinkedIn post. In one command."

Key Concepts

  • Model Context Protocol (MCP)
  • Tool bridging to external APIs
  • API orchestration from terminal
  • Read vs write action safety

Build Examples

  • Attio CRM integration
  • Unipile LinkedIn API
  • Apollo lead enrichment
  • Framer web publishing
# .mcp.json -- server configuration
{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": ["-y", "@anthropic/mcp-slack"],
      "env": { "SLACK_TOKEN": "xoxb-..." }
    },
    "attio": {
      "command": "node",
      "args": [".claude/skills/mcp-client/scripts/attio_server.mjs"]
    }
  }
}

# Now Claude can:
> Post this update to #engineering in Slack
> Add this prospect to Attio with source "LinkedIn DM"

Do This

Connect one MCP server. Start with Slack or your CRM. Watch Claude start taking real actions in the tools you already use. Then connect a second one and chain them together.

Tools:MCP servers.mcp.jsonSlack / Attio / Apollo
Integration
LEVEL 7Custom SkillsDays 22–24

Full skill system — SKILL.md, references/, scripts/, multi-step workflows. Skills are reusable capabilities with their own knowledge base and tools.

Content Angle

"Skills are Claude Code's superpower. Here's how to build one in 10 minutes."

"59 custom skills. Each one replaced a SaaS tool or a manual process."

Skill Structure

  • SKILL.md — capability definition
  • references/ — knowledge base
  • scripts/ — executable tools
  • Triggers and conditions

Build Examples

  • carousel-maker (LinkedIn carousels)
  • cold-dance (outreach sequences)
  • post-to-pipeline (lead gen)
  • nano-banana (image generation)
# .claude/skills/carousel-maker/SKILL.md
## Carousel Maker

Trigger: User asks for a LinkedIn carousel or slide deck.

Steps:
1. Extract key points from the input
2. Structure into 8-12 slides
3. Apply brand identity from references/brand-identity.md
4. Generate HTML slides with export.py
5. Preview and iterate

References: brand-identity.md, slide-patterns.md
Scripts: export.py, preview.py

Do This

Create your first skill. Pick something you do manually at least once a week. Give it a SKILL.md, one reference file, and one script. Then use it on a real task and iterate.

Tools:.claude/skills/SKILL.mdPython / Node scripts
Orchestration
LEVEL 8Agents + Multi-AgentDays 25–27

Subagent system, background agents, parallel execution, worktrees. Specialized agents for different tasks running concurrently.

Content Angle

"I launched 4 agents in parallel. They finished in 3 minutes what would take me 2 hours."

"prospect-researcher, content-writer, security-auditor, fullstack-developer — all running at once."

Key Concepts

  • Specialized agent definitions
  • Concurrent execution
  • Background tasks
  • Agent isolation with worktrees

Build Examples

  • Prospect research + content gen in parallel
  • Multi-agent code review
  • Background monitoring agent
  • Security audit while you build
# .claude/agents/prospect-researcher.md
## Prospect Researcher

You are a prospect research agent. Your job:
1. Take a company name or LinkedIn URL
2. Research: team size, funding, tech stack, pain points
3. Score against our ICP (10-80 employees, ops-heavy)
4. Output a structured brief to 01_Projects/Clients/Prospects/

You have access to: Apollo MCP, web search, Attio CRM.
You do NOT: send messages, modify CRM records, or contact anyone.

# Launch multiple agents
> Run prospect-researcher on "Acme Corp" in background
> Run content-writer on "AI agents for logistics" in background
> Run security-auditor on the auth module in background

Do This

Define 3 agent types for your workflow. Give each a clear scope and explicit boundaries on what it can and cannot do. Run them on a real task. Watch the parallel execution.

Tools:.claude/agents/Agent toolrun_in_backgroundWorktrees
Orchestration
LEVEL 9Full Operating SystemDays 28–30

Everything connected. The second brain as a business OS. Git-controlled knowledge base with Obsidian, PARA method, daily workflows, compound automation.

Content Angle

"This is not a coding assistant anymore. This is how I run my entire business."

"59 skills. 36 commands. 12 agents. 9 MCP servers. One terminal."

The Full Stack

  • Second brain (Obsidian + Git)
  • Claude Code (orchestration layer)
  • MCP servers (external APIs)
  • Skills, Agents, Hooks — all connected

Build Examples

  • Daily command center (cockpit)
  • Content-to-pipeline automation
  • Full client onboarding in one command
  • Automated prospect qualification
# The architecture
Second Brain (PARA + Obsidian + Git)
    |
Claude Code (orchestration layer)
    |
    +-- 59 Skills     (capabilities)
    +-- 36 Commands   (workflows)
    +-- 12 Agents     (specialists)
    +-- 9 MCP Servers  (external APIs)
    +-- 7 Hooks       (guardrails)
    |
Output: Sales, Content, Outreach, Engineering, Ops
    |
One terminal. One brain. One system.

Do This

Map your entire workflow. Identify what's still manual. Build a skill for each manual step. Connect via MCP. Define agents for parallel work. Run it all from one terminal. You have an operating system.

Tools:Everything

Claude Code vs Traditional AI Tools

Why Claude Code is a different category entirely.

FeatureIDE PluginsClaude.aiClaude Code
File accessCurrent fileNoneFull codebase
MemorySession onlySession onlyPersistent (CLAUDE.md)
AutomationNoneNoneHooks + Commands
External APIsNoneNoneMCP Servers
Custom skillsNoneNoneFull skill system
Multi-agentNoneNoneParallel agents
Git integrationBasicNoneFull git-aware
Real file editingSuggestionsNoneDirect read/write/edit

don't miss what's next.

playbooks, templates, and tools that actually save you hours. straight to your inbox. no spam. unsubscribe anytime.

Start your 30-day journey today.

Day 1: Install Claude Code. Day 30: Run your business from a terminal.

$ npm install -g @anthropic-ai/claude-code
Day 1 InstallDay 15 AutomateDay 30 Operate
Day 32  ·  AY Automate  ·  Claude Code Series