/coral-geyser

name: coral-geyser-pptx
description: "Reusable fixed-style PPTX generation skill for the Coral Geyser Notice visual brand — coral-red background (#E95140), warm stone typography (#E7D8D1), bold modern visitor-notice and design-forward travel guide aesthetic, heavy geometric sans titles, strong split-screen compositions, widescreen 16:9 editable .pptx output. Use this skill whenever the user mentions Coral Geyser Notice, asks for a presentation or deck in the Coral Geyser style, wants a visitor notice deck, travel guide deck, field guide presentation, park-hours-poster-style PowerPoint, route card deck, or mentions coral-red with warm stone typography for slides. Also trigger when the user says 'coral geyser', 'notice deck', 'visitor guide deck', 'field guide slides', 'travel notice presentation', 'park guide deck', or 'route card presentation' in any context."

Coral Geyser Notice PPTX Skill

A reusable fixed-style PowerPoint generation skill. It builds on the `pptx` skill's technical capabilities while locking in the Coral Geyser Notice visual identity: bold, modern, design-forward, inspired by park-hours posters and visitor field guides.

**Core principle — style wins over content volume.** When the user's topic contains more information than the format can hold, compress and reinterpret. The deck must feel like a bold modern visitor notice and design-forward visual guide — not a generic tourism brochure, not a text-heavy itinerary, not a business report. Every slide is a notice plate or field guide panel.

---

Step 1: Gather Inputs (Ask First — Max 3 Questions)

Do **not** start generating immediately. Use the `AskUserQuestion` tool to present interactive questions in a **single** call. Only ask what the user hasn't already provided.

**Question 1 — Topic** (skip if already provided):

• header: "Topic"
• question: "What is the presentation topic, destination, notice subject, guide title, event, project, or brand/product name?"
• options: 2–3 relevant examples plus allow Other

**Question 2 — Slide count** (skip if already specified):

• header: "Slides"
• question: "How many slides should the deck include?"
• options: `6 slides`, `9 slides (Recommended)`, `12 slides`, `15 slides`

**Question 3 — Images**:

• header: "Images"
• question: "How should images be handled?"
• options:
• `Generate with AI` — I'll create cool blue-white environmental images using gpt-image-2
• `Use my uploaded images` — Insert images I provide
• `Combine both` — Mix uploaded and AI-generated images

If the user hasn't provided dates, location, route, schedule, safety notes, or other details, **infer reasonable content or use neutral placeholder copy**. Do not keep asking — only follow up if missing info makes it literally impossible to build the deck.

Once you have the three answers, proceed directly to generation.

---

Step 2: Topic Translation — Everything Becomes a Notice or Field Guide

Before writing any slide copy, translate the user's topic into a Coral Geyser Notice frame. No topic is too technical, too abstract, or too far from travel/nature to work. Every subject can be reframed as a bold public notice, design-forward field guide, route card, visitor briefing, product usage guide, event notice, or operational poster sequence — while preserving the user's actual subject.

| User provides | Coral Geyser treatment | |---|---| | National park / nature destination | Visitor field guide with safety, route, highlights | | Tech product | Bold product usage guide — steps, warnings, features as notice panels | | Corporate event | Event field guide — schedule grid, venue map, session notices | | Scientific concept | Environmental visual essay — concept as landscape | | Brand launch | Field guide to the brand — territory, rules, essential stops | | Any other subject | Reframe as a visitor briefing, route card, or operational notice |

Decide the **guide title**, the **one-line field notice**, and the **location/context label** before writing any slides. These anchor the cover and the visual language of the whole deck.

---

Step 3: Generate Images (if requested)

Read the `generate-image` skill at `/home/node/.claude/skills/generate-image/SKILL.md` for the exact API call pattern. Use `openai/gpt-image-2` with `response_format: "b64_json"`.

How many images to generate

• 9-slide deck → 4–5 images
• 12–15 slide deck → 5–6 images
• Fewer than 7 slides → 3–4 images

Coral Geyser image prompt formula

Generated images must be cool blue-white, high-contrast, editorial, and atmospheric. They are supporting visual assets — not slide screenshots and never images with embedded text.

Base formula:

Cool blue-white landscape photograph, high contrast, slightly cold tone, crisp editorial outdoor imagery. [Scene descriptor: mist over water / mineral terraces / snow-dusted path / misty forest / steam vents / boardwalk trail / wide river valley / frost-covered rock face]. No readable text, no logos, no recognizable people. Mostly blue-white with minimal warm color. 16:9 landscape composition.

For non-nature topics, reinterpret through abstract environmental forms:

Cool blue-white abstract environmental texture, high contrast, slightly cold. [Mood word: architectural geometry / industrial surface / crystalline detail / aerial landscape / misty atmosphere]. No text, no logos, no people. 16:9.

Save each image to `/tmp/coral-geyser-img-N.png`.

---

Step 4: Build the PPTX

Read the `pptx` skill at `/home/node/.claude/skills/pptx/SKILL.md` and its `pptxgenjs.md` reference for the full API. Build using PptxGenJS.

Core style constants — do not deviate

const CORAL  = "E95140";       // dominant background — all coral fields
const STONE  = "E7D8D1";       // primary type, rules, dividers, panels
const WHITE  = "FFFFFF";       // high-contrast accents, numbers
const DARK   = "1A1A1A";       // dark text on stone/white panels if needed
const SANS   = "Arial Black