AIS-OS
Your AI Operating System in Claude Code
Turn Claude Code into a personal AI operating system: it knows your business, can access your tools, knows how to do the work, and runs without being asked.
What AIS-OS is
The AIS-OS is a practical kit—based on Nate Herk’s MIT framework—for building your AI Operating System inside Claude Code. It organizes everything into two complementary frameworks and three ready-to-use skills.
3 Ms Framework
The operator’s brain: how you think, decide, and build.
- 🧠Mindset — how to think of AI as an operator
- 🧭Method — how to decide what to automate
- 🛠️Machine — how to build and operate
4 Cs Framework
The system architecture: the four pillars of an AIOS.
- 🗂️Context — knows your business
- 🔌Connections — reaches your tools
- 🧩Capabilities — knows how to do the work
- ⏰Cadence — runs without being asked
3 Skills in the kit
Day 1 Setup — 7 questions that teach Claude to understand your business
Four-Cs Diagnosis — assesses the current state of your AIOS on Day 7
1 automation per week — grow the system without making a mess
AIS-OS Litmus Test
"While you’re away from your desk, your AIS-OS observes a real event and produces an output faster and more accurately than you would."
If this still isn’t happening, the AIS-OS was only half built.
Boring is Beautiful · Workflows beat agents
The AIS-OS isn’t about impressing people with sophisticated agents. It’s about building predictable, deterministic, boring workflows that work every time without supervision. The beauty is in consistency, not complexity.
How to know it worked
Team reaches out
Your team starts asking you, "How do you do that so fast?" — a sign that the system is visible and working.
Context-switching reduction
You stop switching between tabs and tools all the time. The system searches and synthesizes for you before you even ask.
Knowledge leaves your head
Business knowledge moves out of your head and into the system—procedures, context, decisions—everything documented and accessible.
The 3 tracks
The complete journey from Mindset to autonomous operation.
The Operator’s Brain
The 3 Ms
Changes how you think about AI before building anything. The mental foundation for operating with excellence.
- 1 Mindset — How to Think
- 2 Method — How to Decide
- 3 Machine — How to Build and Operate
The Architecture
The 4 Cs
The four pillars that make an AIOS truly work—from context to autonomous cadence.
- 1 Context — Knows your business
- 2 Connections — Reaches your tools
- 3 Capabilities — Knows how to do the work
- 4 Cadence — Runs without being asked
Operating in Practice
The 3 Skills + Expansions
Get the system up and running and keep it running — from initial setup to sustainable week-by-week growth.
- 1 /onboard — Day 1 Setup
- 2 /audit — Day 7 Diagnosis
- 3 /level-up — 1 automation/week
- 4 Expansions and Weekly Cadence
Quick start
From zero to a running AIOS in 14 days.
Clone the repository and open it in Claude Code
github.com/inematds/ais-os — clone locally, open the folder in Claude Code. The kit comes with the skills ready to use.
Run /onboard (7 questions)
Claude asks 7 questions about your business and generates the foundational context for your AIOS. It takes ~15 minutes.
Use it for 1 week with real questions
Work as usual using Claude Code for real day-to-day tasks. Let the system learn through use.
Day 7 — run /audit
Four-Cs Diagnosis: Claude assesses each pillar and identifies the system’s main bottleneck. Generates a health report.
Day 14 — run /level-up
Based on the audit, plan and implement 1 new automation. No more than that — consistency beats complexity.
Weekly ritual — 1 artifact per week
Every week: 1 new artifact (prompt, workflow, or context document) enters the system. The AIOS grows sustainably and without clutter.