Identity
Claude knows who you are.
Your role, your voice, your standards and the way you decide. You write them down once, and every conversation starts from there instead of from a blank page.
Built on Claude. No coding.
A personal AI operating system is Claude set up around you: who you are, what you know and how you work. You build it in plain language, on your own work, and it stays yours.
Your OS has four layers. You set each one up once and keep it.
Identity
Your role, your voice, your standards and the way you decide. You write them down once, and every conversation starts from there instead of from a blank page.
Knowledge
Your notes, documents and ways of doing things live in a Claude Project. You drag them in, and Claude reads them before it answers.
Workflow
The work you repeat every week becomes Claude Skills you run instead of rewrite: research, drafts, analysis, follow-ups, reports. You check the result and decide what goes out.
Agent teams
Connectors reach your inbox, calendar and drive. Agents with named jobs work in parallel while you give the instructions and keep the decisions. Small tools get built in Claude Code, without a developer.
“I am trying to build experience, and the work that used to teach it is going to AI first.”
The tasks that once taught the craft are handed to AI before anyone hands them to you. Your OS lets you produce work at a level you have not reached on your own yet, and shows you, task by task, what a good result looks like. Your judgment grows while you deliver.
“I use AI every day, and my work is not much different.”
Each chat starts from nothing. Claude does not remember your standards, your material or the way you work, so you explain again and then check again. Your OS keeps those in one place. The same request gives you the same quality every time, and each result gets easier to improve.
“Everyone says AI changes my work, and I do not want to learn to code.”
You do not need to. You work inside the Claude desktop app in plain language. What you learn is how to brief AI, give it real work and review what comes back. That is the skill people around you will expect, whatever you are working on.
Each course is a set of sessions you follow step by step, in your own folder, on your own work. You set up your OS as you go, on material you already have, so at the end there is something running rather than notes about it.
The courses are grouped by role, because your identity and knowledge layers depend on what you do. The layers are the same in every course. What changes is the examples and the skills you build.
You keep the folder, the Project, the skills and the instructions you wrote. They live in your Claude account, and they keep working after the course ends.
No. You work inside the Claude desktop app in ordinary language. Where a course uses Claude Code, you follow written steps and read what comes back. You do not write code.
Either. The courses let you build it yourself, step by step, on your own work. If you would rather build it with us, email and we set it up together on the work you already have.
The Claude desktop app on a laptop you can install software on, and the material you already work with: notes, documents, the things you produce every week. Each course page says which Claude subscription it uses.
An OS that runs: Claude set up with who you are and what you know, skills for your repeating work, and the connections and agents you chose to add. It stays in your Claude account when the course ends.
The Accelerator is a live programme where you build your OS on a real challenge from an organisation, alongside other people. The courses here build the same layers on your own time and your own work. Either way, you leave with an OS you built yourself.
A short email is enough. Say what you do and what you would like your OS to take off your plate.
ugo@futureofworklab.co