Create MotherDuck Dives

Use this skill when the user needs a persistent, shareable Dive rather than a one-off chart or a full customer-facing analytics application.

Source Of Truth

Prefer current MotherDuck Dive docs first.
If MotherDuck MCP is available, call get_dive_guide before generating, saving, or updating a Dive.
Keep theming, local-preview, code-management, and embedding guidance aligned with the current Dive docs.

Validate the underlying SQL and schema first with explore and query.
Keep Dive queries fully qualified and SQL-heavy; let React handle presentation, not data reshaping.
When a Dive uses shared databases in REQUIRED_DATABASES, always suffix the alias (e.g. _share) so it cannot collide with an existing database name. Never set alias to conflict with an existing database name.
Start from a named theme direction such as Corporate Dashboard, Tufte Minimal, or FT Salmon instead of vague visual prompts.
Prefer one query per visual section rather than one giant cross-purpose query.
Preview locally before saving when the environment supports it.
Treat embedded Dives as a lightweight read-only surface; for per-customer serving and policy control, move to build-cfa-app.