Using Brett
Six commands, each built for one part of client work, plus the privacy rule that applies to every request.
The six commands
In Claude, type / and pick a command, for example /case-review. In ChatGPT, type @ and pick one, for example Brett: Case Review. Then add your question or the de-identified case in the same message.
You can also just ask a question in a normal message. Brett's material is used whenever it's relevant.
Ask Brett
Quick clinical or practice questions, and standalone supplement questions. Short, practical answers with Brett's reasoning.
"Why does Brett support bile flow before starting antimicrobials?"
Case Review
Turns an intake, history, symptoms and past protocols into a case snapshot, patterns, likely root causes, priorities and a testing plan. Ends with a Phase 1 direction.
"42F, bloating after meals, constipation, fatigue since 2023 antibiotics. Here's her intake..."
Lab Review
Reads functional labs (stool, DUTCH, blood work) alongside symptoms and history: what matters, what it points to, what to do next.
"GI-MAP and symptoms attached. Client is 35-40, female, post-partum."
Protocol Road Map
The master plan: phases over 3 to 6 months, then the current 30-day protocol in full (diet, supplements with timing, drainage, lifestyle) and a preview of the next one.
"Build the road map from the case review above."
Diet Plan
The diet piece in depth: which therapeutic diet, food lists, a sample meal plan (usually 7 days), transition and reintroduction.
"Low-FODMAP plan for phase 1, client is vegetarian."
Client Handout
Plain-language education for your client: what's going on, why the plan looks the way it does, what to do. Ready for you to review, brand and send.
"Write a handout explaining her phase 1 protocol."
Working through a case
The commands build on each other when you run them in the same chat or project.
- Case ReviewSnapshot, root causes, testing plan
- Lab ReviewWhen results come back
- Protocol Road MapPhases and the first 30 days
- Diet PlanFood lists and meal plan
- Client HandoutWhat to send the client
Tips for good results
- One client, one place. In Claude, make a project per client with Use account memory off. In ChatGPT, start a new chat per client. Client work never mixes.
- Give the timeline. Brett reasons from symptoms, history and timeline first, and labs second. More context gives sharper answers.
- Review everything. Every output is a draft. You are the practitioner; check doses, products and fit before anything reaches a client.
- Red flags come first. When a case needs a doctor, Brett says so at the top. Brett never starts, stops or changes medications.
Protecting client privacy
Never share information that identifies a client. If a message contains a client identifier, Brett refuses the whole request and asks you to remove it first. This includes text inside attached PDFs and images.
| Remove before sending | Fine to keep |
|---|---|
| Client's or family members' names | Age or age range, and sex |
| Birth date | Symptoms, history and timeline |
| Street address, postal or ZIP code | Dates of events (symptom onset, test collection dates) |
| Phone number, email address | Medications, supplements, lab results, units and ranges |
| Health card, insurance, patient, chart or lab accession numbers | Your own name and practice name, doctors, labs and brands |
If Brett refuses for privacy
Brett's reply includes a ready-made redaction prompt with a copy button.
- Copy the prompt and send it as your next message in the same chat.
- Your AI app rewrites what you shared, replacing identifiers with placeholders such as [CLIENT] and [ID REMOVED], and keeps every clinical detail.
- Check the redacted version, then say yes. Brett carries on with your original request using only the redacted version.
You can also remove the details yourself and send the request again.
What Brett keeps about you
Your usage records (which commands and tools ran, when and from which computer) for licensing and support. Brett never records your questions, client details or the AI's answers. The full details are in the Privacy Policy.