Account

Name
Email
Plan
Free
Areas trained
0 / 10
MyOS

The AI we were all promised is already here.
You just aren't using it yet.

Claude + MyOS

ChatGPT was good, but Claude is another level. The time to switch has arrived. Let MyOS build you a personalised system that makes Claude work the way you do.

Scroll to explore ↓
The problem

We get it. You've used ChatGPT forever.

It knows everything about you. You had it dialled in. And for a while, you even felt ahead.

Then the game changed. Claude is everywhere, doing everything, for everyone. And you feel like you're falling behind.

You want to make the switch. But starting from scratch, re-explaining everything, rebuilding all that context? It's not worth it. You've tried it anyway. Honestly? It doesn't seem that different.

The solution

It's time to shift your thinking.

If ChatGPT was your assistant, Claude with MyOS is a whole new level of hire.

Imagine your dream deputy, fully trained on how you speak, think and act, ready to complete your work, to your exact standards, at a moment's notice.

However, switching without a system means going backwards before you go forwards. MyOS makes sure you skip that part entirely, handing you a fully personalised system built for where AI is heading.

Don't fall behind. Arrive ahead.

The difference

Before and after MyOS.

Before MyOS
Claude
Write me a project status report for my next board meeting.
Sure! I can help with that. Could you tell me:

What projects should I include?
What format do you prefer?
Who is the audience?
What time period should it cover?
Any specific metrics you'd like highlighted?
After MyOS
Claude
Write me a project status report for my next board meeting.
Skills activated: voice brand-kit status-updates stakeholder-intel
Here's your board status report. I've used your standard deck format with RAG status, pulled the active projects from your portfolio, and structured it how your steering committee expects — headline status up front, decisions needed, then detail by workstream.
Q1 Board Update — Project Status.pptx
How it works

A structured onboarding programme.

MyOS guides you through a suite of modules, extracting key information across the core components of how you work. Setting up Claude as a self-improving operating system, ready to deliver just as you do, whenever you need it to.

01

Profile

We map the foundations — your role, your week, your outputs, and your audiences. Building the blueprint for your system.

02

Extract

Module by module, MyOS extracts your knowledge and converts it into personalised skills. Each one teaches Claude a new dimension of how you work.

03

Build

Every skill is built as one component of a coordinated operating system. Not isolated instructions — a connected architecture where skills stack, reference each other, and compound.

04

Deploy

Your complete system, ready to install as global skills in Claude. A foundation built to your standards — designed to grow as you do.

The onboarding builds your foundation. From there, the system is yours — add new skills, refine existing ones, and expand into new areas. All aligned to the same structure, all compounding on what came before.

The system

An operating system for Claude,
built around you.

MyOS works with you across three structured layers. Giving you the strategic set up from day one, that evolves with you as your usage grows.

OS Layers
Core
How you sound, communicate, and format. The foundation every other layer inherits.
Role
What you produce, how you operate, who you work with. Tailored to your actual job.
Personal
How you think, plan, and decide. Unique to you and your workflows.

Features embedded across the OS.

Your system doesn't just store instructions. It learns, grows, and maintains itself.

Trust model

Skills mature from new to autonomous, mirroring how you'd delegate to a real colleague.

Self-improving

Accepts feedback, updates its own rules, and grows its evidence base with every output.

Gap detection

Identifies repeated tasks no current skill covers and flags where new training is needed.

Skill creation

Builds new skills using the same methodology, structure, and standards as the originals.

Self-calibrating

As the system grows, skills cross-reference each other to stay consistent and aligned.

Cross-layer stacking

Skills are designed to compose across all three layers — voice, structure, and context work as one system.

Pricing

Build your system. Keep it forever.

MyOS Pro
£250
Done with you · limited spaces
Everything in Core
1:1 onboarding session
Role evaluation & custom skills
Priority support
MyOS Teams
£2,000
Up to 5 people · £300 per additional member
Everything in Pro
Team setup & workflow evaluation
Shared skill libraries
Team rollout support

You used to be ahead.
Now it's time to get back there.

M

Create your account

Build your personalised AI operating system. Progress saves automatically.

Name
Email
Password

Already have an account? Log in

Skip — demo mode

Onboarding
Profile
Foundation
Workflows
Bespoke
Deploy
MyOS+
01

Onboarding

Set up your account, learn the system, train your first skill

Account created
Complete

Your MyOS account is set up. Your progress saves automatically — you can leave and pick up exactly where you left off.

Introduction
Not started

MyOS builds you a personalised skill system for Claude — a set of training files that teach it how you write, communicate, produce work, and think. Each skill is generated from your answers, reviewed by you, and deployed as a global skill in Claude.

Skills are structured across three layers: Foundation (voice, communication, brand kit, methodology, audience, personal system), Workflows (meeting notes, meeting prep, status updates, weekly planning, email drafting, exec summaries), and Bespoke Outputs (your role-specific deliverables). Foundation teaches Claude who you are. Workflows put that intelligence to work on recurring tasks. Bespoke handles the outputs unique to your role.

Orientation
Not started

Sidebar — your navigation. Every module is listed in order. Completed modules show a green tick. Locked modules open as you progress.

Journey bar — the stages across the top of this page. Click any stage to see what's involved.

Each module follows the same pattern: why it matters, focused questions, a generated skill file to review, and deployment instructions.

Your first skill — Writing Voice — teaches Claude how you sound and gives you a feel for the whole process.

How You Sound
Not started

Train your writing voice — tone, vocabulary, structure, and the things you always edit out of AI writing. This is the foundation everything else inherits.

02

Building Your Profile

Map the way you work

Full programme unlocked

Once you've completed onboarding, you unlock the full programme. This gives you access to all modules and the complete skill system.

Your Profile
Not started

Tell us about your role, your week, your outputs, and your stakeholders. MyOS analyses this to configure which skills to build and how to structure the system around your job.

03

Foundation

Teach Claude who you are and how you operate

How You Communicate
Not started

Message structure, persuasion patterns, and how your tone shifts by audience.

Brand Kit
Not started

Colours, fonts, document conventions, presentation conventions — your visual identity.

How You Operate
Not started

Frameworks, terminology, governance thresholds, and meeting protocols.

Who You Work With
Not started

Audience profiles, tone adaptation by stakeholder type, and communication sensitivities.

How You Think & Work
Not started

Productivity patterns, decision frameworks, and AI collaboration preferences.

04

Workflows

Set up your daily workflows — pick the ones that matter to you

Meeting Notes
Not started

Structure, actions, and distribution — consistent meeting notes every time.

Meeting Prep
Not started

Briefings, agendas, and stakeholder context before you walk in.

Status Updates
Not started

Recurring updates with your format, cadence, and escalation rules.

Weekly Planning
Not started

Start-of-week and end-of-week routines that match your rhythm.

Email Drafting
Not started

Emails in your voice with the right tone for every audience.

Exec Summaries
Not started

Complex material condensed into decision-ready executive summaries.

05

Bespoke Outputs

The deliverables unique to your role

What You Produce
Not started

Your key deliverables — one skill per output, with full structure, quality standards, and templates. These are the outputs nobody else produces in quite the same way.

06

Deploying Your OS

Install, review, and graduate

Skills Library
Not started

Your complete operating system in one view. Export as a structured skill pack and install into Claude.

Graduation
Not started

Final review plus your meta-skills: Skill Maintenance Manager and Skill Builder for creating new skills.

+

MyOS+

Your system keeps growing

Coming soon

Your onboarding builds the foundation. MyOS+ is what keeps it evolving.

New skills drop regularly — ready-made for common workflows, tools, and use cases. Each one arrives in a generic state. You personalise it through the same guided process and it slots into your existing system automatically.

Subscription · launching post-beta
Complete your onboarding first — MyOS+ builds on everything you create here.
Not started
Your Profile

Tell us how you work

So we can build a system that's shaped around your actual role.

Your Role
Who you are and where you sit
Job title
Organisation
Industry
Your Context
What fills your days? Don't overthink it — just describe a normal week.
Your Outputs
Each one becomes a dedicated skill
OutputFrequency
Key Relationships
These shape your stakeholder and audience skills
WhoRelationship
AI Experience
How much have you used AI tools so far, and for what?
Documents about your role
Job description, org chart, CV, role specification
Drop files here or click to browse
Not started
Core

How You Sound

Your writing voice. The foundation everything inherits.

Voice Basics
How your writing is structured
English variant
UK English
US English
Sentence length
Short & punchy
Mixed
Flowing
Structure preference
Conclusion first
Build up
Context-dependent
What You Ban
Words and patterns that aren't you
Words or phrases Claude should never use
Your Range — Authority & Certainty
How conviction and doubt shape your voice
How do you write when you're the expert — when you know your stuff and need others to trust it?
How do you write when you're not certain or don't have all the information, or when you don't have the answer yet?
Your Range — Distance & Dynamics
How relationships shape your tone
How does your writing shift when you're talking to someone senior vs someone you manage or mentor?
How do you write differently when you know someone well vs when the relationship is new or formal?
What You Edit
The corrections that reveal your rules
When you edit AI-generated text, what do you usually change?
Writing Samples
Real examples of how you sound
Paste text or drop files — anything you wrote that sounds like you

Ready to build the full system?

You've seen how one skill works. Here's everything else.

Early Adopter
£29 £75

One-time · lifetime access · includes all future updates

  • 3 Core skills — Voice, Communication, Brand
  • 5 Role skills — Your outputs, Method, Audience
  • 1 Personal System — Working habits & decision frameworks
  • Meta-skill — system maintenance
  • Skill Builder — create unlimited new skills
  • Agentic readiness — prepared for autonomous AI
Not started
Core

How You Communicate

How you structure, persuade, and adapt across any medium.

How You Get Your Point Across
Your default communication architecture
Think of the last time you had to explain something complex to someone. Walk me through how you structured it.
How You Persuade
What you do when you need buy-in
Think of a time you successfully changed someone's mind or got buy-in for something. What did you do?
How You Adjust by Audience
Same message, different delivery
How does the way you communicate shift depending on who you're talking to?
What Makes Communication Fail
The patterns that lose people
When communication fails — yours or someone else's — what's usually the problem?
How You Open & Close
First impressions and final signals
How do you typically open a piece of communication — and how do you close it?
Communication Samples
Real examples across different contexts
Paste or upload examples of your communication across different contexts
Emails, Slack messages, proposals, presentations — anything that shows how you communicate. The more variety, the better.
Upload communication samples (optional)
Not started
Foundation

Brand Kit

Your visual identity — colours, fonts, and formatting conventions across documents, presentations, and data.

Brand Guidelines
How strict and what defines it
How strict are your brand guidelines?
Strict
Loose
Multiple brands
No formal guidelines
Colours
Your brand palette
Primary colour
Secondary colour
Accent colour
Fonts
Typography standards
Heading font + weight
Body font + size
Presentation font (if different)
Document Conventions
How your written documents are structured
Heading levels, bullets vs prose, table of contents rules, first page layout, margins and spacing
Presentation Conventions
How your slides work
Words per slide, builds or animations, last slide convention, speaker notes approach
Data & Evidence
How you present numbers and proof
Charts vs tables, inline vs appendix, RAG conventions, interpretation rules
What Looks Wrong
The formatting mistakes that stand out
When you see a document or presentation that doesn't look right, what's usually the problem?
Brand Assets
Upload what you have — templates, logos, guidelines
Not started
Workflow

Meeting Notes

Configure how Claude turns your meetings into structured, distributable notes.

Template
Upload an example or describe your format
Upload an example of your meeting notes, or describe the format you use
Upload meeting notes example (optional)
Structure
How you organise your notes
How do you structure your meeting notes?
Decisions → Actions → Discussion
Chronological
By topic/agenda item
Other
Actions
How you capture and track what needs doing
How do you capture and track actions from meetings?
Inline in notes
Separate actions section
External tool (Jira, Asana, etc)
No formal tracking
What does a well-captured action look like?
Distribution
Who gets the notes and how
Who gets your meeting notes? Do different audiences get different versions?
What's Bad
Meeting notes that don't work
What makes meeting notes useless? What do you hate seeing?
Not started
Workflow

Meeting Prep

Configure how Claude prepares you for meetings — briefings, agendas, and stakeholder context.

Template
Upload an example or describe your format
Upload an example briefing, or describe what you want before a meeting
Upload meeting prep example (optional)
Depth
How detailed should prep be
How detailed should your meeting prep be?
Quick summary
Standard briefing
Deep briefing pack
Context
What you need to know going in
What context do you need before a meeting? (attendee backgrounds, previous decisions, open actions, risks)
Timing & Format
When and how you want it
How far in advance do you prep, and what format works?
Document
Bullet email
Calendar note
Timing preference
What's Bad
When meeting prep lets you down
When meeting prep lets you down, what's usually missing or wrong?
Not started
Workflow

Status Updates

Configure how Claude writes your recurring status updates — format, cadence, and escalation.

Template
Upload an example or describe your format
Upload an example status update, or describe the format
Upload status update example (optional)
Cadence & Audience
How often and for whom
How often do you send status updates?
Daily
Weekly
Fortnightly
Monthly
Who receives them?
RAG & Escalation
How you flag status and risk
Do you use RAG status or similar?
Yes — RAG
Custom scale
No formal rating
What triggers an escalation or flag?
Structure
Sections and order
What sections does your status update have? What order?
What's Bad
Status updates that waste everyone's time
What makes a status update useless or actively harmful?
Not started
Workflow

Weekly Planning

Configure your start-of-week and end-of-week routines, priorities, and recurring commitments.

Start of Week
Your Monday routine
What does your start-of-week routine look like? What do you review, prioritise, or prepare?
End of Week
Your Friday routine
What does your end-of-week look like? Do you review, log, or prep for next week?
Recurring Commitments
What's fixed in your calendar every week
What are your recurring weekly commitments? (standing meetings, deadlines, reporting)
Tools & Format
Where your planning lives
Where does your planning live?
Calendar
Document/note
Task tool (Jira, Asana, etc)
Email to self
What's Bad
When your week goes off the rails
When your week goes off the rails, what's usually the cause?
Not started
Workflow

Email Drafting

Configure how Claude drafts emails — tone by recipient, structures, and sign-offs.

Email Samples
Show Claude how you actually write emails
Paste or upload 2–3 emails you've sent to different audiences
Upload email examples (optional)
Tone Flex
How your email tone shifts by recipient
How does your email tone shift by recipient? (e.g. senior stakeholder vs peer vs direct report)
Standard Types
The emails you write most often
What types of email do you write most often?
Sign-offs
How you close emails
How do you sign off? Does it vary by audience or formality?
What's Bad
Emails that miss the mark
What makes an email feel wrong — yours or someone else's?
Not started
Workflow

Exec Summaries

Configure how Claude condenses complex material into executive-ready summaries.

Template
Upload an example or describe your format
Upload an example exec summary or briefing note, or describe the format
Upload exec summary example (optional)
Length
How long should it be
How long should an exec summary be?
Half page
One page
Two pages
Depends on source
Framing
How you present recommendations
How do you frame recommendations?
Direct recommendation
Options with pros/cons
Question-led
Neutral / no recommendation
Audience
Who reads these and what they need
Who typically reads your exec summaries and what do they need from them?
What's Bad
When an exec summary fails
When an exec summary fails, what's usually the problem?
Not started
Role

What You Produce

Your key deliverables. A separate skill for each.

Not started
Role

How You Operate

Frameworks, governance, terminology, and the unwritten rules.

Methodologies
The frameworks you follow
What methodologies or frameworks do you follow?
Terminology
Words that must be used correctly
Terminology that must be used correctly
Wrong word → Correct word
Governance
What needs approval and when
What needs approval, from whom, and what triggers escalation?
Meetings
What happens before, during, and after
Recurring meetings: what happens before, during, and after?
How Work Gets Tracked
Tools, formats, and tracking conventions
How do you track progress, actions, risks, and issues? What tools or formats do you use?
What Goes Wrong
The mistakes that cause rework
What are the most common process mistakes in your environment — the things that trip people up or cause rework?
Not started
Role

Who You Work With

Same message, different readers. How you adapt for each.

Key Audiences
Who they are and your relationship
Key audiences (3–5) and your relationship to each
What Each Audience Wants
Needs and tone per audience
For each audience: what do they want, and what tone works?
Audience Boundaries
What you should never share, assume, or get wrong
For each audience: what should you never share, assume, or get wrong?
Most Difficult Audience
The one that takes the most care
Who is your most difficult audience and why?
How You Win Them Over
What gets each audience on side
For each key audience, what's the thing that gets them on side? What do they respond to?
How You Adjust the Same Message
A real example of audience adaptation
Think of a recent message you had to deliver to two different audiences. How did you change it for each?
Not started
Personal

How You Think & Work

How you prioritise, decide, and want Claude to work with you.

Prioritisation
How you decide what comes first
When you have too much to do, how do you decide what comes first?
Weekly Rhythm
Your ideal week structure
Describe your ideal weekly rhythm
Decision Making
How you think through important choices
Walk through a recent important decision. How did you think it through?
How Claude Should Work
This shapes every interaction
How do you want Claude to work with you?
What Claude Should Never Be
The anti-patterns that break trust
What should Claude never be?

MyOS — Skills Library

Your complete skill system. Click any skill to view, copy, or download.

Export your skills
Copy all as text
For Claude Projects — paste all skills in one go
Copied
Download individual zips
Upload each to Claude.ai via Settings → Skills
Done
Download system package
Full system for Claude Code — unzip into .claude/skills/
Done
Complete

Your Deputy Is Trained

The full programme. One system. Getting better every day.

Training complete

The meta-skill

Your training manager — a skill that audits all your other skills for consistency, identifies gaps, and proposes updates. It covers every skill in your system, including any you build yourself later.

🔧 Copy meta-skill

The skill that manages all other skills

Copied

The Skill Builder

Your final training area teaches Claude how to train itself. The Skill Builder is an active skill that uses the full MyOS methodology: extraction question design, structural conventions, cross-referencing with existing skills, quality standards, and profile integration.

Every future skill you build will follow the same architecture, inherit from your profile, and integrate with your existing system.

🛠️ Copy Skill Builder

The skill that builds new skills

Copied

What happens now

Use it. Every output feeds the trust model. Accept to grow the library. Edit to refine rules. After enough proven work, your deputy handles routine tasks on autopilot.

Extend it. Same instruction three times without a skill? That's training waiting to happen. Use the template below.

Prepare for autonomous. Your skills are built for the next step — AI that acts on your behalf. When that arrives, your deputy is already trained for it.

📋 Skill Template

For all future training

Copied

Directory structure for Claude Code / Cowork

.claude/skills/ ├── writing-voice/ │ ├── SKILL.md │ └── references/ │ ├── voice-profile.md │ ├── writing-samples.md │ └── vocabulary-profile.md ├── communication-context/ │ ├── SKILL.md │ └── references/ │ └── email-examples.md ├── brand-kit/ │ ├── SKILL.md │ ├── references/ │ │ └── brand-palette.md │ └── assets/ │ └── [uploaded templates] ├── output-[name-1]/ │ ├── SKILL.md │ ├── references/ │ │ └── structure-spec.md │ └── assets/ │ └── [uploaded template] ├── output-[name-2]/ │ └── [same structure] ├── methodology-governance/ │ ├── SKILL.md │ └── references/ │ ├── terminology-glossary.md │ └── governance-thresholds.md ├── stakeholder-intelligence/ │ ├── SKILL.md │ └── references/ │ └── stakeholder-profiles.md ├── personal-system/ │ ├── SKILL.md │ └── references/ │ ├── weekly-rhythm.md │ ├── thinking-frameworks.md │ └── ai-collaboration.md ├── skill-maintenance-manager/ │ └── SKILL.md └── skill-builder/ └── SKILL.md
Export your skills
Copy all as text
For Claude Projects — paste all skills in one go
Copied
Download individual zips
Upload each to Claude.ai via Settings → Skills
Done
Download system package
Full system for Claude Code — unzip into .claude/skills/
Done

Your deputy is trained.

Built area by area. Improving with every use. Ready for what's next.