Scaffold a new catalog

Stamp out the minimum a new catalog needs. The templates are in references/templates.md; read it before generating files. The templates are a self-contained subset; the authoritative notebook/data conventions are the compose-notebook skill's references/conventions.md - consult it (and prefer it on any conflict) when generating the orientation notebook. The metric that matters is time-to-second-instance: how fast a domain expert ships a catalog for a new dataset.

Why so little

A catalog is uv + PEP 723 + notebooks, nothing more. Resist adding a package, a pipeline, or an environment manager now - those are weight you cannot remove later and almost never need. Start minimal and let the catalog earn complexity only when a stable subset of the work demands it.

Arguments

• catalog-name (required): short lowercase name (e.g. cellpaint-x). Ask if missing.
• data-surface (optional): how the catalog reaches its data - rest, duckdb, pooch, or files (small data committed to the repo). Ask if not given.
• Ask where to create it (absolute path to the parent directory).