AI Automation: Start Here

Let me read it first.Got it. Writing it now.

Up to this point every session with Claude Code starts when you open it and ends when you close it automations change the ratio

Every session with Claude Code starts when you open it and ends when you close it. You prompt. Claude responds. You are the engine.

Automations change the ratio.

An automation is a workflow that runs itself, triggered by a schedule, an event, or a single command, so Claude does the repetitive work while you focus on the work that actually needs your judgment.

This course teaches you how to build them.

What Automations Look Like in Practice

Here are real examples from what builders in this community are doing.

The morning brief runs every day at 9am. Claude Code reads your project folders, checks your task list, reads any new files you added, and generates a 5-minute brief on what needs to happen today. You open your laptop and the brief is already there.

The content batch runs once a week when you run one command. Claude reads your MARKETING.md, pulls three topics from your backlog, and generates a full week of social content, subject lines, and one newsletter draft. The whole batch takes 8 minutes.

The project kickoff triggers every time you create a new project folder. Claude automatically reads it, generates a CLAUDE.md, a project brief, and a suggested task breakdown. The project is already organised before you type your first real prompt.

The end-of-session save triggers every time you stop a Claude Code session. It automatically writes a summary of what was done, what decisions were made, and what should happen next into a progress.md file in your project.

None of these require you to remember to do them. They run on their own.

What You Will Learn

How custom slash commands work and how to turn any prompt into a one-word command.

How Claude Code hooks work and how to trigger actions automatically when something happens.

How to build the morning brief automation.

How to build a content batch workflow.

How to build a project kickoff system.

How to combine everything into a personal automation stack that runs in the background.

What You Need Before Starting

Claude Code installed as the Desktop App or Terminal. Skills and MCPs from the previous course with at least the fetch MCP installed. And familiarity with CLAUDE.md from the memory course.

One Important Concept First

Automations in Claude Code fall into two categories.

Prompt automations are structured prompts that do a complex multi-step job when you run them. You trigger them manually but they do the heavy lifting. Custom slash commands live here.

Event automations which are hooks are instructions Claude Code follows automatically in response to something happening: you starting a session, you stopping a session, or Claude using a specific tool. These run without you typing anything.

Both are useful. This course covers both.

Your Action Right Now

Think about one thing you do regularly with Claude Code that follows the same pattern every time. Something you have done at least three times in the last month using similar prompts each time.

That is your first automation candidate. Write it down. You will turn it into a slash command before the end of this course.