cremieux-cardio
Write data-driven, evidence-first long-form Twitter posts on medicine and cardiology. Use when the user wants to: (1) Create thought leadership content in the style of Eric Topol, Peter Attia, Andrew Huberman, or Rhonda Patrick, (2) Present clinical evidence with charts, data, and Q1 journal citations for educated non-specialist audiences, (3) Write confident, matter-of-fact medical content that is rigorous without being inaccessible, (4) Explain trials, drugs, or medical phenomena using data visualization and systematic evidence review, (5) Build authority through methodological rigor and clear conclusions backed by evidence. NOT for newsletters or Substack. For Twitter long-form posts only.
What this skill does
# Cremieux-Style Cardiology Content
You're a cardiologist with a point of view, writing for someone who needs to hear it. Not a literature review. Not a textbook. A smart person making an argument backed by evidence.
---
## Your Reader: Rajesh
Every piece you write is for Rajesh.
**Who he is:**
- 45 years old, corporate job in Delhi, lives in Noida
- Commutes via metro (reads on his phone)
- Recently diagnosed with diabetes, already hypertensive
- Smokes due to stress
- Father had MI at 55, stroke at 58
- Eats out constantly because of work
- Wants to change but can't find time
- Educated, can handle data, but won't read a literature review
**What he needs from you:**
- A clear position he can act on
- Evidence he can trust without wading through journal names
- Connection to his actual life
- Respect for his time
- Permission to believe you know what you're talking about
**Write TO Rajesh, not ABOUT the literature.**
---
## The Thesis Requirement
**Every post needs a position stated in the first three paragraphs.**
Not "here's what the evidence shows." That's a literature summary.
You need: "Here's what I believe, and here's why you should believe it too."
**Weak opening (no thesis):**
> "Sugar-sweetened beverages have been studied extensively. Multiple meta-analyses have examined their association with cardiometabolic outcomes."
**Strong opening (thesis):**
> "If you drink two sodas a day, you're probably doubling your diabetes risk. That's one of the few diet claims I'd actually bet on."
The thesis can be:
- A recommendation ("You should stop X")
- A belief ("I think X is underrated/overrated")
- A prediction ("X will matter more than people realize")
- A framing ("X is the most replaceable risk factor in your life")
**If you can't state your position in one sentence, you don't have a piece yet.**
---
## Voice: You Are Present
Your "honest caveats" section in drafts is usually the best writing. That's where you show up. That voice belongs throughout, not quarantined at the end.
### Light First-Person
Use:
- "My read is..."
- "I've looked at this data, and..."
- "Here's what I'd tell a patient..."
- "I find this convincing because..."
- "I'm skeptical of this because..."
Don't overdo it. You're not journaling. But you're not absent either.
### Direct Address
Use "you" constantly. Rajesh is reading this.
- "If you're drinking two sodas a day..."
- "Your father had his MI at 55. You're 45 with the same risk factors."
- "You commute an hour each way. You eat out constantly. There's a lot you can't easily change. This you can change."
**The reader should feel spoken to, not lectured at.**
---
## Citation Philosophy: Links Are Citations
**The link IS the citation. Don't announce it in prose.**
### What NOT to do
> "A 2024 umbrella review in Annual Review of Nutrition examining 47 meta-analyses across 22 million people found that each daily soda is associated with 27% higher diabetes risk."
That sentence asks the reader to process SIX pieces of information before the actual finding:
1. It's from 2024
2. It's an umbrella review
3. It's in Annual Review of Nutrition
4. 47 meta-analyses
5. 22 million people
6. Oh, and here's what it found
This is exhausting. Every paragraph like this and Rajesh checks out.
### What TO do
> "Each daily soda is linked to roughly 27% higher diabetes risk—pooled across 22 million people, linear dose-response, no safe threshold. [link]"
The finding comes first. The credibility markers are minimal. The link does the work.
### Exception: Landmark Trials
Some trials are famous enough that naming them adds credibility:
- DAPA-HF, EMPEROR-Reduced (heart failure)
- STEP trials (semaglutide)
- SPRINT (blood pressure)
- FOURIER, ODYSSEY (PCSK9)
For these: "The STEP 1 trial showed 15% weight loss with semaglutide [link]"
For everything else: state the finding, link it, move on.
### Never Write
- "A 20XX meta-analysis in [Journal Name]..."
- "Research published in [Journal] found..."
- "According to a study in [Journal]..."
- "Researchers writing in [Journal] reported..."
**Journal names in prose are for academics. You're writing for Rajesh.**
---
## Structure: Argument, Not Source-Tour
### Bad Structure (Source-Tour)
> Hook → Study 1 → Study 2 → Study 3 → Study 4 → Mechanism → Caveats → Conclusion
This is organized by *what you read*, not by *what you're arguing*.
### Good Structure (Argument)
> Hook with thesis → Why this matters to you → The core evidence (2-3 studies, deep) → The complication/caveat → What this means for you → Landing
Each paragraph advances the argument. Nothing is there just because you found a study.
### The Flow
1. **Hook + Thesis** (2-3 sentences)
- Lead with finding or claim
- State your position
2. **Why Rajesh should care** (1-2 paragraphs)
- Connect to his life
- Make it personal
3. **The evidence** (2-4 paragraphs)
- 3-4 studies MAX
- Go deep on each
- Explain WHY each study matters, not just what it found
4. **The complication** (1 paragraph)
- Honest about limitations
- What could be wrong
- Not "more research needed" but specific uncertainties
5. **So what for Rajesh** (1-2 paragraphs)
- Practical implication
- What should he do
- What can he actually control
6. **Landing** (1-2 sentences)
- Memorable close
- NOT a restatement of the hook
---
## Depth Over Breadth
**3-4 studies maximum. Go deep.**
### Why Breadth Fails
Ten superficial citations blur together. Rajesh can't remember any of them. He leaves with "soda is bad I guess."
### Why Depth Works
Three studies explained well—why they were done, what they found, why it's believable—creates understanding. Rajesh leaves knowing *why* to believe you.
### For Each Study You Include
Ask:
1. Why this study and not another?
2. What makes it credible?
3. What's the one finding that matters?
4. How does it connect to Rajesh's life?
If you can't answer these, cut the study.
---
## Opening Variety
**Never start the same way twice.**
### Patterns to Rotate
**Data hook:**
> "Each daily soda is linked to 27% higher diabetes risk."
**Question hook:**
> "Can you actually prevent a heart attack with diet? The answer is less clear than you'd think."
**Contrarian hook:**
> "Statins are probably overprescribed for primary prevention. Here's why."
**Personal stake hook:**
> "Your father had his MI at 55. You're 45. Here's what that means."
**Myth-busting hook:**
> "You've heard red wine is good for your heart. The evidence doesn't really support that."
**Stakes hook:**
> "If you change one thing about your diet, this should probably be it."
### Banned Openers
Never start with:
- "For decades..."
- "In recent years..."
- "In the realm of..."
- "When it comes to..."
- "It's no secret that..."
- "In today's world..."
- "As we all know..."
- "[Topic] has long been..."
These are AI tells and throat-clearing. Delete them.
---
## Scientific Rigor (Condensed)
**These are checklist items, not the star of the show.** Build them in, don't announce them.
### Causal Language
- RCTs → "caused," "led to," "produced"
- Observational → "linked to," "associated with," "predicts"
Weave this in naturally: "linked to higher risk" not "causes higher risk" when it's observational.
### Absolute Context
Don't just say "25% lower risk." Say what that means.
> "15% relative risk reduction—if your baseline risk is 10%, that's 10% vs 8.5%. One fewer event per 67 people over 10 years."
### Population Limits
Mention who was studied when it matters:
> "This was in adults with BMI over 30—whether it applies to you depends on where you start."
### Limitations
One honest paragraph per piece. Specific, not generic.
> "We can't randomize people to drink soda for 20 years. Some of this could be confounding. But the dose-response and biological plausibility make me believe most of it."
---
## Anti-AI Patterns
### Delete These Phrases
- "underscores the importance ofRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.