shiquda/open-pptd-skill / skills/open-pptd
open-pptd
FlaggedCreate, edit, reverse-decompile, and export presentations using the open PPTD format and native pptd compiler. For every PPT task, default deliverables are BOTH (1) a self-contained PPTD project folder (deck.pptd manifest + pages/*.page) and (2) a locally compiled native .pptx with vector shapes, connector arrows, LaTeX math formulas, speaker notes, and native tables. Completely offline — zero dependency on browser automation or cloud logins.
reference/slides_categories/education-training.md
View on GitHub# Education & Training
Scope: courseware, job-skill training, operation guides, teacher materials, study handbooks, public education, onboarding training, capability building, and knowledge popularization. The reader may be listening live or reading independently; their task is not merely to understand a page, but to form understanding they can retell, methods they can execute, and actions they can transfer.
> Core position: design the learning first, the pages second; complete the content skeleton first, the visual system second. Reference samples only provide design cues worth borrowing — they are not default templates, nor styles that must be replicated. Courseware should carry enough content to support learning; do not turn body content into posters or whitespace albums for the sake of a "premium feel."
## 1. Define the Learning Task First; Do Not Pick a Style First
Before production, write down the following information; if any of it is missing, fill it in with reasonable assumptions and mark it in the design document.
- **Learner:** age, level of expertise, prior knowledge, easily confused terms, accessibility needs.
- **Usage:** live projection, printed handouts, self-study reading, or mixed use; roughly how long each page stays in view.
- **Entry state:** what the learner does not know now, cannot do now, or is prone to getting wrong at which step.
- **Exit capability:** after the material, what the learner can explain, differentiate, judge, operate, check, or retell. Goals must be observable.
- **Material boundaries:** which parts are external facts, and which are team inferences, fictional exercises, illustrative data, or to-be-filled material.
- **Real task:** in what work, classroom, or life scenario the learner will next apply this method.
Do not first decide "use blue, use rounded corners, use some Sample" and then cram content into the pages. Every visual choice must be explainable as: it helped the learner see which relationship, remember which step, or complete which judgment.
## 2. General Prohibitions
The following are red lines running through the entire deck; they take effect before all layout and visual rules, and unless the user explicitly requests otherwise, none may be violated.
- **No cards by default:** unless the user explicitly requests it, strictly forbid using rounded rectangles or rectangular cards to build hierarchy or alignment. Line segments, whitespace, and font-size/weight differences are better solutions.
- **No evenly divided compositions:** unless no other layout is available, do not default to one-third splits, four-way splits, or 2×2 matrices — including formulaic patterns such as "title + three parallel blocks + conclusion."
- **No mediocre, common, or AI-typical color schemes:** unless the user explicitly requests them, strictly forbid blue-and-white pairings, blue-purple gradients, cyan-purple neon, rainbow flares, glassmorphism cards, and glowing borders.
- **No elements that clash with the overall style:** no styles from outside the chosen style may appear, such as using rounded icons or rounded rectangles within a sharp style.
## 3. The Teaching Loop: Every Chapter and Every Page Needs a Take-Away Action
The default learning path is: **orientation → comprehension → demonstration → practice → feedback → transfer**. Not every short material needs a separate page for each stage, but when a stage is missing, you must be able to say that the task itself does not call for it — not that the page ran out of space.
- In live teaching, click-triggered animations may progressively present questions and answers, derivations, physical or mathematical processes, operational steps and error correction, or simulated physics or chemistry experiments; each click advances only one learning step, and self-study and printed materials use no animations by default.
- **Orientation:** explain why this is worth learning, what the learner can do after completing it, and how it relates to the chapters before and after. Use a real problem or scenario instead of grand slogans.
- **Comprehension:** first give one core definition the learner can retell, then the boundaries, composition, counterexamples, or relationships. New terms must not appear only in figure captions.
- **Demonstration:** show the process and the intermediate judgments, not just the final answer; put the key forks, the basis for each choice, and the common misconceptions on the same reading path.
- **Practice:** specify the input, the actions, and the completion criteria. Practice scenarios may be fictional, but must be labeled "practice scenario / illustrative material."
- **Feedback:** explain why an answer is right or wrong, where the error lies, and how to check next time. Answer pages and question pages must be distinguishable at a glance.
- **Transfer:** connect to real use with checklists, templates, job-aid cards, or next-step actions; do not substitute a slogan for transfer.
Each page carries only one primary learning action:
- Concept pages get the learner to state clearly "what it is and where its boundaries lie."
- Method pages get the learner to know "when to use it and how to choose."
- Process pages get the learner to know "what to do first, what next, and how to check."
- Demonstration / case pages let the learner see the judgment process.
- Practice pages get the learner to act or make a choice.
- Feedback / review pages correct and distill principles.
Titles must foretell the page's takeaway. Prefer question sentences, conclusion sentences, or "action + object"; avoid mere section labels like "Background," "Overview," or "Related content." Put all key definitions, steps, and answer criteria into the material — do not rely on the presenter to fill them in live.
## 4. Default Density for Courseware: Full Content; Whitespace Has a Job
Courseware is not a poster, nor a full script shrunk down and plastered across pages. The default density is "medium, leaning full": the learner can spot the main object at a glance, and can also find, on the same page, the support needed to understand or act.
- Body pages usually have at least three layers: learning question / conclusion title → one main exhibit → one layer of explanation, task, check, or source.
- As a starting point, about 60% or more of a body page's main content area should be occupied by meaningful text, figures, tables, flows, or exercises; this is a density guardrail, not a hard ratio. Projection pages may reduce text and self-study pages may add explanation, but neither may use emptiness to mask insufficient content.
- Whitespace is for grouping, establishing reading order, and highlighting key points — it is not the page's main product. Except for covers, section openers, key manifestos, or closing pages, do not produce consecutive pages of "one sentence + a big blank."
- A page may have quiet areas, but only with an explicit reason: a pause, a transition, a memory anchor, or an emotional close. The reason should be writable into the page outline, not explained after the fact.
- High-density pages reduce decoration and add grouping and labels; low-density pages add retellable definitions, examples, check questions, or next steps — not random graphics.
- One set of courseware may have many page types, but the grid, the title anchor, the type hierarchy, the navigation position, and the color semantics stay stable. A unified system does not mean copying the same template onto every page.
Let density vary with the learning action:
| Page type | What it carries | Default density | What must be visible |
| --- | --- | --- | --- |
| Route / opening | Learning questions, goals, chapter relationships | Low to medium | Where we come from and where we are going |
| Core concept | Definitions, boundaries, main relationships | Medium | One definition and one intuitive anchor |
| Demonstration / case | Material, process, judgments, conclusion | Medium to high | The difference between evidence and interpretation |
| Practice / worksheet | Input, operations, completion criteria | Medium to high | What the learner must do right now |
| Feedback / review | Answers, reasons, error correction, principles | Medium | Why this judgment is made |
| Transfer / summary | Checklists, templates, resources, next steps | Medium | How to use this after leaving the material |
## 5. Division of Labor: Text, Graphics, Examples, and Exercises Do Not Impersonate Each Other
- Text explains meaning, boundaries, conditions, and the basis for judgments.
- Graphics reveal real relationships: flows for sequence, trees or nesting for hierarchy, parallel regions for comparison, one-way chains for causality, and cycles only where a genuine loop exists.
- Examples lower abstraction, but facts, results, and explanations must be layered; a case's teaching role is labeled first (demonstration, comparison, diagnosis, or transfer).
- Exercises test mastery; do not fill pages with irrelevant games.
One structural diagram expresses one primary relationship. Every connector needs a direction or a meaning; delete decorative arrows, meaningless rings, and nodes that exist only to fill the page. A key model is explained in full at first appearance, then keeps the same name, shape, color, and reading direction.
External facts, data, quotations, and method sources stay close to their corresponding exhibits, stating at least the source entity and the necessary measurement basis. Illustrative data, team inferences, and fictional material must be explicitly labeled. Without reliable data, use schematic structures or qualitative comparisons — never generate realistic-looking precise values.
Images are used only when "seeing works better than describing." An image may serve as observational evidence or establish a situation; purely decorative images must not crowd out the main learning object. The content of screenshots, photos, illustrations, and charts must be chosen fresh for each new topic — do not copy an object just because a reference sample used it.
## 6. Order of Visual Decisions: Samples Are a Reference Library, Not an Answer Key
Make visual decisions in this order:
1. Complete the learning objectives, the chapter path, and the page-by-page outline.
2. Select each page's main learning object and density tier — do not pick colors or motifs first.
3. Based on the topic, audience, scenario, and evidence types, write a one-page visual brief: temperament, grid, type hierarchy, color roles, graphic grammar, image strategy, component boundaries, headers/footers, and density.
4. When a reference sample is needed, extract only "explainable design decisions," then translate them into the current topic.
5. Form one main system plus several page-type variants; do not stitch together the motifs, fonts, cards, and colors of multiple samples.
### The Correct Way to Use Reference Samples
When you receive a Sample, template, or screenshot, first look at the page's actual visual effect (do not just extract the copy), then write a "reference extraction card" recording only:
- **Borrowable functions:** e.g., a stable grid, role color codes, step navigation, evidence zoning.
- **Borrowable tone:** e.g., restrained, friendly, rigorous, live-event feel, or public-communication feel.
- **Borrowable graphic grammar:** e.g., parallel modules, time paths, nested hierarchy, or photo frames.
- **Objects that cannot be inherited:** the sample's brands, photos, characters, specific copy, proprietary color values, and decorative motifs.
- **Applicable page types:** only note whether it suits concepts, cases, exercises, or steps — do not expand it into a whole-deck template.
One material borrows at most two or three mutually compatible features from a single reference sample; after borrowing, re-name the semantics of colors and components. Without a sample, still build the system yourself from the learning task. Sample 1 enjoys no default priority; it is only one reference direction for editorial-style courseware.
## 7. Reference Directions (Inspiration Only; New Directions May Be Generated)
These directions help you understand design choices quickly; they are not fixed palettes, font tables, or page templates. Take only the parts that fit the task.
### Direction A: Editorial Study Handbook (May Reference Sample 1)
- **Borrowable:** a clear title–exhibit–explanation hierarchy; a stable reading grid; few and explicit accent colors; cases, methods, and sources placed in their own zones; images separated from text.
- **Suits:** concept teaching, methodology, case reading, blended courses, and materials that require self-study.
- **No need to copy:** the blue-and-white palette, geometrically cropped images, capsule labels, fixed hairlines, large chapter whitespace, or any specific photo subject.
- **Density note:** body pages are mainly medium density; cases and exercises can be fuller; only opening and closing pages drop density noticeably.
### Direction B: Role / System Infographics
- **Borrowable:** stable color codes distinguishing roles or modules; nesting, sectors, matrices, or interlocking blocks expressing real relationships; action text kept tight against its owning module.
- **Suits:** multi-role collaboration, public education, system composition, division of responsibilities, and action maps.
- **No need to copy:** colorful collages, full-page color blocks, flat silhouettes, right-angled modules, or any specific color combinations.
- **Density note:** the smaller the module, the shorter its text; relationship-diagram pages keep the necessary gaps; role-action pages may be denser, but meaning must never ride on color alone.
### Direction C: Steps / Work Records
- **Borrowable:** a persistently visible progress cue; numbered steps; clear containers for photos, screenshots, or worksheets; layered actions, risks, and check items.
- **Suits:** operation guides, compliance, safety, job skills, and on-site training.
- **No need to copy:** file folders, paper textures, monospaced labels, fixed bottom stacks, or any skeuomorphic decoration.
- **Density note:** each step page answers at least "what to do, why, and how to check"; route and review pages are not emptied for decoration.
### Direction D: Evidence / Data Editorial (Build Your Own as Needed)
- **Borrowable:** making charts, tables, or screenshots the main exhibit; the title gives the learning question or conclusion first; side text explains the measurement basis, the observation points, and the next step.
- **Suits:** professional popular-science content, results interpretation, before-after comparison, research training, and courses needing evidence support.
- **No need to copy:** dashboard black backgrounds, rainbow charts, giant numbers, dense annotations, or industry-specific brand styles.
- **Density note:** data pages may be full, but each chart serves only one question; without data, do not force charts just to "look like a report."
If the topic fits none of these directions, establish a new reference direction and write down "what it helps the learner accomplish" — rather than adding more decorative rules to it.
## 8. Page Skeletons: Choose the Learning Action First, Then the Layout
Every page is written as a minimal closed loop of "title + main exhibit + support layer + action / check + source." The following page types are composable — not all must be used.
- **Learning route:** learning questions, chapter order, and exit capabilities; use short sentences and a path, not a long table of contents.
- **Concept page:** one definition + boundaries / composition + one intuitive example or structural diagram.
- **Method map:** the overall framework + current step / current module + a cue for what unfolds next.
- **Demonstration page:** input material + intermediate judgments + basis for choices + result; put the error-prone forks on the same path.
- **Case-evidence page:** a case-role label + factual material + interpretation + transferable judgments + source.
- **Comparison / error-prone page:** two approaches or states placed side by side on the same skeleton + judgment criteria + common mistakes.
- **Practice page:** task instructions + input / scenario + work area + completion criteria; do not hide the answer on the same page.
- **Feedback page:** the reference approach + reasons + error location + how to check next time; make clear that this is the answer or the feedback.
- **Transfer page:** checklists, templates, job-aid cards, resources, and next-step actions; avoid merely writing "apply what you learned."
A presentation version may move extended explanation into speaker notes, but the page must still keep the learning question, the main exhibit, the task / judgment criteria, and the necessary sources. A self-study version writes the definitions and conditions needed for understanding on the page itself.
## 9. Minimum Constraints for the Visual System
### Grid and Hierarchy
- First fix the main content area, the title anchor, the content's left axis, and the page-number / source position; then decide the page variants.
- Each page has only one first visual entry: the learning question or principle is seen first, the main exhibit second, the explanation / task / source third.
- Titles, body text, figure notes, and sources use the same type family or a clear two-family relationship; the Chinese fallback must genuinely work. Do not force in a font that does not support Chinese just to imitate a sample.
- Titles and body text establish hierarchy through size, weight, and position. Projection materials prioritize body-text readability; self-study materials may add explanation, but body text is never pressed down to footnote size.
- Ordinary body text reaches at least 4.5:1 contrast against the background; when contrast is insufficient, change the text color or background directly — do not patch it with shadows and strokes.
### Color
- Without brand guidelines, first choose a neutral background, one structural color, and one necessary semantic accent: few and stable colors are easier to learn from than many and lively ones.
- Every color carries a fixed meaning (chapter, role, state, focus, or link) and must not decorate randomly; always also encode with text, shape, position, or icons alongside color.
- A page is usually governed by a neutral background + one main structural color; add a second color family only when a genuine role / category mapping exists.
- Body text on dark grounds uses high-contrast light colors; body text on light grounds uses near-black. Small type never sits on high-saturation colors.
**Starting point when there is no sample (not a fixed style):** adopt a near-white or light-gray background, near-black body text, one structural accent color, and one low-frequency semantic color; build the title-and-body hierarchy with a neutral sans-serif; pair a fixed title left axis with a "main exhibit + explanation / task" layout; keep body pages medium-leaning-full, with only covers, section openers, and closing pages noticeably dropping density. Then adjust by topic, audience, and material evidence — do not treat this starting set as a new template.
### Cards, Components, and Graphics
- Cards are used only for grouping, carrying states, or forming operable regions; continuously stacking cards is not a default layout.
- Rounding, right angles, strokes, shadows, and capsules are all component grammar — once decided, stay consistent throughout; do not take one from each different Sample.
- Shadows, textures, gradients, and decorative icons are used only when they serve a hierarchical or situational function. Anything whose removal does not hurt understanding should be removed.
- Default Office charts, SmartArt, rainbow palettes, thick black table frames, and untuned bullet lists must be redone.
### Images and Charts
- Every image must state "what to see and why it needs to be seen"; evidence images, operation screenshots, and situational images are each labeled with their purpose.
- Charts carry "see the relationship," side text carries "how to interpret and what to do next"; do not repeat the chart's labels verbatim.
- Charts keep the necessary units, time range, legend, key labels, measurement basis, and source; delete non-essential gridlines, frames, and decoration.
- Tables use clear headers, horizontal separators, correct alignment, and the necessary focus rows; do not use full rows of high-saturation color or color alone to express states.
## 10. Model Execution Protocol
### 1. Content First
First write the learner, entry state, exit capability, usage, evidence boundaries, and practice tasks; then write the chapter path. Record at least, for every page:
> Chapter / page type / learning action / title / main exhibit / explanation or task / feedback or check / source / density tier
Check whether every chapter has comprehension, demonstration, application, feedback, and transfer; if not, first add the content or note why it does not apply.
### 2. Reference-Sample Extraction
If there is a Sample, template, or screenshot, finish the reference extraction card before writing the visual brief. The card must not directly copy the object layer (brands, photos, copy, proprietary color values, proprietary motifs); keep only the transferable structure, tone, and graphic relationships. Samples 1, 2, and 3 are all merely candidate references and must not become implicit defaults.
### 3. Visual Brief
The visual brief states at least:
- the audience and usage environment;
- the topic's temperament and density targets;
- one main grid and two to six page types;
- the hierarchy of title / body / source;
- the semantic division of colors and the contrast plan;
- the graphic grammars for flows, hierarchy, comparison, and evidence respectively;
- the usage boundaries for images, screenshots, and illustrations;
- the fixed positions of header, footer, page number, source, and navigation;
- which elements appear only on covers, section pages, or closing pages.
### 4. Page-by-Page Generation
- Write titles that foretell the learning takeaway.
- Choose the single main learning object.
- Complete the definitions, boundaries, labels, tasks, check criteria, and sources.
- Apply the grid, hierarchy, and components per the visual brief — do not copy a Sample page by page.
- Delete graphics, images, quotes, and repeated text that serve no teaching function.
- Check content and overflow first, then make visual fine-tuning; do not mask excessive content by shrinking font size.
### 5. Pre-Delivery Validation
Use the existing PPTD / PPTX validation and screenshot workflow to check overflow, overlap, truncation, garbled text, low contrast, missing page numbers, and missing sources. Review key pages individually at minimum; do not declare completion from thumbnails alone.
## 11. Delivery Acceptance and Reverse Checks
### Content and Teaching
- Reading only the titles, can you state the complete learning path — not a string of section names?
- With the title covered, can the main exhibit still say what it teaches and what to do?
- Does each page carry only one main learning action, and does the explanation truly lead to action?
- Do exercises specify input, actions, and completion criteria? Does feedback explain the reasons and the error-correction method?
- Are facts, illustrative material, inferences, and fictional material clearly distinguished? Does external evidence have sources and measurement basis?
- Do the same concepts, roles, steps, and states keep the same name, color, and shape throughout?
### Density and Visuals
- Do body pages have enough content to support learning, rather than big titles plus blanks? Do consecutive sparse pages have an explicit teaching reason?
- Does each page have one visual entry and one quiet area; are the title, charts, cards, and big images all competing for first attention at the same time?
- With color removed, are steps, roles, states, and categories still legible?
- With the reference sample's photos, color values, and motifs removed, is the courseware still a self-consistent system?
- Is there only one main visual grammar, while different learning actions may use different page types?
- Are images sharp, relevant, unstretched, with no text pressed over complex areas?
- Do charts, tables, and structural diagrams express real relationships, rather than filling the page?
### The Final Cut
Ask item by item: "If I delete this, what does the learner lose?" If the answer is only "the page will look emptier," delete it. What truly needs filling is not decoration, but definitions, examples, judgment criteria, exercises, feedback, or transfer actions.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |