A starter template for running your business with AI coding assistants.
Business OS is a folder structure that transforms AI coding tools (Claude Code, Cursor, Windsurf, etc.) from "chatbots you ask questions" into "systems that run operations."
The mental model: You are the manager. The AI is the executor.
This template works with multiple AI coding assistants:
| File | Tool |
|---|---|
CLAUDE.md |
Claude Code |
AGENTS.md |
Cursor, Windsurf, and similar |
GEMINI.md |
Gemini-based tools |
Important: These files should stay in sync. When you update one, update the others.
Download this folder and open it in your preferred AI coding tool.
Edit the files in context/business/:
- Add your company description
- Describe your services/offers
- Define your ideal client
- Document your brand voice
Run the /morning command to generate your daily priorities.
Try the included YouTube skill:
"Process this video: https://youtube.com/watch?v=..."
business-os/
│
├── CLAUDE.md # Instructions for Claude Code
├── AGENTS.md # Instructions for Cursor/Windsurf
├── GEMINI.md # Instructions for Gemini tools
├── README.md # This file
├── .env.example # Template for environment variables
├── .env # Your secrets (create from .env.example)
├── .gitignore # Keeps secrets out of git
│
├── context/ # What the AI knows about you
│ ├── business/ # Your company, offers, clients
│ └── learning/ # Research, notes, references
│
├── .claude/ # AI capabilities
│ ├── skills/ # Repeatable workflows
│ ├── commands/ # Daily triggers (/morning, etc.)
│ └── agents/ # Parallel specialists
│
└── workspace/ # All outputs
├── foundations/ # Tasks, wins, daily briefs
├── content/ # Content you create
├── docs/ # Project folders
└── journal/ # Personal reflection
The .env file stores secrets and API keys that your skills might need.
-
Copy the example file:
cp .env.example .env
-
Edit
.envand add your keys as needed -
Never commit
.envto git (it's in.gitignore)
- Security - Keep API keys out of your code and git history
- Portability - Same code works with different credentials
- Skills can use it - Scripts can read from
.envfor API access
# AI APIs (if your skills call APIs directly)
OPENAI_API_KEY=sk-...
ANTHROPIC_API_KEY=sk-ant-...
# Integration APIs (for skills that connect to services)
NOTION_API_KEY=secret_...
AIRTABLE_API_KEY=pat...
# Webhooks (for automation skills)
SLACK_WEBHOOK_URL=https://hooks.slack.com/...Add variables as you build skills that need them. Start empty - you may not need any.
Extract and analyze YouTube video transcripts:
# Install requirement
pip install youtube-transcript-api
# Usage
"Process this video: [YouTube URL]"The skill will:
- Fetch the transcript
- Categorize the video type
- Extract key insights
- Save to your learning folder
Generates a daily brief with:
- Your TOP 2 priorities for the day
- A quick win (10-15 min task)
- Context from your weekly goals
The context/ folder is the AI's memory about your business. The more context you add, the less you need to explain every time.
Skills are self-contained instructions for repeatable tasks. When you say "process this video," the AI follows the YouTube skill's instructions.
Commands are quick triggers that run specific workflows. Type /morning and get your daily brief.
Everything the AI creates goes in workspace/. Keep it organized by type.
- Fill in your context - The more the AI knows, the more useful it becomes
- Use it daily - Run
/morningto start each day - Create new skills - When you find yourself repeating a process, make it a skill
- Watch the video series - Learn how to build on this foundation
This template is part of the "Claude Code for Business" video series:
- Setup Guide - Understanding the structure (you are here)
- Building Skills - Create your own capabilities
- Commands & Rituals - Daily triggers that run your day
- Context Deep Dive - Why context is everything
- Agents & Automation - Parallel specialists
Open an issue on the GitHub repo or leave a comment on the video.