Tidal Service Playbook Deck

---
name: bs-tidal-service-playbook-deck
description: Create a service training deck with ice-blue and navy pages, organic contours, and clear operational steps. Turn standards and handovers into an editable presentation that new teammates can follow.
---

# Tidal Service Playbook Deck

Use this Skill for service training, operating standards, onboarding playbooks, and partner or team updates that should look calm and premium: pale ice-blue and navy pages, soft organic contours, large open headlines, edge-bleed photographs, equal-height cards, service tables, and connected journey steps.

## Shared editor contract

This style always uses the bundled framework in `references/framework/`; never build a separate editor or paging engine. The editor UI is identical across styles: black, white and gray, with localized icon tooltips and independently editable objects. Palettes, fonts, artwork and layouts stay specific to this Skill and come from its style kit. Read [runtime](references/runtime.md) for the editor, saving and export behaviour, and [compose guide](references/compose.md) for the plan format.

## Workflow

1. Confirm the user's topic, audience, source facts, communication language, content language and slide count. Write slide copy in English unless the user asks for another language. Keep this style's art direction, layout proportions and content limits below; do not substitute a generic template.
2. Plan a clear narrative with one job per page, using the agreed number of fixed 16:9 pages and this style's word budgets and evidence rules.
3. Read this package's style references (below). Named palettes are choices for slide content; the shared editor stays unchanged.
4. Compose from the style kit so the deck matches the store example: write `plan.json` picking a recipe from `references/style-kit.json` for each page (recipes may repeat), set the new text, pictures, picture descriptions (`alt`), icons, chart labels and data values by node ID, remove nodes a page does not need, then run `python3 scripts/style-kit.py compose --style-kit references/style-kit.json --plan plan.json --output project.json`. Work through the report: fill every `unfilledImages` slot and replace each `leftoverExample` entry that belongs to the example's topic. The [compose guide](references/compose.md) documents every plan field. Refine `project.json` where needed (add, delete, move or restyle nodes, keeping IDs unique), keep the kit's `contentCSS`, and write `editor-config.json` with the bundled schema.
5. Pictures:
   - Before making any picture, ask the user once (with the step 1 questions when possible) and offer exactly three options. Pictures the user supplies come first in every option. If the user cannot be asked or does not answer, use option 1. Tell the user which option you used.
     1. **Reuse this style's original pictures (recommended)**: use only pictures from this Skill's picture library, with no image credits. A slot with no fitting picture keeps its labeled image frame; list those slots for the user.
     2. **Generate as needed**: reuse library pictures where they fit and generate only the remaining slots.
     3. **Regenerate everything**: generate every picture new for this topic.
   - Library: run `node scripts/embed-library-images.mjs --list`; use `any-topic` pictures freely and `topic-specific` ones only when their topic matches the deck, never show one picture on two pages, and set the plan's `images` value (or an image node `src`) to `library:<id>`. After composing, run `node scripts/embed-library-images.mjs project.json` to inline them; if a download fails, treat those slots as unfilled.
   - Generate pictures following `references/image-prompts.md`, at the `aspect` that `style-kit.json` and the compose report list for each slot. Use FAL with the user's `FAL_KEY` through `node scripts/fal-image.mjs` (submit once, then status/fetch; each submission is a paid task that is never retried automatically). In ChatGPT or Codex, the built-in image generation (GPT Image) may be used instead and needs no key. Never use another image provider. Library pictures (`--download <id> --out <dir>`) or pictures already made for this deck can be passed as `--reference` to keep the series consistent.
   - With neither FAL nor a built-in tool, options 2 and 3 fall back to option 1.
6. Set `uiLocale` and `conversationLocale` to the user's communication language and `contentLocale`/`contentDirection` from the brief; compose detects Chinese, Japanese and Korean plans. Arabic and Hebrew right-to-left layout is handled by the framework; do not reverse logical arrays.
7. Build and check: `python3 scripts/build-deck.py --project project.json --config editor-config.json --output presentation.html`, then `python3 scripts/check-deck.py presentation.html --expected-slides N --style-kit references/style-kit.json --report deck-check.json`. Resolve every example string the check still reports. If it warns about size, run `python3 scripts/optimize-images.py presentation.html` and check again.
8. Open the file over local HTTP and inspect every page: typography, pictures, hierarchy, crops, bounds, contrast and spacing. Edit text, add/delete/move a block, change a color or Smart layout, edit notes, undo/redo, save and reopen. Presentation mode must disable editing and its glass navigation must hide after five idle seconds.
9. Deliver the single HTML file. It opens in a page view with an Edit button and works offline. Tell the user that edits stay in the browser until they press Save (Cmd/Ctrl+S), which writes them into the file. On request, export PPTX from the built-in menu, run `python3 scripts/check-pptx.py presentation.pptx --project project.json --report pptx-check.json` and inspect it in PowerPoint, Keynote or WPS. Keynote uses the compatible `.pptx`. Print/PDF gives one page per slide.

## Style references

Read the [style kit](references/style-kit.json), [compose guide](references/compose.md), [palettes](references/themes.md), [layout recipes](references/layouts.md), [image prompts](references/image-prompts.md), [icons](references/icon-library.md), [style reference](references/style-reference.md) and [runtime](references/runtime.md).

## Inputs and outputs

- Inputs: topic or approved outline, audience, approximate slide count, the action the deck should drive, verified figures and standards, and any pictures the user may use.
- Outputs: one self-contained presentation HTML (page view, editor, presentation mode, speaker notes, pictures inline); optionally an exported PPTX and a PDF via print.

## Restraint rules

- Word budget: headline ≤ 7 words (cover ≤ 5), one supporting line ≤ 18 words, at most 3 items of a ≤ 3-word label plus one line ≤ 10 words; ≤ 45 words per slide. Detail goes into the speaker notes.
- No tag clutter: only the small brand mark top-left on content slides; no pills, eyebrows (except one on the cover), folios or footer captions.
- 12-column grid on the 1280x720 page, 77px side margins, at most 3 content blocks per slide, roughly a third of each slide left calm.
- One corner radius for every photo and card; never overlap two photos; the workflow figure card is the only card over a photo.
- Embedded Manrope, headlines weight 500 with tight tracking; body text at least 17px.

## Constraints

- One coherent visual system from cover to closing; do not mix in unrelated styles.
- Never repeat a photo on two pages, and never use real organisations, people, or logos as sample content.
- Example numbers and organisation names are fictional; never imply real customer proof.
- Short labels, no paragraphs on slides, readable contrast, and running text no smaller than 17px.

## Style-specific planning and composition

- **Brief.** Confirm audience, slide count, source facts, and the closing action. Ask only for facts that change the result. Default copy to English. Keep approved figures; mark invented example data as illustrative.

- **Theme.** Apply one preset from `references/themes.md` (`--ink`, `--paper`, `--accent`). Keep the authored light preset unless asked. Type is the embedded Manrope (OFL) through `--font-display` / `--font-body`; do not swap in Arial or a font CDN.

- **Layouts.** Compose pages from the nine archetype recipes in `references/style-kit.json`, using `references/layouts.md` for their geometry, and follow its restraint rules. One focal point per page; keep the two dark archetypes as the only dark pages. Keep node IDs unique and text in independently editable leaves.

- **Icons.** Use inline Lucide SVG from `references/icon-library.md` only where it adds meaning, always next to a visible label. No emoji, dingbats, icon fonts, glyph arrows, or logos.

- **Pictures.** Follow Workflow step 5 (user pictures first, then the library question, then generation) and the slot briefs in `references/image-prompts.md`.

## Package boundary

Keep SKILL.md, scripts and references together. Include the shared runtime and required style resources. Examples, manifests, provider records, migration reports, previews and credentials do not belong in the installation ZIP. Use only references inside this Skill.