Jiuyuan defense ppt style

Jiuyuan Defense PPT Style

Description

Use this skill to create or revise a concise academic PowerPoint deck that feels like the user's doctoral defense slides: restrained, medical, credible, readable on a projector, and suitable for mentor or collaborator discussion.

Use it together with the presentations skill when generating or editing .pptx files.

When to Use

• OpenScar mentor, collaborator, or Shanghai Ninth People's Hospital briefings.
• Medical project presentations that should inherit the user's doctoral-defense typography and evidence rhythm.
• Decks that need to build confidence while withholding target rankings, implementation details, or private data.

Do Not Use

• Generic sales pitches, investor decks, or decorative marketing presentations.
• Clinical decision support, patient diagnosis, treatment selection, or individualized medical advice.
• Situations where the user explicitly requests another visual system.

Required Inputs

• User goal: who the deck is for, what decision it should unlock, and what must stay confidential.
• Project facts: only use facts available from the user's files or explicit request.
• Reference style: default to /Users/doc_k/Desktop/毕业/论文原始文件/论文/答辩/沈康杰答辩PPT.pptx when available.

Read references/style-system.md before designing slides.

Workflow

1. Inspect the reference PPTX if accessible.

   • Identify cover, section divider, bullet, figure + text, and conclusion slide patterns.
   • Do not copy the old scientific content.
   • If the user says the output must be close to the reference style, duplicate selected source slides as the starter deck and replace content inside inherited layouts.

2. Define the deck as a decision-support artifact.

   • State the audience decision in one sentence.
   • Limit the deck to 8-14 slides unless the user requests a full academic talk.
   • Prefer one claim, one visual, or one request per slide.

3. Build the narrative.

   • Start with why the project matters to the mentor or collaborator.
   • Show what is already real: local assets, demos, templates, validation, governance.
   • Ask for the smallest useful collaboration step.
   • End with a concrete next action.
   • Use academic evidence rhythm, not startup pitch rhythm.

4. Protect confidential content.

   • Do not expose ranked targets, detailed algorithms, private data paths, patient identifiers, or reusable internal operating details.
   • Replace implementation detail with governed workflow diagrams, readiness tables, and bounded asks.
   • Add explicit no-claim/no-overreach language for medical projects.

5. Render and verify.

   • Export slide previews.
   • Check that Chinese text does not overlap, captions are readable, and template residue is removed.
   • Inspect exported text for old-template content, patient identifiers, and unsupported medical claims.

Output Format

• Deliver an editable .pptx.
• Use Chinese as the main explanatory language.
• English labels are acceptable inside schematic figures.
• Keep visuals simple and projectable; do not use decorative stock-like imagery unless it directly supports the topic.
• Prefer thesis-defense visual density over SaaS-style cards: fewer rounded cards, more figure + caption + conclusion layouts.
• If reference-slide speaker notes are inherited, clear them.

Safety

• The deck does not diagnose, recommend treatment, predict recurrence, or claim a validated biomarker or therapeutic target.
• It does not expose patient identifiers, recognizable clinical photographs, protected links, or unauthorized omics data.
• A clinician or clinician-scientist must review medical claims, collaboration asks, and specimen/data governance language.
• Escalate unsupported claims, ambiguous consent, or identifiable data to the responsible clinician-scientist before presentation.

Examples

Use the Jiuyuan defense style to turn the OpenScar seven-direction architecture into a 12-slide mentor briefing. Emphasize ScarAtlas and target discovery, keep implementation details confidential, and leave experimental image placeholders editable.

Revise this OpenScar PPTX so the title, typography, figure-caption rhythm, and conclusion slides match my doctoral defense deck. Preserve all scientific boundaries and remove inherited speaker notes.

Integration

• Use presentations or pptx for editable PowerPoint generation and modification.
• Read references/style-system.md before layout work.
• Use the OpenScar project files as the factual source of truth; do not invent progress, datasets, results, or publication claims.
• Render every slide to images and visually inspect typography, clipping, confidential content, and template residue before delivery.

Failure Modes To Avoid

• A marketing deck: too much hero copy, vague value propositions, or decorative graphics.
• A generic modern deck: rounded card grids, pastel dashboards, or startup-style pipeline graphics that do not resemble the user's defense PPT.
• A full protocol leak: too much algorithm, target ranking, code path, or operating detail.
• A manuscript talk: too many dense results slides for a mentor ask.
• A template clone: old disease terms, speaker notes, or figure captions left inside the new PPTX.