MModern Pain Care·Clinician OS
INCLUDED IN MODERN PAIN PROOpen enrollment
CLINICIAN OS· FOR THE 73% WHO CAN'T EDIT A MARKDOWN FILE

Your AI shouldn't sound like AI. The fix isn't a better prompt.

You're not bad at AI. The tools were built for engineers. Drafts that sound like you. Research that comes back synthesized. Handouts that go out in twenty minutes. None of it learned in a terminal.

By Sunday night, you'll have a patient handout that sounds like you talking. The system does the next one in twenty minutes.

You've watched the AI-savvy clinicians stand up agents, build custom GPTs, plug into PubMed in three clicks. You've tried. Three tabs in, you're staring at a config file, a GitHub folder that won't open, and a YouTube tutorial that was made for a software engineer, not a clinician at 9:30 on a Wednesday between patients.

Clinician OS is the workspace I wish I had when I started. A complete folder structure that drops into Antigravity (the chat-first AI app), with skills that run on a chat prompt, organized the way your practice already is. No terminal. No GitHub. No API keys. The voice stays yours.

Join Modern Pain ProSee what ships
Included in MPP No terminal, no GitHub Works with Claude, ChatGPT, Gemini
A NOTE FROM ME
Mark Kargela, PT, DPT
Founder, Modern Pain Care · kargelaAI

I spent the first two years of trying to use AI in my clinic the same way most clinicians do. Browser tab open, paste a question, copy the answer, hope it sounded like me. It didn't. The handouts were generic. The marketing copy was AI-flavored. The research summaries were confident and wrong.

The fix was not a better prompt. The fix was structure. A folder for my voice. A folder for my visual brand. A folder for the people I read. A folder for each patient population I work with. Once that structure existed, the AI started sounding like a colleague who had read everything I had and watched me work for a year.

Clinician OS is that structure, packaged. I'm running my whole practice out of it. So are the first 18 paid Modern Pain Pro members. I'd like you next.

THE FIVE PROBLEMS

The things that stop clinicians from using AI well.

Quotes pulled from a readiness survey of 30 working clinicians (Tally form 0Q1Do0, 2026-04). Verbatim where shown.
01VOICE
That it will still sound like AI.
Top fear, named by 14 of 25 respondents

Voice does not come out of a prompt. It comes out of a rules file. Sentence patterns, banned words, the specific stories you tell, the way you close a paragraph. None of that lives in a chat history. It has to live somewhere the AI can read every time.

How the OS handles it

The starter ships a writing-rules.md scaffold. You fill in ten of your own sentences once. Every output runs against it. If a draft reads like a LinkedIn post, the OS catches it before you see it.

02TECHNICAL FLOOR
That I will not be able to do it.
Verbatim from respondent 01, echoed by 7 others

60% of clinicians said they could not download a folder from GitHub. 73% said they could not edit a markdown file. 57% could not paste an API key into a settings file. Most AI workflows assume all three. That is the floor that keeps clinicians out.

How the OS handles it

The OS ships through Antigravity, which installs everything from a chat prompt. You drag in a folder. You ask it to set up a tool. It does. No terminal, no vendor accounts, no API keys for the base tier.

03TOOL SPRAWL
I already have a ton of platforms. This will get lost in the shuffle.
Respondent 13, n=30 survey

The same survey clinicians named Claude, ChatGPT, Gemini, NotebookLM, Heidi, Perplexity, and Patient Notes. Most run three at once. Adding another platform makes the problem worse.

How the OS handles it

The OS is not a platform. It is a folder structure your AI tool reads. Claude, ChatGPT, and Gemini all work. You keep the tool you already pay for. You add the structure that makes it useful.

04HIPAA
HIPAA. Data security. Would the investment be worth the return?
Respondent 19, n=30 survey

Most AI tutorials skip this. Then a clinician pastes a patient case into ChatGPT and learns about it the wrong way. Healthcare access to AI requires a Business Associate Agreement, and the rules differ by product tier.

How the OS handles it

As of January 2026, Claude for Enterprise has a self-serve BAA. Chat, projects, and artifacts are covered. Code seats and Cowork are not. The OS scaffolds keep PHI out of agent prompts by design and run on composite cases. The install guide marks every HIPAA boundary.

05TRANSLATION · #1 REQUESTED FEATURE
Translate pain science into something my patient will actually read.
Most-requested feature: 12 of 30 named it explicitly, more across handouts, social posts, and consults

The single most-requested feature in the survey, by a wide margin. The same theme came back under handouts (57%), social posts (40%), marketing copy (20%), and consult summaries. It is the same translation problem, four times, dressed differently.

How the OS handles it

The OS ships a handout skill, a social-post skill, a consult-summary skill, and a synthesis skill. Each runs against your writing rules and your visual brand file. The output reads like you talking to a patient, not like a chatbot reading a textbook at one.

THE TECHNICAL FLOOR

What 30 working clinicians told the readiness survey.

Tally form 0Q1Do0, n=30, fielded 2026-04. Linear scale items show the share who answered 1 or 2 of 5, i.e. “no, or barely.”
73%
cannot edit a markdown file
77%
have never used a terminal install command
80%
want a self-paced video walkthrough they can pause
WHAT SHIPS

A complete workspace, not a stack of prompts.

The starter is plain folders and markdown. Read it. Edit it. Move things around. The structure follows the PARA framework, adapted for clinical practice.
clinician-os/starter · v0.4
├── areas/ # long-term responsibilities │ ├── clinical/ # your specialty area │ │ ├── raw/ # source material in │ │ ├── wiki/ # concepts in your own words │ │ └── CLAUDE.md # area-specific rules │ ├── practice/ # billing, admin, ops │ └── personal/ # health, family, finance ├── projects/ # time-bound, one folder each ├── shared/ │ ├── writing-rules.md # your voice, defined once │ ├── design-system/ # your visual brand │ └── people/ # authors, mentors, colleagues ├── skills/ │ ├── handout/ │ ├── synthesis/ │ ├── ingest/ │ ├── query/ │ ├── lint/ │ └── dream/ # weekly workspace audit ├── library/ # empty by design ├── archive/ ├── CLAUDE.md # top-level rules ├── AGENTS.md # for Codex / Cursor users └── _first-run.md # 30-minute onboarding
01

Antigravity-locked

End-user workflows assume Antigravity, not the developer-grade Claude Code. The seat you keep is your $20/month Pro plan. Everything else installs from a chat prompt.

02

Model-agnostic

Plain folders, plain markdown. Use Claude, ChatGPT, Gemini, or whatever your practice already pays for. The OS is not a vendor product. There is nothing to lock you in.

03

No pre-baked library

The starter ships an empty library/ with a README. You curate your own sources. The curation is the learning. A library someone else built is not your library.

04

No emoji. Anywhere.

In scaffolds, in skills, in outputs. The OS is a clinical instrument, not a vibe. Modern Pain Care brand rule, dogfooded.

TAKE THIS HOME TODAY

Get the writing-rules template I built the OS on.

One markdown file. The voice rules every Modern Pain Care draft runs against. Use it with Claude, ChatGPT, or whatever you already pay for. Free.

Get the template
HOW IT SHIPS

Three steps. No terminal at any point.

Built for the readiness survey's median respondent: cannot use a terminal, cannot edit markdown, cannot paste an API key.
01

Download the workspace

One zip. You unzip it into a folder on your laptop. Same skill set as moving a file from Downloads to your desktop.

~/Downloads/clinician-os.zip → ~/Documents/clinician-os/
02

Drop it into Antigravity

Antigravity is a chat-first agent app. You drag the folder in. You ask it to set up the tools. The agent installs everything for you.

“Set up the OS in this workspace and install the MCPs.”
03

Talk to it like a colleague

You ask. It does. You edit. You ship. The structure that makes the answers good is already in the folders.

“Draft three patient handouts on central sensitization in my voice.”
THE COMPOUND

Your AI gets smarter about you every time you use it.

Use AI to its capacity, not one prompt at a time. The structure travels. Claude, ChatGPT, Gemini, or whatever's next.

Most clinicians using AI today are working off the same ceiling. You re-explain yourself in every chat. You paste the same context into five different threads. The handout that worked last month is lost to a vanished conversation.

Clinician OS puts you into folders the AI reads every time. Your voice in writing-rules.md. Your brand in shared/design-system/. The people you read in shared/people/. Your specialty in areas/clinical/. Not stored in chat history. Stored in files. Permanent, editable, yours.

The more you add to the workspace, the smarter your AI gets about you. Every concept you file in wiki/, every author you add to people/, every revised sentence in writing-rules.md. The next draft you ask for starts from a higher floor than the last.

And because it's plain folders and plain markdown, the structure travels. Claude today. ChatGPT next year. Whatever launches in 2027 that you decide to switch to. Your workspace doesn't care which model is reading it. The LLMs keep getting smarter. So does the file they keep reading.

PRICING

Included in Modern Pain Pro. No upcharge.

Clinician OS is part of MPP. If you're already a member, you're already in. If you're not, joining MPP gets you the workspace, the monthly builds, the live calls, the community, and Mark.

No premium tier you have to upgrade to. No quarterly fee on top. The base price covers it. The work I want to focus on is the building, not the cart.

MODERN PAIN PRO · INCLUDES CLINICIAN OS
$75/ monthor$750 / year
Cancel anytime. Annual saves two months.
Standard tier shown. Regional $40/mo and Accessibility $15/mo tiers also available.
  • The complete Clinician OS workspace. Folders, skills, scaffolds, install guides.
  • Monthly builds and live unstuck calls. New skills and pause-able walkthroughs ship every month, plus office hours to work through what isn't clicking.
  • The MPP community. 18 paid clinicians at last count, growing. Where the OS is being road-tested.
  • Direct access to me. Ask questions. Send drafts. I read everything.
This month inside the OSThe writing-rules skill + first-handout walkthrough.New build and a live unstuck call the first week of every month.
Join Modern Pain Pro
Included for current MPP members. Already a member? Just sign in.
If 30 days in, the OS isn't making your work easier, message me. I'll refund your MPP month, no question.
QUESTIONS

Honest answers to the things people actually ask.

Pulled from member questions, the readiness survey, and DMs. If yours isn't here, send it to me.

What if I'm not technical?

73% of the readiness-survey clinicians said they could not edit a markdown file. The OS was built for that 73%. Antigravity does the technical part. You stay in chat.

Will it really sound like me?

Voice comes out of a writing-rules file you fill in once, not a prompt. You'll write ten of your own sentences, your story, your phrases. Every output runs through that file. If you want me to draft your rules file with you on a live call, that's part of it.

Can I use ChatGPT or Gemini instead of Claude?

Yes. The OS is plain folders and markdown. Every major AI tool can read them. Claude is what I use, and the install guides are clearest for Claude, but the structure works anywhere.

What about HIPAA?

Claude for Enterprise added a self-serve BAA in January 2026. Chat, projects, and artifacts are covered. Code seats and Cowork are not. The OS scaffolds keep PHI out of agent prompts by design and use composite cases throughout. If you don't have a BAA yet, the scaffolds still work for teaching, drafting, and research.

Why does the library ship empty?

Because the curation is the learning. A library someone else built is not your library. You'll know your own faster than you'd ever know mine. The starter shows you exactly where things go. You fill it in.

What if I'm not a Modern Pain Pro member?

Join MPP. The OS is included. There is no standalone purchase. I want the people building this with me to be the ones in the community, not buyers who disappear after the download.

How much setup time is realistic?

Two to four hours for most clinicians, based on the readiness survey. You can do it in one sitting on a weekend afternoon. The live unstuck calls and the MPP community are there so you don't sit in front of a stuck screen alone.

THE COST OF WAITING

What happens if you keep dabbling.

Most clinicians who started experimenting with AI six months ago are still experimenting. Three tabs open. Copy-pasting. Hoping the next prompt finally sounds right.

The handouts still read like a textbook. The Instagram posts still sound like a chatbot wrote them. The PubMed search still ends in a wall of abstracts the patient was never going to read anyway.

The clinicians who got past it weren't the most technical. They picked a structure and stuck with it.

WHO THIS IS FOR

The clinicians I want inside this.

PTs who want to translate pain science without sounding like a chatbot. Chiros and DCs running solo practices who need an OS that doesn't require an IT team. DPT students who'd rather learn how to use AI on their first day in practice than their tenth year. Educators who want to give their students a workspace that holds up after the course ends.

If that's you, get in now. It's included for MPP members.

Join Modern Pain ProSee Modern Pain Pro