# Clinical Evidence Ppt Style

> Use when creating or revising clinical, medical, scientific, technical-research, literature-review, product-evidence, or mechanism-proof PPTs that need a sober evidence-driven style, manually cropped original evidence, white-background layouts, sparse dark-red emphasis, readable typography, editable PowerPoint output, and built-in PPT cleanup after ppt-master or other automated generation.

- Skill: `anklecrusher/clinical-evidence-ppt-style` (Agent Skill, multi-file: 12 files)
- Install (CLI): `npx skillmds@latest add anklecrusher/clinical-evidence-ppt-style`
- Raw SKILL.md: https://api.skillmd.com/api/skills/anklecrusher/clinical-evidence-ppt-style/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- Author: anklecrusher (https://skillmd.com/u/anklecrusher)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/anklecrusher/clinical-evidence-ppt-style

---


# Clinical Evidence PPT Style

Use this skill as the style, slide-construction, and quality-control layer for evidence-heavy PPTs. It is suited for clinical, medical, scientific, product-evidence, regulatory, mechanism-proof, and literature-review decks.

This skill does not replace source collection. If evidence still needs to be collected, first use `ppt-evidence-prep`. If the user asks to generate the deck through `ppt-master`, use `ppt-master` for generation and apply this skill during planning, slide construction, and final PPT cleanup.

## Inputs

Expected inputs may include:

- Evidence package from `ppt-evidence-prep`: slide outline, evidence matrix, quote library, image manifest, source list, and manual crop brief.
- User-provided cropped screenshots: original quote crops, figure crops, table crops, chart crops, product manual excerpts, UI screenshots, or source page screenshots.
- Redraw requirements: mechanism diagrams, process flows, logic diagrams, or comparison structures that should be made with editable PowerPoint elements.
- Existing PPTX to revise, or desired output path for a new editable PPTX.
- Style constraints: white background, black text, sparse dark-red emphasis, Chinese/English font rules, minimum font size, source footer style, or template/assets to match.
- `ppt-master` output, when the deck is generated through that pipeline and needs post-generation cleanup.

## Outputs

Expected outputs:

- Editable `.pptx` file.
- Slides with a complete evidence chain: claim, original evidence, visual explanation, reasoning, conclusion, and source footer.
- Editable text, tables, and logic/flow/mechanism diagrams wherever feasible.
- Original evidence screenshots used only where provenance or source fidelity matters.
- Native PowerPoint tables for comparison or decision slides when possible.
- Cleaned PPT text styling:
  - Chinese font: Microsoft YaHei.
  - Western font: Times New Roman.
  - Chinese proofing language set appropriately, or proofing disabled when needed to avoid red spelling waves.
  - Body text readable, normally 16-20 pt and never below 14 pt except restrained footers.
- Visual validation notes or exported preview images when tools allow.

## Core Style

The deck should feel like a concise research briefing, not a marketing template.

- White background.
- Black body text.
- Thin light-gray rules for structure.
- Dark red only for key terms, key numbers, source-highlight boxes, and final conclusions.
- Minimal shaded boxes. Prefer plain text on white.
- Original source screenshots are evidence, not decoration.
- Every inserted image must be explained before the slide states a conclusion.
- Prefer direct briefing language. Avoid AI-sounding labels such as "本页读法", "这页告诉我们", or generic narration that a presenter would not say.
- Prioritize clarity and source traceability over visual novelty.

## Evidence Chain

Every evidence slide must preserve this chain, though the exact labels do not need to appear on the slide:

1. Claim: a short title that states the page's point.
2. Evidence: original quote screenshot, table crop, figure crop, chart, or credible source image.
3. Visual explanation: what the reader should look at in the image.
4. Reasoning: why that evidence supports the slide claim.
5. Conclusion: one concise takeaway, usually with sparse dark-red emphasis.
6. Source footer: compact and unobtrusive.

Do not place references only at the end. Evidence must appear in the slide body whenever the slide is making an evidence-based claim.

## Image and Evidence Rules

- Use at most 1-2 core evidence visuals per slide unless the user explicitly asks otherwise.
- If a table is present, avoid crowding the slide with extra images.
- Do not use an image as main evidence unless it directly supports the slide claim.
- Explain each figure, chart, table, or screenshot in plain language.
- State evidence boundaries when a figure supports only part of the conclusion.
- If a page would need too many visuals, split the page.

## Manual Evidence Crop Workflow

The preferred workflow is user-controlled evidence cropping when source fidelity matters. The agent identifies the exact evidence; the user performs the final crop/highlight when needed.

When source images are full pages, dense tables, unhighlighted figures, or hard to read:

1. Do not silently crop, trim, or draw red boxes unless the user asks.
2. Extract the exact original sentence, row, cell, figure label, or chart region that should be highlighted.
3. Name the source file and page/section where it appears.
4. Explain why the crop supports the slide claim.
5. Suggest a descriptive output filename.
6. Tell the user where the cropped asset should be placed in the slide.
7. Pause before final PPT production if the missing crop is central, unless the user asks for a placeholder draft.

After the user provides manually cropped/highlighted assets, resume slide construction and focus on layout, text, tables, and visual placement.

## Redraw and Editable Output Rules

The user often needs editable `.pptx` output.

- Export or save as `.pptx`, not only PDF, PNG, or SVG.
- Keep text editable.
- Use native PowerPoint tables for comparison, boundary, summary, or decision slides when feasible.
- Use editable PowerPoint shapes for mechanism diagrams, process flows, logic diagrams, and comparison frameworks.
- Use screenshots for original evidence, paper figures, source tables, product manual excerpts, and UI evidence where source fidelity matters.
- If an image is only explaining logic rather than proving provenance, prefer an editable redraw.
- Before finishing, state whether important tables and diagrams are native editable or image-based.

## Typography and Language

- Chinese font: Microsoft YaHei.
- Western font: Times New Roman.
- Titles: usually 22-28 pt.
- Body text: preferably 18 pt, usually 16-20 pt.
- Small supporting text: 14-16 pt.
- Minimum PowerPoint font size: 14 pt, except restrained source footers when necessary.
- Chinese paragraphs should usually be justified.
- Do not shrink dense evidence pages below the readability floor; crop, simplify, or split the slide.
- Chinese narrative paragraphs should avoid mixed Chinese-English writing.
- Keep English only for necessary abbreviations, product names, proper nouns, source titles, original quotes, or established terms such as DBS, VTA, GUI, MRI, CT, or sweet spot.
- If a Chinese term is natural and accurate, use Chinese in the narrative instead of English.

## Red Emphasis

Use dark red sparingly:

- Red text only for the few words, numbers, or phrases that carry the inference.
- Red outline only around key source sentences, figure regions, or table cells when the user has supplied or requested that highlight.
- One concise red conclusion or conclusion phrase per slide is enough.

Avoid:

- Whole paragraphs in red.
- Red as a routine label color.
- Large isolated red text blocks that feel disconnected from the paragraph.
- Decorative red that does not guide reasoning.

## Layout Rules

Use stable evidence-first structures:

- Two-column evidence page: evidence on one side, explanation and inference on the other.
- Top evidence page: source evidence at the top or upper-left, interpretation below or beside it.
- Large table page: table or table crop takes the main area, concise interpretation on the side.
- Summary page: native editable table plus a direct answer sentence.

Avoid:

- Decorative gradients, icons, visual metaphors, or marketing-style hero layouts.
- Many tinted cards.
- Nested cards.
- Small source screenshots that cannot be read at presentation scale.
- Conclusions that are not visibly connected to a specific quote, figure, table, or source.

## Built-In PPT Cleanup

When the deck is generated or revised, especially after `ppt-master`, this skill includes final PPT cleanup. Do not treat cleanup as an optional separate concept.

Check and fix:

- Chinese font is Microsoft YaHei.
- Western font is Times New Roman.
- Chinese text has Chinese proofing language where possible.
- If PowerPoint shows large red spelling waves under Chinese text, set proofing language correctly or disable proofing for generated text.
- Body text is normally 16-20 pt and never below 14 pt unless it is a restrained source footer.
- Paragraph alignment follows the user's requirement, usually justified for Chinese body text.
- Red emphasis is sparse and meaningful.
- Text does not overlap images, tables, or other text.
- Source footers are present but visually quiet.
- Important tables and logic diagrams remain editable when feasible.

## Workflow

1. Confirm inputs and deck type.
   - Check whether `ppt-evidence-prep` outputs exist.
   - Inventory available crops, figures, tables, screenshots, and redraw needs.
   - If central evidence crops are missing, prepare or update a manual crop brief before final production.

2. Plan slides from evidence.
   - For each page, identify the claim, evidence image(s), visual explanation, reasoning, conclusion, and source footer.
   - Keep to the slide asset budget unless the user asks otherwise.
   - Mark which visuals are screenshots and which diagrams/tables should be editable redraws.

3. Draft or revise the deck.
   - Build each slide around the evidence first.
   - Add explanation text that starts from what the image literally shows.
   - Add reasoning and conclusion after the explanation.
   - Keep the visual structure plain, stable, and readable.

4. Handle tables and diagrams.
   - Use native editable tables when possible.
   - Use editable shapes for logic, flow, mechanism, and comparison diagrams.
   - Use screenshots only where source fidelity is the point.

5. Apply typography, language, and red-emphasis rules.
   - Use Microsoft YaHei for Chinese and Times New Roman for Western text.
   - Avoid unnecessary Chinese-English mixing in Chinese narrative paragraphs.
   - Use dark red only for key terms, key numbers, and conclusion-critical phrases.

6. Run built-in PPT cleanup.
   - Normalize fonts, sizes, alignment, and proofing behavior.
   - Remove or prevent red spelling waves caused by wrong language/proofing settings.
   - Confirm key text, tables, and diagrams remain editable.

7. Validate visually.
   - Export preview images or inspect the PPT when tools allow.
   - Check readability, image clarity, text overlap, excessive whitespace, overuse of red, source footers, and evidence-to-conclusion linkage.

8. Report completion.
   - Provide the output PPTX path.
   - Mention any low-resolution evidence, missing manual crops, or image-based elements that could not be made editable.
   - Confirm whether important tables/diagrams are native editable.

## Completion Criteria

A finished deck in this style has:

- Claim-driven titles.
- Original evidence visible on evidence slides.
- Readable manually cropped/highlighted evidence, or a clear crop brief if assets are not ready.
- A short explanation of what each image says.
- Reasoning that connects evidence to the claim.
- Sparse dark-red emphasis for key terms and conclusions.
- Source footers on evidence slides.
- Editable tables, text, and redrawable diagrams where feasible.
- Correct Chinese/Western fonts.
- No distracting red spelling waves under Chinese text.
- No hidden reliance on references the audience cannot see.