docs: require hero imagery for svg slide roles

skills/lark-slides/references/svg-slides/authoring-rules.md

@@ -45,7 +45,11 @@ Use images when there is a real image asset or generated visual. The SVG file re
 
 Informational images such as charts, diagrams, screenshots, and infographics must preserve their original ratio. Decorative images may be composed more freely, but should still fit the resolved design brief.
 
-Generated cover or closing images must not contain baked-in text. Render text as slide text on top of the image.
+Unless the user explicitly requests no images, cover, section divider, and closing pages should use a large hero image or generated visual. Full-bleed image backgrounds use `<image slide:role="background">`; large non-background images use `<image slide:role="image" slide:shape-type="image">`.
+
+When text sits on an image, place a semi-transparent `<rect slide:role="shape" slide:shape-type="shape">` scrim or a solid text zone after the image and before the text. Do not use SVG `<mask>` for this readability layer.
+
+Generated cover, section divider, or closing images must not contain baked-in text. Render text as slide text on top of the image.
 
 ## Chart Embeds
 

skills/lark-slides/references/svg-slides/design-brief.md

@@ -56,9 +56,12 @@ Presented decks can use shorter on-slide wording because the speaker carries con
 - typography category and treatment;
 - layout grammar;
 - imagery or material direction;
+- page-role imagery defaults for cover, section divider, and closing pages;
 - decoration and motif rules;
 - constraints to avoid.
 
+Unless the user explicitly requests no images, `visual_system` must specify how cover, section divider, and closing pages use a high-impact hero image or generated visual. The brief should describe the imagery subject, treatment, crop attitude, and how foreground text stays readable.
+
 Font mapping must preserve the same category and treatment. Do not swap serif and sans, ignore uppercase treatment, or pick generic fonts when the brief calls for a distinctive style.
 
 ## How It Drives Generation

skills/lark-slides/references/svg-slides/visual-design.md

@@ -33,6 +33,8 @@ Every substantive slide should have a visual idea: image, chart, diagram, proces
 
 Avoid repeating title-plus-bullets. Reuse deck-level motif and style, not the exact same page layout.
 
+Cover, section divider, and closing pages are not exceptions. Unless the user explicitly requests no images, make these pages image-led with a high-impact hero image or generated visual. Text over imagery must use an intentional readability treatment, such as a translucent scrim or solid text zone, instead of relying on contrast by accident.
+
 ## Density
 
 Density comes from audience and delivery mode. Split rather than cram when a slide needs more than one central idea.

skills/lark-slides/references/svg-slides/workflow.md

@@ -62,6 +62,8 @@ Translate `visual_system` into concrete deck-level style:
 - `typography`: a stable display/body pairing that matches the brief's category and treatment.
 - `visual_assets`: per-slide image and chart needs, including aspect ratio and placement intent.
 
+Unless the user explicitly requests no images, cover, section divider, and closing pages default to a high-impact hero image or generated visual. Record the intended asset, crop/aspect ratio, placement, and text-readability overlay treatment in `visual_assets`; do not leave these page roles as text-only by default.
+
 Plan charts before writing slides. Any real quantitative series that supports a slide's point should use the chart workflow rather than a hand-drawn fake chart.
 
 ## Phase 8: Author SVG Pages