How to Build Your AI OS

An AI OS is a personal system that ties your AI tools, your information, and your routines together, so AI helps you every day without you starting from scratch each time.

Stop using AI like a search box. Build it into how you work.

Context

What AI knows about you, your work, and your goals

Tools

The assistants and apps you use

Workflows

Repeatable prompts, templates, and skills

Agents

AI that carries out multi-step tasks

Review

How you check results and improve the system

• Your role, goals, and current priorities
• How you like answers: length, tone, format
• Your tools and where your files live
• Things AI should never do for you

Interview me with 15 questions to build a personal context file you can use in every chat. Then write it as a one-page document.

Add it to custom instructions, a Project, or a CLAUDE.md file.

• One AI Project per area: work, clients, health, learning
• Upload the key documents for each
• Keep a running notes file AI can read and update

Main assistant

Claude, ChatGPT, or Gemini as your hub

Notes

Notion, Obsidian, or Google Docs

Tasks and calendar

Your existing task app and calendar

Automation

Zapier, Make, n8n, or built-in scheduled tasks

• Add connectors for email, calendar, files, and notes
• Start read-only where possible
• Give each connector only the access it needs

• Save your best prompts as templates
• Package repeated processes as skills or custom GPTs
• Name them clearly so you remember to use them

Daily start

AI briefs you on calendar, priorities, and messages

Daily end

AI summarises progress and sets tomorrow’s top three

Weekly review

AI reviews goals, wins, and what to drop

• Start with research, drafts, and organising
• Require approval before sending, buying, or deleting
• Keep logs of what agents did

• Review what your AI tools remember and delete what you do not want kept
• Keep passwords, ID numbers, and bank details out of AI
• Use work-approved tools for work data

• Track hours saved each week
• Retire workflows you do not use
• Add one new automation a month

• Saturday morning: write your context file
• Saturday afternoon: create three Projects and upload key files
• Sunday morning: connect calendar and email, read-only
• Sunday afternoon: save five prompt templates and set a daily briefing