Claude Code Skills Made Easy: One Prompt to Build Your Productivity System

By the end of this article, you'll paste one block into Claude Code and have a working system that runs your mornings, evenings, and weekly reviews. No coding required.

Okay, so you’ve been using Claude Code for a minute now. Maybe you organized some files. Maybe you built some context docs. Maybe you just tested it on your Downloads folder and felt feelings about it.

(Valid.)

But here’s what probably happened after a few sessions: you kept explaining the same stuff. “Here are my goals.” “Here’s how I like my tasks organized.” “Remember that thing I told you yesterday?”

Claude Code doesn’t automatically remember your instructions unless you save them somewhere for it to check again and again. New sessions don’t carry over your workflow or preferences unless those live in files or in a project. So, unless you write things down for it, you end up explaining the same stuff over and over and over again.

You know what would be nice? If you could just say “do my morning routine,” and Claude already knew what that meant. Your goals, your tasks, your priorities. All handled. Every morning. Without you re-explaining a single thing.

That’s what skills are. And I built something to help you with that.

---

📍Claude Code Series: From Zero to Personal OS

• Part 1: What’s the Difference? Claude vs Claude Code vs Claude Cowork

• Part 2: Before You Use Claude Code: Build This First

• Part 3: Claude Code for People Who Don’t Code: Your First 15 Minutes

• Part 4: Understanding Skills ← You are here

• Part 5: Daily Routines (coming soon)

• Part 6: Complete Personal OS (coming soon)

---

Wait, What’s a Skill? (The Simplest Possible Explanation)

The TL;DR - a skill is a note you leave for Claude. Written in plain English. Saved as a file. That’s it.

For real. That’s the whole concept. Basically, a prompt that the system can check over and over.

You write instructions like “when I say morning, check my task list, ask me for my top 3 priorities, and save them to a file.” You save it. Now every time you type `/morning`, Claude does exactly that. Same steps. Same order. Without you explaining anything.

It’s not code. It’s not programming. It’s just writing clear instructions in plain English.

Think about it like a note you’d leave for someone watching your house: “Water the plants on Monday. Feed the cat twice. Don’t touch the thermostat.”

Except the house sitter is AI, and it follows your instructions (nearly) perfectly every single time.

(I kept waiting for someone to tell me the complicated part. There is no complicated part.)

---

Here’s What We’re Building Today

By the end of this article, you’ll have three skills on your desktop that talk to each other:

• A morning startup that sets your daily priorities

• An evening shutdown that reviews your day and sets up tomorrow

• A weekly review that spots your patterns and plans the next week

You won’t create any files manually. You won’t open any folders. You’ll paste one block into Claude Code, it’ll build everything for you, ask you a few questions about your life, and you’ll be running your first morning routine before you close this tab.

(Both powerful and slightly surreal. Classic 2026.)

---

The Yes, And Also No

YES: You can teach Claude routines; it repeats (almost) perfectly. No more re-explaining. No more starting from scratch.

ALSO NO: You’re writing a playbook for how to run parts of your life, and handing it to an AI. That’s both incredibly useful and worth sitting with for a second.

(We’ll sit with it. But first, let me show you what this looks like in real life.)

---

The Best First Skill (And Why It’s a Morning Routine)

I tested a lot of different first skills. Gratitude journals. File organizers. Meal planners. But the one that made everything click was a morning routine. Here’s why:

You already have a morning. You already think about what you need to do today. You’re just doing it in your head (or not doing it, which is worse). A morning skill takes that mental process and puts it on autopilot.

You type `/morning`. Claude asks what your top 3 priorities are for the day. It saves them. Done in 5 minutes. Tomorrow you type `/morning` again and it remembers what you said yesterday, shows you what you didn’t finish, and helps you set today’s priorities.

That’s your first “oh” moment. Claude remembered (ok fine, Claude doesn’t have a brain, but it read the tracker file you built yesterday and picked right back up)

You didn’t re-explain anything.

---

Then You Add an Evening Skill (And It Gets Good)

Once your morning skill is working, you add an evening skill. This is where things start to click.

You type `/evening`. Claude reads the tracker that your morning skill built. It already knows what you said your priorities were. It asks which ones you finished. It handles the ones you didn’t. It helps you set tomorrow up.

See what happened? Your evening skill is reading a file that your morning skill wrote. They’re talking to each other. You didn’t set up some complicated integration. You just told each skill to use the same tracker file.

Morning writes. Evening reads and writes. Morning reads what evening wrote. It’s a loop. And it runs on plain English instructions.

(This was the moment I stopped thinking of these as cute productivity tricks and started thinking “oh, this is actually a system.”) And I love me a good system.

---

Then You Add a Weekly Review Skill (And It Gets Real)

Friday comes. You type `/weekly-review`. Claude reads the log your evening skill has been building all week. It shows you patterns. How many of your Big 3 priorities did you actually complete? What kept getting pushed to tomorrow? What were your wins?

You didn’t track any of that manually. Your morning and evening skills were quietly building a log every day. The weekly review just reads it.

Three skills. Each one builds on the last. Each one reads what the others wrote. One system made of plain English instructions.

I now have 30+ skills. But they all grew from this exact foundation. Morning, evening, weekly. Everything else came after.

(And yes, I eventually named one of my skills Vera and talk to her like she’s my executive assistant. That happened around skill number 7. No apologies.)

---

One More Thing: CLAUDE.md (The House Rules)

Every project folder you create/work on should eventually have a CLAUDE.md file. This is the master file. The constitution. The house rules. Before a skill does anything, it checks in with the house rules.

Skills are recipes. CLAUDE.md is the kitchen rules. “Always clean as we go.” “Never use peanuts.” “Good knives go in this drawer.” Every recipe follows those rules, even though each recipe is different.

You don’t need a CLAUDE.md to get started. Your skills will work without one. But when you start adding more skills and want them all to behave the same way (”always ask me one question at a time” or “never make up data”), that’s where you write it. In the CLAUDE.md files.

Also, just a plain text file. Also written in English. And yes, you can tell Claude to just write it for you.

…and don’t worry. In the prompt below I’m having Claude just…write you one.

---

Build Your First Skill System (Tonight)

Step 1: Open Claude Code and paste this

Open Claude Code. Desktop app, terminal, whatever you have. You don’t even need a folder yet. Claude’s going to build everything for you.

If you haven’t set up Claude Code yet - here’s a link back to how you do it.

Copy everything below (yes, the whole thing) and paste it into Claude Code. Then sit back and watch. It’ll build everything for you, ask you a few questions about your life, and you’ll be running your first morning routine before you close this tab.

(Don’t worry - you’ll still see and approve the changes before anything is created. Nothing happens silently.)

NOTE: This copy-paste block is long (about 80 lines). That’s intentional, so you don’t have to do anything manually, but it does make this article look DENSE AND BORING for a minute. Keep scrolling for the rest of the article.

I want to build a personal productivity system using skills. Walk me through every step of what you're doing and why, so I understand the system you're building for me. Here's what I need:

**First, create my workspace:**
Create a folder on my Desktop called `my-daily-system`. Tell me what you're creating and why.

**Then, build these three skills inside that folder:**

SKILL 1 — Morning Startup (put it in `my-daily-system/.claude/skills/morning/SKILL.md`):

```
---
name: morning
description: 5-minute morning startup. Reviews yesterday, sets today's priorities, builds the tracker. Use when I say "morning", "start my day", or type /morning.
---

# Morning Startup

1. Check today's date and day of the week.
2. Read my-goals.md (if it exists) to know what I'm working toward.
3. Read tracker.md and show me anything left incomplete from yesterday.
   If there are incomplete items, ask: roll forward, reschedule, or drop?
4. Ask me: "What are your 3 most important outcomes for today?"
   Ask one at a time. Push me to be specific.
   "Work on project" isn't an outcome. "Finish the first draft of Section 2" is.
5. Ask: "Any other tasks on your mind?" Add them below the Big 3.
6. Write today's section into tracker.md with the date, my Big 3, and any other tasks.
7. Say: "You're set. Go make it happen."

Keep it fast. 5 minutes max. Warm but efficient.
```

SKILL 2 — Evening Shutdown (put it in `my-daily-system/.claude/skills/evening/SKILL.md`):

```
---
name: evening
description: Evening shutdown. Reviews the day, handles incomplete tasks, sets up tomorrow, logs wins. Use when I say "evening", "end my day", or type /evening.
---

# Evening Shutdown

1. Read tracker.md. Show me today's Big 3.
2. Ask which ones I completed. Mark them done.
3. For anything incomplete, ask: "Roll to tomorrow, reschedule, or drop?"
4. Ask: "What was your biggest win or lesson today?" Capture it. Don't probe.
5. Ask: "What are your 3 most important outcomes for TOMORROW?"
   Push for specifics again.
6. Update tracker.md: remove completed items, add tomorrow's Big 3.
7. Append today's results to log.md with the date, Big 3 status, and the win/lesson.
8. Say: "Tomorrow's locked in. Rest up."

Same energy as morning. Fast, warm, no fluff.
```

SKILL 3 — Weekly Review (put it in `my-daily-system/.claude/skills/weekly-review/SKILL.md`):

```
---
name: weekly-review
description: Friday review. Summarizes the week, spots patterns, sets next week's priorities. Use when I say "weekly review", "review my week", or type /weekly-review.
---

# Weekly Review

1. Read log.md for this week's daily entries.
2. Show me a summary:
   - How many Big 3 outcomes I completed vs planned
   - Patterns: what kept showing up? What got rolled forward repeatedly?
   - Wins and lessons from the week
3. Ask: "What's the ONE thing you want to be true by next Friday?"
4. Ask: "What are your 3 big outcomes for next week?"
5. Save the weekly summary to weekly-log.md under this week's date.
6. Say: "Week closed. Have a good weekend."
```

**Also create a file called `tracker.md`** in the `my-daily-system` folder with just the heading "# My Tracker". Explain that the skills will build this file over time.

**Now interview me about my goals.** Ask me what I'm working on this month, what matters most to me right now, and what I'd love to make progress on. Ask me one question at a time. When you have enough, save my answers to `my-daily-system/my-goals.md`.

**After everything is set up, give me a summary** of every file you created, where it lives, and what it does. Then tell me to type `/morning` to start my first day.

There is no step 2. That’s it. You paste that block, Claude creates a folder, builds three skills, explains what it’s doing at every step, asks you a few questions about your life, saves your goals, and tells you how to start. You didn’t open a file. You didn’t create a folder. You didn’t write a single instruction. You just had a conversation.

What Happens Next

Type `/morning`. Answer the questions. Watch it build your tracker. Feel a small rush of control over your day that you haven’t felt in a while.

Tonight, type `/evening`. Tomorrow morning, type `/morning` again. Friday, type `/weekly-review`.

That’s the whole system. Three skills. Plain English. Claude built everything. You just use it.

(Feel powerful? Good. You should. I felt the same way. Then I immediately started adding more skills. Fair warning.)

---

The Uncomfortable Truth

You’re building a system that tracks your goals, your wins, your failures, your patterns. A system that remembers what you said you’d do and gently asks whether you did it.

That’s the point. And also the thing worth sitting with.

I don’t have a tidy resolution for that tension. I just have the reality that my mornings are calmer, my tasks are tracked, my priorities are clear, and I built all of it by writing instructions in a text file.

Both powerful and personal. Both helpful and worth questioning.

(Classic 2026. Welcome to my daily life.)

---

P.S. - When I first started building skills, I felt ridiculous. Writing instructions to an AI like it was a new hire? Absurd. Then I stopped having to think about my morning routine. Then my evening. Then my weekly review. My morning skill started as the same simple version you just built. It’s now 600 lines long. But it started exactly where you’re starting right now.

What’s the one routine you wish someone else would just handle for you? The thing you do every day that you’re tired of thinking about? Reply and tell me. That’s your next skill.

---