👇 After this module

Your morning and evening protocols are running. Your energy is tracked. Your content rhythm is set. Your root system knows how you work.

Morning and evening protocols

A protocol is a sequence of steps your root system runs when you say a specific phrase. You design it once. It runs the same way every time. No willpower required, no forgetting steps.

Your morning protocol activates when you say "good morning" to your root system. It checks your calendar, reviews yesterday's notes, sets today's priorities, and checks in on your energy. All of this happens in the first two minutes of your work day, before you open a single tab or check your inbox.

Your evening protocol activates when you say "wrapping up." It logs what you accomplished, rates your energy for the day, captures any learnings worth keeping, and sets tomorrow's intention. This is how nothing falls through the cracks. Every day closes cleanly.

You design these once. Your root system runs them every day. They become your rhythm.

The beauty is that these protocols are yours to customize. Add a reflection question in the morning. Remove the calendar check if you prefer to look at it yourself. Add a gratitude prompt. Take out what does not fit. Your root system adapts to how you actually want to start and end your day.

The review gates that keep memory clean

In Module 2, you learned that nothing expires automatically. Claude has no internal timer. Memory stays clean because your protocols include review gates. Three gates run on schedule, and you do not have to remember any of them. They live inside your morning and evening protocol files.

The protocols already include these gates. You do not need to set them up by hand. Your morning and evening skill files run them at the right times. Your only job at each gate is to answer in plain language: keep, promote, delete, push to next week, still true, drifted.

If you are on Memory System v1.0 (set up before April 8, 2026), your skill files use a 30-day rule for scratchpads and a 2-week rule for learnings, and the review gates do not exist yet. The v2.0 update is a one-command upgrade and is documented on the Memory System v2.0 update page.

Energy and cycle tracking

Your root system can track anything you want to measure about your day. Energy on a scale of 1 to 10. Sleep quality. Whether you moved your body. How focused you felt. Your mood. This is the Body dimension of the Four Languages, and it is one of the most powerful parts of the system.

To set it up, you simply tell your root system what to track. That is it. No apps, no spreadsheets, no habit trackers with notification overload.

Your root system logs this data to your daily files. Over time, you start seeing patterns. Which days you have more energy. What affects your focus. Whether sleep quality correlates with productive days. Whether skipping movement shows up as lower energy two days later.

For those who want it, your root system can also track your cycle. This is completely optional. If it is relevant to you, it becomes another data point that helps you plan your weeks with more awareness.

You choose what to track. Start with one thing. Add more when it feels right. The goal is not to measure everything. The goal is to notice patterns you would otherwise miss.

The Four Languages check-in

The daily check-in is four questions, one for each language. It takes about two minutes. It keeps all four dimensions visible so none of them get quietly neglected.

Your root system asks these questions as part of your morning or evening protocol. You answer in plain language. "Energy is a 6, slept okay, going for a walk later." "Working on the sales page, need to email Sarah back." That is all it takes.

Over time, this daily check-in reveals something powerful: which languages get your attention and which get neglected. If you notice you always have a strong Mind answer but your Heart answer is "nothing this week," that is information. Not a judgment. Just something to notice.

The check-in is not a test. There are no right answers. It is a mirror that keeps all four parts of your life visible, even on busy days when it would be easy to let some of them disappear.

Your content rhythm

You have your morning and evening protocols. You are tracking your energy. Now add the third rhythm: content. Not a content strategy deck. Not a 90-day editorial calendar. A simple, repeatable weekly rhythm for creating and publishing content that sounds like you.

Step 1: Analyze what you already have

Before creating anything new, feed your existing content into your system. Blog posts, newsletters, social media posts, emails you are proud of. Your root system reads through everything and extracts your patterns: the themes you return to, the phrases that are uniquely yours, the tone that makes your writing feel like you.

Step 2: Refine your voice

Your system now has a voice profile. But it is a first draft. Run the voice refinement and give feedback. "Too formal." "I would never say that." "More like how I talk to a friend." Every correction sharpens how your system writes for you.

Step 3: Find your content pillars

Content pillars are the 3 to 5 themes you always come back to. Your content analysis already surfaced them. Now you make them explicit.

Your pillars are not a cage. They are a starting point. When you sit down to create and do not know what to write about, your pillars give you a direction. When you have too many ideas, your pillars help you filter.

Step 4: Build your content calendar

A content calendar is not a spreadsheet you fill in once and ignore. It is a weekly rhythm your root system helps you maintain. How many posts per week? Which platforms? Which days? What mix of pillars?

Step 5: Start your content vault

Ideas do not arrive on schedule. They come during walks, in the shower, at 2am. Your content vault catches them all so nothing gets lost.

Create and modify your own skills

By now you have used skills like /morning, /evening, and /content-analysis. You have seen how they work: you type a command, Claude reads the skill file, and follows the instructions inside it. Now you are going to learn how to write your own.

A skill is just a markdown file in .claude/commands/. That is it. There is no special syntax, no programming language, no configuration. You write instructions in plain English, save the file, and it becomes a command you can run.

What a skill file looks like

That is a complete skill. When you type /weekly-review, Claude reads this file and follows the steps. The filename becomes the command name. weekly-review.md becomes /weekly-review.

Your first custom skill

Think about something you do repeatedly. Something where you find yourself explaining the same thing to Claude every time. That is a skill waiting to be written.

Claude will interview you about what the skill should do, write the markdown file, and save it. You can test it immediately by typing the command.

Modifying existing skills

Your starter system came with skills that were built for a general user. They might not match exactly how you work. That is fine. You are meant to change them.

What makes a good skill

One rule: keep only what works

When you update a skill, delete the old version of the instructions. Do not keep both. Do not add "v2" sections. Do not write "what we tried before." One method per task. If the new way works, the old way is gone. This keeps your skills clean and prevents Claude from getting confused by contradictory instructions.