Most teams use Claude Code reactively — they type a prompt, Claude responds, they type another. That is fine, but it leaves significant value on the table. Claude Code has four automation layers that let you turn it from a reactive assistant into an active workflow participant: Layer What it does When to reach for it Hooks Shell or HTTP calls that fire on lifecycle events “This must happen every time, without exception” Custom Commands Reusable slash commands for repeatable prompts “I type the same prompt repeatedly” Skills Context-aware instructions Claude loads automatically “Claude should always do X when working on Y” Subagents Separate Claude instances for isolated, parallel work “This task is noisy and the main session only needs a summary” This post covers how to create each one and when to use them.