Ppt Evidence Prep

PPT Evidence Prep

Use this skill before making an evidence-heavy PPT. The goal is not only a bibliography. The goal is a local, traceable evidence package: every slide conclusion has a matching source, source location, image/table plan, explanation of what the evidence proves, and a clear boundary for what it does not prove.

This skill stops before final slide design. If the user asks to create or revise the PPT itself, use clinical-evidence-ppt-style and, when requested, ppt-master after this evidence package is ready.

Inputs

Expected inputs may include:

• User request: topic, question, thesis, target audience, and desired slide count or scope.
• Existing project files: Markdown notes, drafts, PDFs, manuals, saved webpages, patents, product pages, screenshots, and prior PPTs.
• Source preferences: papers, official manuals, product pages, patents, guidelines, clinical trial records, news, or internal materials.
• Existing folders such as references/, images/, raw_images/, or user-provided cropped assets.
• User constraints: concise deck, original evidence screenshots, editable redraws, maximum image count per page, citation format, or language preference.
• Known conclusion, if the user already has one.

Outputs

Create or update project-local artifacts, usually:

• references/: downloaded or localized source files with stable descriptive names.
• images/ or raw_images/: extracted figures, page screenshots, table crops, interface screenshots, or candidate evidence images.
• <topic>PPT大纲.md: slide-by-slide outline with claim, evidence, image/table plan, source, and explanation.
• <topic>引用原文.md: quote/source library with short source names, full titles, local paths, page/figure/table locations, and access links.
• Manual crop brief: exact user cropping instructions for pages, regions, figure/table/text targets, suggested filenames, and intended slide placement.
• Image usage manifest: for every candidate image, mark whether it is direct-to-slide, manual-crop-needed, redraw-reference, backup, or do-not-use.
• Evidence matrix: a table matching each slide claim to source quote, source location, image file, what it proves, and evidence boundary.

Workflow

1. Read project context first.

   • Open the user's existing notes and local source folders before searching externally.
   • Capture current conclusions, disputed points, terminology, and the exact claim the PPT must support.
   • Do not broaden the topic beyond what the user asked.

2. Convert the topic into a claim tree.

   • Write one core claim in plain language.
   • Split it into slide-sized subclaims.
   • Mark adjacent concepts that could be confused and must be separated in the deck.

3. Build an evidence matrix before drafting slides.

   Claim	Source quote	Source file/page	Image file	What it proves	Evidence boundary
   Short conclusion	Concise original quote or figure/table reference	Local file and page/section	images/descriptive_name.png	Why it supports the claim	What this source does not prove

   Rules:

   • Evidence must support the exact claim, not merely be related.
   • Prefer primary papers, official manuals, patents, product documentation, guidelines, or clinical trial records.
   • Use secondary sources or news only as context unless the user explicitly asks otherwise.
   • If evidence is indirect, label it as inferred instead of presenting it as direct proof.

4. Collect and localize sources.

   • Download or copy key PDFs/manuals/webpages into references/ when allowed.
   • Use stable descriptive filenames.
   • If a source cannot be downloaded, list it with a clear URL and reason.
   • Keep short source names distinguishable and reusable, such as ILS 12例研究, Boston程控手册, or 自动程控安全约束.
   • Hyperlink display text should be the source short name, not generic labels such as PDF下载, 网页, or PMC页面. If the same source has multiple links, use 短名称 and 短名称原文.

5. Control slide asset budget.

   • Default to at most 1-2 core evidence visuals per slide.
   • If a slide includes a table, reduce other image count.
   • Move surplus images into backup status instead of forcing them into the outline.
   • Every selected image must have a reason to appear on that slide.

6. Classify every candidate image. Use these labels:

   • direct-to-slide: already cropped/readable and should be inserted as evidence.
   • manual-crop-needed: user should crop/highlight the exact region before PPT production.
   • redraw-reference: use only as a reference for an editable redraw.
   • backup: relevant but not part of the main slide plan.
   • do-not-use: not directly supportive, too low quality, or redundant.

7. Decide whether to screenshot or redraw.

   • Original quotes, paper figures, tables, product manual pages, and UI screenshots usually stay as evidence images.
   • Mechanism diagrams, process flows, logic diagrams, comparison frameworks, and dense/low-resolution mixed-language diagrams should usually be redrawn as editable PPT elements later.
   • If a source image is used only to explain logic rather than prove provenance, prefer a redraw.

8. Prepare manual crop instructions before PPT production. For each needed crop, provide:

   • Source file and page/section.
   • Exact region to crop.
   • Crop type: figure, table, sentence, paragraph, interface area, or chart region.
   • Why this crop supports the slide claim.
   • Suggested filename.
   • Intended slide number and placement.

   Pause for user-supplied crops if the missing crop is central to the deck, unless the user explicitly asks for a placeholder draft.

9. Write read-the-visual notes. For every image that will enter the deck, write:

   • What the reader should look at.
   • Which number/axis/row/region matters most.
   • Which slide conclusion it supports.
   • What the image should not be over-interpreted to prove.

10. Write the quote library. Include:

• Source short name and full title.
• Local path and access URL.
• Page, figure, table, section, or paragraph location.
• Concise original quote or figure/table description.
• Chinese explanation of what the evidence proves.
• Matching image filename or crop request.
• Suggested PPT usage and citation wording.

11. Write the PPT outline. For each slide, include:

• Slide title as a claim, not a vague topic.
• One-sentence slide conclusion.
• Evidence quote or figure/table reference.
• Suggested image(s), with usage label.
• Read-the-visual explanation.
• Reasoning from evidence to conclusion.
• Source footer suggestion.

12. Validate local completeness.

• Check that every referenced image exists, or is listed in the manual crop brief.
• Check that every local PDF/manual/path exists, or is listed as a download gap.
• Check that every slide has conclusion, source, evidence location, image/table plan, and what-it-proves explanation.
• Check that no slide is overloaded with visuals.
• Check that all links use meaningful source names.

Failure Recovery

• If sources disagree, separate strong evidence, supporting evidence, and uncertain or inferred claims.
• If the original claim is too broad, narrow it to what the evidence can prove.
• If a screenshot is unreadable, request a closer crop or plan an editable redraw.
• If no direct source proves the wording, rewrite the slide conclusion to match available evidence.
• If a PDF path or tool fails because of Chinese paths, use a temporary ASCII working alias while keeping final files in the project folder.

Completion Criteria

The evidence prep is complete when:

• The PPT can be made from local Markdown files, references/, and images/ without going back online.
• Every slide conclusion has a paired source and source location.
• Every image has a usage label and read-the-visual note.
• Manual crop needs are explicit enough for the user to crop quickly.
• Redraw needs are clearly separated from evidence screenshots.
• Source links are traceable and named by source, not by access method.