4 AI employees that work while I sleep (download them and the prompts to install them)

For most of my working life, the business stopped when I stopped. If I closed the laptop at ten, nothing moved until I opened it again, and the first hour of every morning went on catching up with myself. What did I decide yesterday? Where's that client at? What was I meant to be building?

When I started building my AI team, I had one rule in my head the whole time. In my words: the whole point of this system is to get shit done while I'm sleeping.

Now I go to bed, and four of my AI employees work the night. One updates my AI brain with everything that happened today. One reads my day and turns it into content ideas. One builds whatever I handed it before bed. And one is waiting for me at 06:06 with a brief of what they all did.

I'm not giving you four prompts in this post. I'm giving you the four employees. Each one is a download: a zip with the skill, the routine, and a readme that tells Claude exactly how to set it up with you. You drag the folder into a Claude chat, paste the prompt underneath it with your details filled in, and Claude checks what you've got connected, sets it up with you and runs it once while you watch.

The night shift

This is what my night looks like.

00:00     Knowledge Base Updater - writes today into my AI brain
00:15     Post Idea Generator - turns my day into content ideas
On call   Vibe Coder - builds whatever I handed it before bed
06:06     Morning Brief - tells me what today is, & what happened overnight

They're in that order on purpose. The updater goes first, so everything after it is reading the truth about today. The post idea generator reads the same day. The Vibe Coder doesn't run on a timer at all: I hand it a build and it works through the night on that one job. The morning brief goes last and reads what the others left behind.

Every employee you install from this post writes one line into the same file when it finishes, a night log in a folder called "Night shift". That's what your morning brief reads, so it can tell you who worked and who didn't.

What you need before you start

• Claude on a paid plan, with the Claude desktop app. Everything here runs from the Code tab.
• Your AI brain. Three of these four read your business files. If your business isn't written down anywhere Claude can read it yet, set that up first: The Co-Founder Setup.
• Your computer awake at night, with the Claude app open. A scheduled task in the Claude desktop app only runs while the app is open and your computer is awake. There's a Keep computer awake setting in the app's settings, but closing the lid still puts a laptop to sleep, so leave it open and plugged in.
• For the morning brief, your calendar and task manager connected to Claude. I'll come to that in its section.

You don't need a Mac Mini, a developer or a task manager to start. Those are what I added later.

Every employee sets up the same way.

1. Download the zip and double-click it to unzip it.
2. Open the Claude desktop app and click the Code tab at the top.
3. Start a new chat.
4. Click the + at the bottom of the chat and choose your AI brain folder.
5. Drag the unzipped folder into the chat.
6. Paste the prompt for that employee, with the blanks filled in.

One employee per chat keeps it simple. Claude reads the readme in the folder first, so it checks what you've got connected before it installs anything, and walks you through anything that's missing. It never asks you for a password or key in the chat. Connectors use your normal sign-in.

1. The Knowledge Base Updater - midnight

Everyone's building AI brains at the moment. Nobody talks about updating them, and a business changes every single day. A client call moves a project on, a decision gets made in a chat at four in the afternoon, and by the end of the week Claude is confidently telling you something that stopped being true days ago.

Mine runs just after midnight and processes the day that has just ended. It reads every chat I had with Claude that day, on both of my Macs, plus every task that moved in ClickUp and every file I changed. Then it writes it all down in the right place: a new entry in each client's daily log, each client's status page rewritten so it's true as of tonight, and my operating system documents updated if I built or changed something. It never touches my brand documents or my offers. If it can't tell where something belongs, it doesn't guess.

This is the one everything else depends on. My morning brief, my content ideas and every employee I hand work to the next day all read what this one wrote. I wrote the full story of it here: the AI employee that updates my AI brain every night.

Download the Knowledge Base Updater →

Inside the zip:

• The readme for Claude, which is how it sets the whole thing up with you: what to check first, how to install it, the questions to ask you and the test run.
• The skill, which is the whole job written down: which day to process, where to read, how to match everything to the right client, what to write in the daily log and the status page, what counts as a change and what never does, and what it must never touch.
• The templates for the status page, the daily log and the index of your clients and projects.
• The routine, the short instructions the nightly scheduled task runs.

I've downloaded the Knowledge Base Updater kit (attached). Read
README FOR CLAUDE.md first & set it up with me, one step at a time.
Here's how I want mine:
- My name: [NAME]
- My clients or projects are in: [FOLDER, or "find them for me"]
- Time it runs every night: [e.g. 23:30]
- Documents it can keep up to date: [e.g. my processes, my tools list]
- Documents it must never touch: [e.g. my brand guide, my offers, my
  goals - or "suggest a list"]
- My task manager: [ClickUp / Notion / Asana / Trello / none]
- My timezone: [e.g. Europe/London]
- Anything else it should know: [e.g. "I have two businesses"]

What you'll see is Claude looking through your AI brain and telling you what it found, then asking you one question at a time about anything you left blank. It makes a status page for any client that doesn't have one, creates the scheduled task, and runs it once. Each time it asks your permission to read or write something, choose Always allow, so it never stops at night waiting for a click. When it finishes, open one client's status page and read it. If it's true, you've got an employee.

It reads the chats you have in the Claude desktop app's Code tab, because those are saved on your computer. Chats in the Claude website or the phone app aren't, so it can't see those.

2. The Post Idea Generator - 00:15

I do so many things in a day to move my business along that I want to share, and by the next morning I've forgotten half of them.

So fifteen minutes after the updater finishes, my post idea generator reads the same day and pulls out everything I did that moved Incuv8or forward. Under each one, it gives me post ideas: what the post teaches, the problem it solves for the person watching, the steps they could copy, and what I actually did that day as the proof. In its first five nights it gave me 48 ideas, and 49 went into my content calendar, because I added one of my own.

It gives me ideas, never hooks or scripts. I write those myself from my own brain dump, and that's what keeps them in my voice.

I call mine the build in public night skill, because it started as the ideas for my build in public series. This download is that skill, with my business taken out. The full story is here: the routine that turns my day into content ideas.

Download the Post Idea Generator →

Inside the zip:

• The readme for Claude, so it sets it up with you, one step at a time.
• The skill, which reads your day, lists what moved your business forward with where it saw each one, and builds every idea backwards from the problem it solves. It also handles the morning: when you reply with the numbers you want, it adds them to your content calendar and never suggests them again.
• A content brief template. Claude writes yours with you. It says what you post about, who for, where you're heading, and what counts as a post-worthy moment, which is the filter that stops the ideas being generic.
• The routine the nightly scheduled task runs.

I've downloaded the Post Idea Generator kit (attached). Read
README FOR CLAUDE.md first & set it up with me, one step at a time.
Here's how I want mine:
- My name: [NAME]
- What I post about & who it's for: [ONE OR TWO LINES]
- Where I'm heading: [MY GOAL, WITH A DATE IF I HAVE ONE]
- What counts as a post-worthy moment: [e.g. something I built, a
  client win, a setback & what I did about it]
- Never include: [e.g. client names, personal admin]
- The formats I make: [talking head / carousel / B-roll / stories]
- Where my content calendar is: [A SHEET, A NOTION PAGE, A LIST - or
  "make me one"]
- Time it runs every night: [e.g. 23:45]
- My timezone: [e.g. Europe/London]

Claude interviews you for the content brief first, one question at a time. Spend the most time on what counts and what doesn't. Then it sets up the scheduled task and runs it once. In the morning, open the list, reply with the numbers you want ("1, 3" or "all"), and it files them for you.

If you've installed the Knowledge Base Updater, this one reads the daily logs it wrote, so set it for fifteen minutes later, like mine.

3. The Vibe Coder - on call

This is my developer, and it's the one that works differently. It doesn't run on autopilot. I delegate to it.

When I want something built - a client portal, a website, a fix on something that broke - I create a task in ClickUp with the brief in it and set the AI employee to Vibe Coder. A small script on my Mac Mini checks ClickUp every ten minutes for any work waiting for an AI employee, and when it sees mine, it starts the Vibe Coder. It can work for up to six hours on a single run. It builds the thing, runs it, clicks through it, takes screenshots and checks them, runs my security and legal checks on it, and writes me a report on the task. I set it before bed and read the report in the morning.

Nothing goes live from the Vibe Coder. It builds and shows me. Going live, connecting a domain and switching on real payments all happen with me, after I've read the report and looked at it.

If you want to hand work to your AI employees from a task manager the way I do, I wrote up how I set mine up in how to build the workflow for your AI employees. You don't need it to start. You can install the Vibe Coder as a skill, and then all you do is type /vibe-coder in a Claude Code chat and drop in your brief.

Download the Vibe Coder →

Inside the zip:

• The readme for Claude, which checks you have the free tools code needs to run and helps you install anything missing.
• The skill my Vibe Coder uses, with my business taken out. It works like a full developer: it reads the brief, looks at what's already there, picks the stack, builds it, runs it, checks it in a browser and writes the report. If it needs a login or a key, it builds everything it can without it and asks you once, at the end.
• The Vibe Coder rules: never go live, never spend money, never put a password or key in the code, access checked in the database and not just on the screen, plus the pre-launch checklist it runs on anything real people will use.
• A report template and a build brief template you fill in before you hand a job over. There's no routine in this one, on purpose.

I've downloaded the Vibe Coder kit (attached). Read README FOR
CLAUDE.md first & set it up with me, one step at a time. It's a
skill, not a scheduled task. Here's how I want mine:
- My name: [NAME]
- What I'll mostly build: [e.g. websites & landing pages for clients,
  client portals, tools for my own business]
- Where my brand profile is: [PATH, or "I don't have one"]
- Where I want my builds saved: [e.g. ~/Documents/Builds, or "you
  choose"]
- My default stack: [or "you choose"]
- Hand builds over as tasks in my task manager: [no / yes - ClickUp,
  Notion, Asana or Trello]

Claude installs the skill, makes your builds folder, checks you have the free tools the code needs to run, and suggests a small first build so you can watch it work. When you hand over a real build, this is all you type in a new chat with your builds folder attached:

/vibe-coder [PASTE YOUR BRIEF, OR ATTACH IT]

For a build overnight, choose Auto in the mode selector next to the send button before you go to bed. It lets the Vibe Coder work without stopping for routine permissions, and it still checks anything risky. Leave the app open and the computer awake. In the morning, read the report first, then open the build. If something's broken, these are the four prompts I use when a build breaks.

If you want a starting point for the brief itself, the one in the prompt I use to build a website works well here.

4. The Morning Brief - 06:06

This is the payoff. Every morning at 06:06, my morning brief reads my tasks, my client projects and what every one of my AI employees did overnight, and writes me one brief of the day. It opens with a line about the night shift. Then it tells me what today's core focus should be, what's slipping, where every client is at, and whether it's going to rain on Obe's walk.

I wake up to the report. I don't open ClickUp first, I don't open my inbox first, and I don't spend the first hour working out where I am.

My brief has its own employee, its own routine and its own set of prompts behind it, so that's what the download gives you. The full story of how I built mine is here: the morning brief.

This one only works if Claude can see your day. Before you set it up, you need:

• Your calendar connected to Claude: Google Calendar or Outlook.
• Your task manager connected to Claude: ClickUp, Notion, Asana or Trello.
• A status page for each client or project in your AI brain. The Knowledge Base Updater writes and keeps these true for you.

You connect them in the Claude desktop app under Settings, then Connectors: find the tool, click Connect and sign in. You don't have to do this first, because the readme tells Claude to check every connection and walk you through anything that's missing, but if your calendar and tasks aren't connected, the brief will be thin.

Download the Morning Brief →

Inside the zip:

• The readme for Claude, which checks your calendar, task manager and email connections before anything else.
• The skill, which reads the night log, your calendar, your task manager and your status pages, works out what's slipping, and picks one core focus from your priorities. It never changes anything.
• The sections, in order, in their own file, so you can switch them on and off or move them around: good morning and the weather, overnight, today's core focus, where you're really at, today, clients and projects, leads, what's waiting for you, and why you're doing this.
• A Vision & focus template. Claude writes yours with you, because the core focus can only tell you what matters today if it knows what you're aiming at.
• A prompts file for afterwards: make it look like your brand on your phone and your laptop, change the sections, and fix anything that's wrong.
• The routine the morning scheduled task runs.

I've downloaded the Morning Brief kit (attached). Read README FOR
CLAUDE.md first & set it up with me, one step at a time. Check my
connections first. Here's how I want mine:
- My name: [NAME]
- My town, for the weather: [TOWN]
- My dog's name, for the walk: [NAME, or "no dog"]
- My calendar: [Google Calendar / Outlook / none]
- My task manager: [ClickUp / Notion / Asana / Trello / none]
- What wins when two things compete, in order: [e.g. paying clients,
  content, new leads, my own projects]
- My goal right now: [ONE LINE]
- Where my leads come in: [e.g. a form, an email label, or "none"]
- Time it runs: [e.g. 06:00, weekdays only]
- How I like it written: [e.g. warm, short, emojis welcome]
- Anything else it should always tell me: [e.g. "which client I
  haven't spoken to in a fortnight"]
- My timezone: [e.g. Europe/London]

Claude checks your connections first and tells you what it can and can't see. Then it writes your Vision & focus document with you, sets up the brief, and runs it once so you can read today's. If the core focus is wrong, it's usually because your vision document is vague or your task manager is out of date, and both of those are worth knowing.

The overnight line is the part that matters most once you have more than one employee. If one of them didn't run, the brief tells you, and you know before you've had your coffee.

The catch, and the fix

A scheduled task can stop and wait for a permission click, and nobody's there at night to click it. One of my routines once sat waiting 25 hours on a single permission. There was no error. It just didn't run.

The fix is built into every kit: Claude runs each employee once while you watch, and you choose Always allow for every permission it asks for. The Claude app remembers those for that task, so future runs don't stop to ask.

The second catch is your laptop. If it's asleep at midnight, the task is skipped. When you open the app again, Claude runs one catch-up for the most recent missed run, so your updater still runs, just at breakfast instead of midnight. The skills in these downloads work out which day to process from the clock, so a catch-up at breakfast still writes up yesterday. Mine run on a Mac Mini that stays on, because I didn't want my business to depend on me remembering to leave my laptop open.

These four sit at the last two steps of the Incuv8or AI Framework. The Vibe Coder is step 5, work handed out from a task manager. The other three are step 6, routines, for jobs that run on a schedule: how to build a Claude routine. And across every step, nothing goes live without your approval.

What this looks like as a business

Every business owner you work with goes to bed with things half done and starts the next morning trying to remember where they were. A night shift like this fixes that, and three of the four only read and write notes, so they can't break anything in a client's business.

You're not being paid for setting up scheduled tasks. You're being paid for knowing what should happen overnight in their business, and what they need to see when they wake up.

Start with one

Don't install all four this week. Tonight, install the Knowledge Base Updater, point it at one client or one project, and read that status page tomorrow morning. When you trust it, add the morning brief, because now it has something true to read.

If you haven't got your AI brain set up, that's the foundation for all of this: start here.