Pre-Set Catalog with Generate-On-The-Fly Fallback

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Select a slide theme for a monochrome technical report with a preset catalog and readability requirements. Teaching A uses colored legends; B is black/gray/white but has poor title contrast. Preset status does not make either suitable.

Mechanism

Inspect specifications/previews against one shared requirement set. Reuse a fitting preset; otherwise create a constrained small custom candidate with preview/checks. Reuse a valid explicit selection rather than asking mechanically again. Generation does not automatically admit a theme into an approved catalog.

Bad example

Force colorful A onto the monochrome report or assume B's preset status proves acceptable contrast.

Good example

Inspect A/B against monochrome/readability. A's colors and B's poor contrast require a corrected/new minimal candidate. Preview title/body/legend and inspect them. Distinguish new candidates from catalog items. Apply valid existing selections and review new choices under the task contract; preset/generation identity cannot replace verification.

Why the change matters

Presets reduce repeated design but suitability depends on brief/artifact. An explicit fallback supports preparation without equating closest with suitable or new with approved.

Observable expectation

State why A/B fail, then check a candidate’s black/gray/white palette and readable text/legends under the same rules as a reused theme.

Names alone, brief violations or unreviewed candidates presented as approved fail. No real slides are generated.

Limits

A small adjustment may suffice instead of rebuilding. Monochrome does not replace content/accessibility/print checks. Source choice steps do not require reopening a valid choice already supplied.