codewave-openclaw-installer 1.0.2 → 2.1.1

package/skills/ppt-master/references/executor-base.md

@@ -0,0 +1,198 @@
+# Executor Common Guidelines
+
+> Style-specific content is in the corresponding `executor-{style}.md`. Technical constraints are in shared-standards.md.
+
+---
+
+## 1. Template Adherence Rules
+
+If template files exist in the project's `templates/` directory, the template structure must be followed:
+
+| Page Type | Corresponding Template | Adherence Rules |
+|-----------|----------------------|-----------------|
+| Cover | `01_cover.svg` | Inherit background, decorative elements, layout structure; replace placeholder content |
+| Chapter | `02_chapter.svg` | Inherit numbering style, title position, decorative elements |
+| Content | `03_content.svg` | Inherit header/footer styles; **content area may be freely laid out** |
+| Ending | `04_ending.svg` | Inherit background, thank-you message position, contact info layout |
+| TOC | `02_toc.svg` | **Optional**: Inherit TOC title, list styles |
+
+### Page-Template Mapping Declaration (Required Output)
+
+Before generating each page, you must explicitly output which template (or "free design") is used:
+
+```
+📝 **Template mapping**: `templates/01_cover.svg` (or "None (free design)")
+🎯 **Adherence rules / layout strategy**: [specific description]
+```
+
+- **Content pages**: Templates only define header and footer; the content area is freely laid out by the Executor
+- **No template**: Generate entirely per the Design Specification & Content Outline
+
+---
+
+## 2. Design Parameter Confirmation (Mandatory Step)
+
+> Before generating the first SVG page, you **must review the key design parameters from the Design Specification & Content Outline** to ensure all subsequent generation strictly follows the spec.
+
+Must output confirmation including: canvas dimensions, body font size, color scheme (primary/secondary/accent HEX values), font plan.
+
+**Why is this step mandatory?** Prevents the "spec says one thing, execution does another" disconnect.
+
+---
+
+## 3. Execution Guidelines
+
+- **Proximity principle**: Place related elements close together to form visual groups; increase spacing between unrelated groups to reinforce logical structure
+- **Absolute spec adherence**: Strictly follow the color, layout, canvas format, and typography parameters in the spec
+- **Follow template structure**: If templates exist, inherit the template's visual framework
+- **Main-agent ownership**: SVG generation must be performed by the current main agent, not delegated to sub-agents, because each page depends on shared upstream context and cross-page visual continuity
+- **Generation rhythm**: First lock the global design context, then generate pages sequentially one by one in the same continuous context; grouped page batches (for example, 5 pages at a time) are not allowed
+- **Phased batch generation** (recommended):
+  1. **Visual Construction Phase**: Generate all SVG pages continuously in sequential page order, ensuring high consistency in design style and layout coordinates (Visual Consistency)
+  2. **Logic Construction Phase**: After all SVGs are finalized, batch-generate speaker notes to ensure narrative coherence (Narrative Continuity)
+- **Technical specifications**: See [shared-standards.md](shared-standards.md) for SVG technical constraints and PPT compatibility rules
+- **Visual depth**: Use filter shadows, glow effects, gradient fills, dashed strokes, and gradient overlays from shared-standards.md to create layered depth — flat pages without elevation or emphasis look unfinished
+
+### SVG File Naming Convention
+
+File naming format: `<number>_<page_name>.svg`
+
+- **Chinese content** → Chinese naming: `01_封面.svg`, `02_目录.svg`, `03_核心优势.svg`
+- **English content** → English naming: `01_cover.svg`, `02_agenda.svg`, `03_key_benefits.svg`
+- **Number rules**: Two-digit numbers, starting from 01
+- **Page name**: Concise and descriptive, matching the page title in the Design Specification & Content Outline
+
+---
+
+## 4. Icon Usage
+
+Four approaches: **A: Emoji** (`<text>🚀</text>`) | **B: AI-generated** (SVG basic shapes) | **C: Built-in library** (`templates/icons/` 640+ icons, recommended) | **D: Custom** (user-specified)
+
+**Built-in icons — Placeholder method (recommended)**:
+
+```xml
+<use data-icon="chart-bar" x="100" y="200" width="48" height="48" fill="#005587"/>
+```
+
+> No need to manually run `embed_icons.py`; `finalize_svg.py` post-processing tool will auto-embed icons.
+
+**Common icons**: `chart-bar` `arrow-trend-up` `users` `cog` `circle-checkmark` `target` `clock` `file` `dollar` `lightbulb`
+
+> ⚠️ **Icon validation rule**: If the Design Specification includes an icon inventory list, Executor may **only** use icons from that approved list. Using icon names not in the index is FORBIDDEN — verify against `templates/icons/icons_index.json` if uncertain.
+
+Full index: `templates/icons/README.md`
+
+---
+
+## 5. Chart Reference
+
+When the Design Spec includes a **VII. Chart Reference List**, read the referenced SVG templates from `templates/charts/` to understand common chart patterns.
+
+**Adaptation rules**:
+- **Must preserve**: Chart type (bar/line/pie etc.) as specified in the Design Spec
+- **Must adapt**: Data values, labels, colors (match the project's color scheme), and dimensions to fit the page layout
+- **May adjust**: Axis ranges, grid lines, legend position, spacing — as long as the chart remains accurate and readable
+- **Must NOT**: Change chart type without Design Spec justification, or remove data points specified in the outline
+
+> Chart templates: `templates/charts/` (33 types). Index: `templates/charts/charts_index.json`
+
+---
+
+## 6. Image Handling
+
+Handle images based on their status in the Design Specification's "Image Resource List":
+
+| Status | Source | Handling |
+|--------|--------|----------|
+| **Existing** | User-provided | Reference images directly from `../images/` directory |
+| **AI-generated** | Generated by Image_Generator | Images already in `../images/`, reference directly |
+| **Placeholder** | Not yet prepared | Use dashed border placeholder |
+
+**Reference**: `<image href="../images/xxx.png" ... preserveAspectRatio="xMidYMid slice"/>`
+
+**Placeholder**: Dashed border `<rect stroke-dasharray="8,4" .../>` + description text
+
+---
+
+## 7. Font Usage
+
+Apply corresponding fonts for different text roles based on the font plan in the Design Specification & Content Outline:
+
+| Role | Chinese Recommended | English Recommended |
+|------|--------------------|--------------------|
+| Title font | Microsoft YaHei / KaiTi / SimHei | Arial / Georgia |
+| Body font | Microsoft YaHei / SimSun | Calibri / Times |
+| Emphasis font | SimHei | Arial Black / Consolas |
+| Annotation font | Microsoft YaHei / SimSun | Arial / Times |
+
+---
+
+## 8. Speaker Notes Generation Framework
+
+### Task 1. Generate Complete Speaker Notes Document
+
+After **all SVG pages are generated and finalized**, enter the "Logic Construction Phase" and generate the complete speaker notes document in `notes/total.md`.
+
+**Why not generate page-by-page?** Batch-writing notes allows planning transitions like a script, ensuring coherent presentation logic.
+
+**Format**: Each page starts with `# <number>_<page_title>`, separated by `---` between pages. Each page includes: script text (2-5 sentences), `Key points: ① ② ③`, `Duration: X minutes`. Except for the first page, each page's text starts with a `[Transition]` phrase.
+
+**Basic stage direction markers** (common to all styles):
+
+| Marker | Purpose |
+|--------|---------|
+| `[Pause]` | Whitespace after key content, letting the audience absorb |
+| `[Transition]` | Standalone paragraph at the start of each page's text, bridging from the previous page |
+
+> Each style may extend with additional markers (`[Interactive]`/`[Data]`/`[Scan Room]`/`[Benchmark]` etc.), see `executor-{style}.md`.
+
+**Language consistency rule**: All structural labels and stage direction markers in speaker notes **MUST match the presentation's content language**. When the presentation content is non-English, localize every label — do NOT mix English labels with non-English content.
+
+| English | 中文 | 日本語 | 한국어 |
+|---------|------|--------|--------|
+| `[Transition]` | `[过渡]` | `[つなぎ]` | `[전환]` |
+| `[Pause]` | `[停顿]` | `[間]` | `[멈춤]` |
+| `[Interactive]` | `[互动]` | `[問いかけ]` | `[상호작용]` |
+| `[Data]` | `[数据]` | `[データ]` | `[데이터]` |
+| `[Scan Room]` | `[观察]` | `[観察]` | `[관찰]` |
+| `[Benchmark]` | `[对标]` | `[ベンチマーク]` | `[벤치마크]` |
+| `Key points:` | `要点：` | `要点：` | `핵심 포인트:` |
+| `Duration:` | `时长：` | `所要時間：` | `소요 시간:` |
+| `Flex:` | `弹性：` | `調整：` | `조정:` |
+
+> For languages not listed above, translate each label to the corresponding natural term in that language.
+
+**Requirements**:
+
+- Notes should be conversational and flow naturally
+- Highlight each page's core information and presentation key points
+- Users can manually edit and override in the `notes/` directory
+
+### Task 2. Split Into Per-Page Note Files
+
+Automatically split `notes/total.md` into individual speaker note files in the `notes/` directory.
+
+**File naming convention**:
+
+- **Recommended**: Match SVG names (e.g., `01_cover.svg` → `notes/01_cover.md`)
+- **Compatible**: Also supports `slide01.md` format (backward compatibility)
+
+---
+
+## 9. Next Steps After Completion
+
+> **Auto-continuation**: After Visual Construction Phase (all SVG pages) and Logic Construction Phase (all notes) are complete, the Executor proceeds directly to the post-processing pipeline.
+
+**Post-processing & Export** (see [shared-standards.md](shared-standards.md)):
+
+```bash
+# 1. Split speaker notes
+python3 scripts/total_md_split.py <project_path>
+
+# 2. SVG post-processing (auto-embed icons, images, etc.)
+python3 scripts/finalize_svg.py <project_path>
+
+# 3. Export PPTX
+python3 scripts/svg_to_pptx.py <project_path> -s final
+# Default: generates native shapes (.pptx) + SVG reference (_svg.pptx)
+```

package/skills/ppt-master/references/executor-consultant-top.md

@@ -0,0 +1,218 @@
+# Executor Consultant Top — Top-tier Consulting Style (MBB Level)
+
+> Common guidelines: executor-base.md. Technical constraints: shared-standards.md.
+
+---
+
+## Role Definition
+
+An MBB-level (McKinsey / Bain / BCG) top-tier consulting style SVG design executor. Suitable for strategic planning, board presentations, investment roadshows, C-suite decision support, and other **premium consulting** scenarios. Core characteristics: data-driven insights, pyramid-structured narrative, extreme simplicity. Output targets C-level decision-makers.
+
+---
+
+## SCQA Framework (Narrative Structure)
+
+Every MBB-level presentation follows the SCQA narrative structure:
+
+| Element | Purpose | Typical Pages |
+|---------|---------|---------------|
+| **S - Situation** | Establish shared context | Cover / Pages 1-2 |
+| **C - Complication** | Introduce the problem / tension | Pages 2-3 |
+| **Q - Question** | The implicit or explicit question to solve | Transition page |
+| **A - Answer** | Core solution | All body pages |
+
+**Page sequencing**: Cover embodies S+C → Executive Summary answers Q → Chapters develop A → Closing revisits S
+
+**Title writing**:
+
+| SCQA Element | Weak Title | MBB-level Title |
+|-------------|------------|-----------------|
+| S | "Industry Background" | "Digital penetration surpasses 60%, industry enters deep waters" |
+| C | "Challenges Faced" | "Yet three structural contradictions constrain scaled deployment" |
+| Q | "Strategic Question" | "How to move from pilot to full deployment within 18 months?" |
+| A | "Solution" | "Three-phase path: Focus, Expand, Scale" |
+
+---
+
+## Data Contextualization (Never Present Data in Isolation)
+
+> **Golden Rule**: Never display a single data point in isolation. Every number needs context.
+
+| Method | Pattern | Visual Implementation |
+|--------|---------|----------------------|
+| **Time comparison** | "From X to Y" | Line chart + arrow annotating magnitude of change |
+| **Benchmark** | "X vs industry average Y" | Bar chart with gray dashed baseline |
+| **Competitive comparison** | "Us X vs Competitor Y" | Side-by-side bar chart, highlight own data |
+| **Target gap** | "Actual X / Target Y" | Progress bar + gap annotation |
+| **Ranking** | "Ranked #N of M" | Horizontal bar chart + highlight marker |
+
+**Data annotation three essentials**: Every data visualization must include (1) The value itself (large bold font) (2) Comparison reference (baseline / prior period / competitor) (3) Meaning interpretation ("So what?")
+
+```xml
+<text x="160" y="280" text-anchor="middle" font-size="42" font-weight="bold" fill="#1E293B">97.3%</text>
+<text x="160" y="310" text-anchor="middle" font-size="13" fill="#64748B">Industry avg 82% | Competitor A 89%</text>
+<text x="160" y="335" text-anchor="middle" font-size="12" fill="#059669">Leading industry by 15.3 percentage points</text>
+```
+
+---
+
+## Pyramid Principle (Conclusion First)
+
+> Executives don't care about your *process* — they care about *results*.
+
+```
+         ┌─────────────────┐
+         │  Core Conclusion │   ← Page title / Takeaway
+         └────────┬────────┘
+      ┌───────────┼───────────┐
+  ┌───┴───┐  ┌───┴───┐  ┌───┴───┐
+  │ Arg 1 │  │ Arg 2 │  │ Arg 3 │   ← Key supporting points
+  └───────┘  └───────┘  └───────┘
+```
+
+| Level | Position | Font Size |
+|-------|----------|-----------|
+| Core conclusion | Takeaway Box | 16-18px bold |
+| Arguments | Content area body | 14-16px |
+| Supporting data | Charts / cards | 12-14px |
+
+**Contrast**: Title "Market Research Results" (wrong) → "Metaverse needs 5-10 years to reach scale" (right); Body "We researched... and found..." (wrong) → "Three arguments: (1)... (2)... (3)..." (right)
+
+---
+
+## MBB-level Layout Patterns
+
+### Content Page Standard Structure (1280x720)
+
+```
+┌──────────────────────────────────┐
+│ Gradient top bar (0,0 → 1280,6)  │
+├──────────────────────────────────┤
+│ Assertion title (x=40, y=50, 24px)│
+├──────────────────────────────────┤
+│ Takeaway Box (x=40, y=75,        │  ← Dark background + white text, one-sentence conclusion
+│   w=1200, h=45)                  │
+├──────────────────────────────────┤
+│ Content area (x=40, y=140,       │  ← Charts / data / analysis
+│   w=1200, h=520)                 │
+├──────────────────────────────────┤
+│ Source | CONFIDENTIAL | Page #    │  ← y=700, 10px
+└──────────────────────────────────┘
+```
+
+### Strategic Roadmap
+
+Three phases laid out horizontally, `<rect rx="8">` + title + action list, `<polygon>` arrows connecting:
+
+```
+Focus Core (0-6mo)  ──>  Expand Capability (6-12mo)  ──>  Scale Up (12-18mo)
+x=40,w=380              x=450,w=380                     x=860,w=380
+```
+
+### Benchmarking Matrix
+
+Horizontal table; own row highlighted in theme color, others in gray. Leading indicators marked green, lagging marked red. Use `<circle>` or `<rect>` to build score points.
+
+### Waterfall Chart (Change Attribution)
+
+Start → increase/decrease factors → End. Positive factors green bars, negative factors red bars, start/end points dark bars, cumulative line as dashed connector.
+
+---
+
+## Strategic Use of Color
+
+MBB-level color usage is extremely restrained — color serves information:
+
+| Purpose | Method |
+|---------|--------|
+| **Focus** | Target data in theme color, everything else gray |
+| **Reduce cognitive load** | Same series differentiated by opacity (`fill-opacity` 1.0/0.6/0.3) |
+| **Semantics** | Green = positive, Red = negative, Gray = baseline |
+| **Branding** | Gradient top bar / decorative lines in brand color |
+
+**Commandments**: No more than 3 primary colors; accent color used at most 2-3 places globally; data series use same-hue depth variations, not different colors; background white or very light gray.
+
+---
+
+## Chart vs Table Selection Matrix
+
+| Scenario | Recommended Form | Reason |
+|----------|-----------------|--------|
+| Comparing 2-7 categories | **Bar chart** | Visual comparison is intuitive |
+| Time trends | **Line chart** | Time series clarity |
+| Precise values / large rankings | **Table** | 50 data points in a bar chart would be chaotic |
+| Proportional composition | **Donut chart** | More modern than pie charts |
+| Two-dimensional positioning | **2x2 matrix** | Strategic quadrant analysis |
+| Change attribution | **Waterfall chart** | Factor decomposition |
+
+---
+
+## Speaker Notes Style
+
+### Narrative Tone
+
+Targeting **executives / decision-makers**. Pyramid structure — every sentence carries information. Composed, authoritative, and insightful tone.
+
+### Stage Direction Markers
+
+| Marker | Purpose | Example |
+|--------|---------|---------|
+| `[Pause]` | Silence after key insight, let executives absorb | "This means we are missing a billion-dollar market. [Pause]" |
+| `[Scan Room]` | Observe decision-makers' reactions, decide whether to elaborate | "[Scan Room] If there are questions, I can elaborate." |
+| `[Data]` | Conversational number delivery | "[Data] 63% → nearly two-thirds" |
+| `[Benchmark]` | Emphasize comparison baseline | "[Benchmark] Compared to the industry average of 12%, our 23% is nearly double" |
+| `[Transition]` | Bridge from previous page, at start of each page's text | "[Transition] Building on the strategic framework, let's drill into the implementation path." |
+
+### Notes Writing Guidelines
+
+- **Pyramid structure**: Conclusion → Arguments → Details
+- **Data contextualization**: Every number has a comparison reference
+- **Executive language**: "The strategic implication is...", "The core insight is..."
+- **Flex mechanism**: Annotate "content that can be skipped if time is tight" for flexible duration
+- **Key points structure**: `Key points: (1) Core insight (2) Data support (3) Strategic implication`
+
+### Notes Example
+
+```markdown
+# 03_strategic_path
+
+[Transition] Having clarified the problem and the opportunity, now comes the most critical part — our response path.
+
+We recommend a three-phase strategy. [Pause]
+
+Phase one: Focus. Over the next six months, concentrate resources on conquering the Eastern China market.
+[Data] Eastern China contributes nearly two-thirds of industry growth, [Benchmark] yet our penetration rate is only half of Competitor A's. [Pause]
+
+Phase two: Expand. Use Eastern China as a template, replicate to Southern and Northern China.
+Phase three: Scale. Leverage a digital platform for nationwide coverage.
+
+[Scan Room] The resource allocation for phase one is in the appendix — would you like me to walk through it now?
+
+Key points: (1) Focus-Expand-Scale three-phase approach (2) Data-backed Eastern China priority (3) 18-month full deployment
+Duration: 3 minutes
+Flex: [If time is tight, skip phase two and three details and go straight to financial impact]
+```
+
+---
+
+## MBB-level Quality Checklist Supplement
+
+### Content Level
+
+- [ ] **SCQA complete**: Overall follows Situation-Complication-Question-Answer structure
+- [ ] **Data contextualized**: Every data point has a comparison reference
+- [ ] **Conclusion first**: Every page's Takeaway Box has a one-sentence conclusion
+- [ ] **MECE principle**: Categorized analysis is mutually exclusive and collectively exhaustive
+
+### Visual Level
+
+- [ ] **Color with intent**: Colors serve information delivery
+- [ ] **Ample whitespace**: Not crowded; information can "breathe"
+- [ ] **Visual hierarchy**: Conclusion > Arguments > Details, differentiated by font size/weight
+- [ ] **Brand consistency**: Gradient top bar and footer unified throughout
+
+### Notes Level
+
+- [ ] **Pyramid structure**: Every page is conclusion-first
+- [ ] **Stage markers complete**: [Pause] and [Scan Room] at key positions
+- [ ] **Flex content annotated**: Supports flexible duration

package/skills/ppt-master/references/executor-consultant.md

@@ -0,0 +1,197 @@
+# Executor Consultant — Consulting Style
+
+> Common guidelines: executor-base.md. Technical constraints: shared-standards.md.
+
+---
+
+## Role Definition
+
+A data-driven, consulting-style SVG design executor. Suitable for business analysis reports, market research, operational reviews, strategic recommendations, and other **general consulting** scenarios. Emphasizes structured information presentation and data visualization; clean, clear, and professional style.
+
+---
+
+## Consultant-specific Data Visualization Techniques
+
+### 1. KPI Dashboard Design
+
+KPI cards are the most common element in consulting reports. Standard layout (1280x720):
+
+```
+4-card layout: each card 280x180, gap 30
+  Card 1: x=45,  y=160
+  Card 2: x=355, y=160
+  Card 3: x=665, y=160
+  Card 4: x=975, y=160
+```
+
+**Card internal structure** (top to bottom):
+
+| Area | Content | Font Size | Style |
+|------|---------|-----------|-------|
+| Icon row | data-icon icon | 32x32 | Theme color |
+| Metric name | "Monthly Active Users" | 14px | Gray #64748B |
+| Core number | "1.2M" | 36-42px | Bold, dark color |
+| Trend annotation | "+12.3% vs last month" | 12px | Green=up / Red=down |
+
+**Trend arrow conventions**:
+- Up: `arrow-trend-up` icon + green text
+- Down: `arrow-trend-down` icon + red text
+- Flat: horizontal line icon + gray text
+
+### 2. Chart Color Conventions
+
+Consulting-style charts use **monochromatic depth gradients** rather than rainbow colors:
+
+```
+Primary series:   Theme color 100% opacity
+Comparison series: Theme color 60% opacity
+Baseline:         #94A3B8 (gray dashed line)
+Highlight:        Accent color (only for key data points)
+```
+
+### 3. Data Annotation Principles
+
+- **Direct data labels**: Place values at the top of bar charts — no legend needed
+- **Annotated trend lines**: Add text notes at key inflection points ("Policy change", "Product launch")
+- **Comparison baselines**: Mark industry average / target values with gray dashed lines
+- **Consistent units**: Maintain the same numeric units and precision within a chart
+
+### 4. Table Design
+
+Consulting reports frequently use tables for precise data:
+
+| Design Element | Specification |
+|----------------|---------------|
+| Header | Dark background + white text, font-weight="bold" |
+| Zebra striping | Alternate rows with `fill-opacity="0.05"` light background |
+| Number alignment | Numbers right-aligned, text left-aligned |
+| Highlighted row | Mark key rows with accent color `fill-opacity="0.1"` |
+| Borders | Use horizontal lines only to separate rows; avoid full grid lines |
+
+---
+
+## Consulting-specific Layout Patterns
+
+### MECE Decomposition Tree
+
+Main trunk on the left, branches expanding rightward — mutually exclusive, collectively exhaustive:
+
+```
+Main metric ──┬── Branch A (45%)
+              ├── Branch B (30%)
+              ├── Branch C (20%)
+              └── Branch D (5%)
+```
+
+- Use `<line>` to connect trunk to branches
+- Each branch has a `<rect>` container + percentage annotation
+- Sum must = 100% (or explicitly label "Other")
+
+### Driver Factor Tree
+
+Top-level metric → decomposed factors → actions. Ideal for performance attribution analysis:
+
+```
+Revenue growth 15%
+  ├── Average order value +8%  → Premium product line expansion
+  ├── Customer count +5%       → New channel acquisition
+  └── Repurchase rate +2%      → Loyalty program optimization
+```
+
+### Left-chart Right-text (Chart Interpretation)
+
+Core consulting report layout: chart on the left, key insights on the right:
+
+```
+Chart area: x=40, y=120, w=700, h=480
+Insight area: x=780, y=120, w=460, h=480
+  - Core conclusion (bold, 16px)
+  - 3-5 bullet points (14px)
+  - Data source (12px, gray)
+```
+
+---
+
+## Professional Expression Standards
+
+### Page Titles
+
+Consulting-style page titles should be **assertion headlines**, not descriptive titles:
+
+| Type | Descriptive (avoid) | Assertion (recommended) |
+|------|---------------------|------------------------|
+| Market | "Market Overview" | "Domestic market grows 23% YoY, significantly outpacing global average" |
+| Competition | "Competitive Analysis" | "Three major competitors show clear weaknesses in channel coverage" |
+| Finance | "Financial Data" | "Gross margin improved for four consecutive quarters, breaking industry ceiling" |
+
+### Data Source Attribution
+
+Every data-containing page must include a source note at the bottom:
+
+```xml
+<text x="40" y="700" font-size="10" fill="#94A3B8">
+  Source: National Bureau of Statistics 2025 Annual Report; Internal team analysis
+</text>
+```
+
+### Key Takeaway Box
+
+Consulting-style content pages should include a **Takeaway Box** below the title:
+
+```
+Position: x=40, y=80, w=1200, h=50
+Background: Light theme color (fill-opacity="0.08")
+Text: 14-16px, one-sentence summary of the page's core takeaway
+```
+
+---
+
+## Speaker Notes Style
+
+### Narrative Tone
+
+Consultant-style speaker notes use a **conclusion-driven** approach — state the conclusion first, then present supporting evidence. Professional, concise, and persuasive tone.
+
+### Stage Direction Markers
+
+| Marker | Purpose | Example |
+|--------|---------|---------|
+| `[Pause]` | Silence after key conclusions, let the audience absorb | "This means our market share is being eroded. [Pause]" |
+| `[Data]` | Cue to verbalize numbers conversationally | "[Data] 85% → more than eight out of ten customers reported this issue" |
+| `[Transition]` | Bridge from previous page, must be at start of each page's text | "[Transition] Based on that analysis, let's look at specific recommendations." |
+
+### Notes Writing Guidelines
+
+- **Conclusion first**: The first sentence of each page's notes is the core takeaway
+- **Conversational data**: 30% → "roughly one-third", 85% → "more than eight out of ten", 2.5x → "two and a half times"
+- **Evidence follows immediately**: After the conclusion, provide 2-3 supporting data points/facts
+- **Professional terminology**: Use terms like "insight", "driver", "key lever" etc.
+- **Key points structure**: `Key points: (1) Core conclusion (2) Supporting data (3) Next steps`
+
+### Notes Example
+
+```markdown
+# 03_key_findings
+
+[Transition] Based on our market scan, we have distilled three key findings.
+
+First, the primary growth driver is shifting from acquisition to retention.
+[Data] New customer acquisition cost rose nearly 40% year-over-year, yet improved repurchase rates contributed over 60% of revenue growth. [Pause]
+
+Second, lower-tier market growth significantly outpaces tier-1 and tier-2 cities.
+Third, the 25-35 female user segment has an ARPU 1.8x the overall average.
+
+Key points: (1) Growth engine shifting from acquisition to retention (2) Lower-tier market opportunity window (3) High-value user persona
+Duration: 2 minutes
+```
+
+---
+
+## Self-check Supplement (Consultant-specific)
+
+- [ ] Data matches source data — no fabrication
+- [ ] Every data page has a source attribution at the bottom
+- [ ] Page titles are assertion-based, not descriptive
+- [ ] KPI cards have trend arrows and comparison annotations
+- [ ] Chart colors are unified, using monochromatic scheme rather than rainbow
+- [ ] Notes are conclusion-first with conversational data