chore: 1.1.0 release

skills/open-kimi-ppt/reference/design_system/academic/wine-red-data/design.md

@@ -0,0 +1,62 @@
+# Wine Red Data · Academic STYLE DESIGN SYSTEM
+
+## PART A — Category Baseline (General Minimum Standard)
+
+A rigorous, formally typeset academic presentation benchmarked against top-tier research talks and thesis defenses (at the standard of NeurIPS/CHI/SIGGRAPH main conferences), where clarity of argument takes precedence over decoration. This deck must read as a reproducible scientific claim, not as marketing collateral. Use academic language throughout: standard terminology for research questions, hypotheses, evidence, significance, contributions, and limitations, with no marketing language or business jargon. Shift the visual emphasis by discipline: theoretical work should devote substantial space to equations and proof steps; computer science and engineering should be structured around system diagrams, code, execution traces, and performance curves; experimental research should tightly organize equations, charts, and images around a single conclusion; and humanities and social sciences should layer archival materials, maps, manuscripts, and other textual evidence with a sense of narrative, without compromising academic rigor.
+
+Content and layout:
+1. Use a fixed argumentative structure: Research Question → Gap in Related Work → Data and Methods → Main Results → Ablation/Analysis → Limitations → Future Work. A short deck may compress this structure, but must not change the sequence.
+2. Evidence-first slides: results tables must include baseline comparison columns, comparison charts, and architecture/process diagrams; core contributions must be expressed through formally typeset equations.
+3. Moderate information density: one argument per slide, with evidence organized around that argument. Slides should be composed, not filled—whitespace is a legitimate way to separate stages of the argument.
+
+Visual style:
+1. Aesthetic: plain, precise, and scholarly. Do not use promotional copy, decorative photography, or clip-art icons.
+2. Typography: use a clear sans serif for body text and labels (render with Liter / Chinese: MiSans); titles may use a serif when the source style does. Equations must be formally typeset (KaTeX quality), with correct equation numbering and italic treatment for variables.
+3. Color: use a two-color system for each deck—one primary structural color plus one accent, with gray carrying hierarchy; use a white or near-white background; use only one consistent warning color for negative results or ablation signals.
+4. Graphics: use thin, precise vector lines for diagrams; minimal horizontal rules for tables; and axis labels, units, and sample definitions for charts. Do not use 3D, shadows, or gradients as decoration.
+
+Structure and discipline (derived from work we recognize as benchmark quality):
+1. Every content-slide title must state an argument—a finding, not a section label: “Attention Lapses Can Be Predicted 10 Seconds in Advance,” not “Experimental Results.” The evidence supporting that argument follows on the same slide.
+2. Claim–evidence alignment: every quantitative conclusion on a slide must be supported on that same slide by a chart, table, or cited result. No orphan numbers.
+3. The main results table must include baseline comparison columns and mark the best value; show relative improvement alongside absolute values.
+4. Method slides must include the information needed for reproducibility: data scale, annotation protocol, inter-annotator agreement, and key hyperparameters. Show only the core idea as an equation; move derivations to appendix slides.
+5. Every figure must be self-contained: include axis labels with units, a legend or direct labels, and a caption area stating sample size and confidence basis. Figures must not rely on legends alone.
+6. Ablations and limitations are mandatory slides, not optional ones: ablations isolate the contribution of each component; limitations candidly state scope of applicability, failure modes, and ethics/de-identification status.
+7. Every number must include its unit, time range, dataset, and statistical basis (mean ± variance, sample size); express uncertainty through observable quantities or confidence intervals, never vague wording.
+8. Open with the problem statement plus a one-sentence contribution; close with numbered conclusions—claims, not a summary—and an explicit list of open questions.
+9. Citations appear as compact footnote lines at the bottom of the slides where they are referenced; do not create a full-slide wall of dense references unless the genre requires it.
+
+Default baseline (derived from the layout skill; PART B may override): Organize each slide around one evidence unit (figure/table/equation); give charts complete axis labels, units, and sample definitions; keep charts honest by avoiding truncated vertical axes that exaggerate differences, and distinguish correlation from causation explicitly in the copy; ensure projection readability, with body text at ≥14pt equivalent and chart labels at ≥10pt equivalent on a 960×540 canvas.
+
+**Title read-through test**: Reading only the slide titles should tell the complete story. If the sequence does not flow, the structure has not been established.
+
+Density anchor: The specific minimum standard for each style—the number of evidence modules and charts per slide, plus annotation conventions—is defined by that style’s 【Density Baseline】 reverse-engineered from the source deck. This baseline does not impose a uniform number.
+
+### Global Prohibitions (Default AI Patterns · Mandatory)
+
+1. **No default card layouts**: Unless the user explicitly requests them, never use rounded rectangles or rectangular cards to create hierarchy or alignment. Containers with a genuine information function—status indicators, assumption boxes, and quotation frames—do not count as cards. Rules, whitespace, type size, and weight contrast are preferable.
+2. **No equal-split compositions**: Unless no other layout is viable, do not default to equal thirds, equal quarters, or two-by-two matrices. Equal splits must be justified by the content structure—three scenarios naturally warrant three columns; frameworks explicitly named in the content are exempt.
+3. **No arbitrary AI-default color schemes**: Institutionally specified palettes in the body are exempt. What is prohibited is a generic, commonplace, unjustified default palette—blue-purple gradients, cyan-purple neon, rainbow glows, glass cards, and luminous borders.
+4. **No elements inconsistent with the overall style**: Do not introduce out-of-style treatments—for example, rounded icons or rounded rectangles in a sharp-edged visual system.
+5. **Keep chart backgrounds transparent**: Use transparency or the slide background, except for reversed-out charts on dark backgrounds.
+6. **No empty regions**: Do not leave large blank areas in the body-content region. Every planned area must be filled with real content; an unfilled region is the most serious form of roughness.
+
+## PART B — Signature System (Template-Specific Signature; This Section Prevails in Case of Conflict with PART A)
+
+One-sentence style signature: predominantly white-background academic lecture notes, with black type accented by wine red and purple-orange; full-slide solid-color chapter transitions; and information consistently resolved into “argument—evidence—source.”
+
+【Color Palette】The source deck uses “white-background content + sectional reskinning.” Background #FFFFFF (approximately 108/150 slides); chapters may use full-slide #820000 wine red (approximately 7 slides); covers and contents pages often use #F3F3F3 (approximately 13 slides); a standalone subsection later in the deck uses a #FFEFD9 cream background with #004032 dark-green text (approximately 13 slides), never mixed with wine red on the same slide. Primary text #000000; title purple #4F0E86 is reserved for openings/navigation; primary accent orange #E69138 is used for keywords, numbers, and arrows and occupies no more than 10–15%; fluorescent yellow #F7D05B (approximate) is used only for short horizontal brush strokes. Common chart-series colors are #0076BA, #00A2FF, #56C1FF, #D2C7EB, and #A9AAAC, with gray as the baseline; positive #00B050 and negative #FF0000 convey status only. Keep table backgrounds white or light gray; do not invent additional colored fills. Use 2–3 hues per slide, and never let the accent color fill the entire slide.
+
+【Layout Skeleton】Source-deck specifications: 720×405 pt, approximately 1100×619 px, 16:9. Place content-slide titles at top left with a left margin of approximately 4–6%. The body typically uses a 40/60 or 50/50 two-column split, with the main chart, screenshot, definition box, or table in the right column. Separate modules with whitespace and fine rules; a single gray source line often runs along the bottom, while slide numbers are not fixed throughout the deck. Special slides include centered chapter titles on light gray/light purple, full-slide declarations in wine red/black/dark green, and numbered contents pages whose current item is marked with a yellow brush stroke or colored capsule; these treatments are for transitions only. The reading path is title conclusion → chart/process → explanation → source. Reskinning applies continuously across an entire section and must not be mixed within a single slide.
+
+【Typography】PDF measurements show section-specific combinations: standard slides primarily use ArialMT/Arial-BoldMT, with OpenSans/Roboto appearing at the beginning; use Consolas for code; and SpaceGrotesk + Jomolhari in the later cream-colored subsection. When only slide images are available, do not guess font families; preserve the sans-serif/serif relationship. Body = 1x, titles 1.6–2x, large chapter text 2.3–3.4x, large numbers 1.4–2x, and footnotes 0.5–0.7x. Set titles in bold; keywords may use bold or italic orange/red. Use sentence case for body copy and all caps for short labels when appropriate; keep numbers and English abbreviations aligned to the baseline, and preserve formal equation typesetting. Render with {latin: Liter, ea: MiSans}; use JetBrains Mono for code (via customFonts).
+
+【Chart Language】Observed in the source: bar/line/scatter charts and dot distributions, radar charts, comparison tables, equation-definition tables, closed-loop processes, and screenshot comparisons. ⭐Signatures: ① The title states the conclusion first, and the chart only proves it; use one orange or wine-red series as the focal point and render the rest in gray/low-saturation blue (20+ slides). ② Show methods as horizontal steps or closed-loop arrows, with lightly filled nodes and thin black lines (15+ slides). ③ Place definitions/quotations in light-gray or pale-yellow rounded boxes beside the main figure (10+ slides). ④ Use human figures or dot arrays converging on a conclusion box to represent population distributions (approximately 8 slides). ⑤ High-density tables use only fine horizontal rules, equation columns, and a source line at the bottom (approximately 6 slides).
+
+【Signature Components】Apply the yellow brush stroke only to the current contents item or a key short phrase; keep it short and horizontal (approximately 3–4 instances). A full-slide wine-red declaration uses large white type for transitions and carries no data (approximately 7 slides). Rounded quotation/definition boxes hold direct quotations, measurement definitions, or status, with no more than 2–3 per slide. Red/orange outlines, strike-through lines, and arrows attach only to the marked object. Human/robot and similar icons serve only as process nodes or population glyphs. Photographs/screenshots must sit in a distinct frame with an explanation and must not be used as backgrounds.
+
+【Prohibited】Do not stack rounded cards without an information function; do not use glass effects, gradients, or luminous borders. Rounded containers are reserved for quotations, definitions, status, and process steps. Do not mix decorative colors; retain only one primary accent color per slide. Do not use full-slide hand-drawn textures or substitute strike-through marks for argumentation. Photographs/screenshots/illustrations may support evidence or a special cover, but must not become the default background. Do not center long passages of body text. Full-slide wine-red, black, dark-green, and cream reskinning must not jump between colors within the same chapter.
+
+【Slide Types and Layouts】Argument–evidence two-column｜One conclusion + explanation/source｜Left 40–45% text, right 55–60% chart/screenshot｜2–4 blocks｜Keyword color, quotation box, source line｜Not suitable for multiple equally weighted conclusions. Process/closed-loop diagram｜Method, lifecycle, causal chain｜Central 60–70% graphic with explanations on both sides｜1 main diagram, 4–10 nodes｜Semantic arrows and role glyphs｜Not suitable for a pure literature list. High-density data/definition slide｜Table + equation or multiple metrics｜35–45% table, 55–65% chart/definition box｜1–2 main charts or 1 table + 1 chart｜Fine horizontal rules, single-series highlight｜Not suitable for numbers without measurement definitions. Large-type viewpoint/chapter slide (special)｜Transition/strong judgment｜Full-slide 80–90% text, 0–1 metadata item｜1 statement｜Solid color or whitespace｜Not suitable for body evidence. Contents/navigation slide (special)｜Section transition｜Numbered list covering 60–80%, 3–5 items｜Current-item brush stroke/capsule｜Not suitable for chart explanation.
+
+【Density Baseline】There is no uniform minimum across the full deck. Two-column content slides typically contain 2–4 evidence blocks, 0–2 charts, and 1–3 explanation blocks, each approximately 20–60 words/characters equivalent; place whitespace between the title and evidence group and at the two-column divide. Process slides use 1 main diagram, 4–10 nodes, and 2–6 arrows. Table slides use 1 main table + 1 equation/conclusion box, with numbers right-aligned, text left-aligned, and 1–2 footnote lines; multi-chart slides use 2–4 small charts, label only key values, and do not crowd every bar with labels. Viewpoint slides contain only 1 statement of approximately 20–60 words/characters equivalent, while source notes still sit at the bottom. Close the “title—evidence” loop first, then move remaining copy down into the source line.