figura-cli 0.18.0 → 0.19.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "figura-cli",
-  "version": "0.18.0",
+  "version": "0.19.0",
   "description": "Command-line client for the Figura visualization SaaS",
   "license": "MIT",
   "type": "module",

package/skills/fig/SKILL.md

@@ -2,7 +2,7 @@
 name: fig
 description: "Mock up a screen as an on-brand, shareable HTML fig via your Figura team — render a UI state in seconds before writing the real code. Use when asked to visualize a screen, mock a UI, or 'make a fig'. iPhone-framed by default; browser frame for web/desktop."
 argument-hint: '<what to visualize>'
-allowed-tools: 'mcp__figura__figura_whoami, mcp__figura__figura_fig_scaffold, mcp__figura__figura_generate_fig, mcp__figura__figura_create_fig, mcp__figura__figura_revise_fig, mcp__figura__figura_publish_fig, mcp__figura__figura_commit_fig, Bash(figura *), Bash(bunx figura-cli *)'
+allowed-tools: 'mcp__figura__figura_whoami, mcp__figura__figura_fig_scaffold, mcp__figura__figura_fig_devices, mcp__figura__figura_generate_fig, mcp__figura__figura_create_fig, mcp__figura__figura_revise_fig, mcp__figura__figura_publish_fig, mcp__figura__figura_commit_fig, Bash(figura *), Bash(bunx figura-cli *)'
 ---
 
 # /fig — figure it out before you build it
@@ -316,26 +316,23 @@ with two things you do **not** hand-write:
   search and the self-improving loop. Artifact-descriptive only — no team/brand
   ids (the block is served on the public link).
 
-So when you **hand-build** a fig (the default path), do your part of the contract:
-
-- **Bare mobile screen — and ONLY then:** when the fig's HTML *is* one raw app
-  screen (no masthead, no state pills, no hand-drawn `.fig-device` frames — the
-  Figura viewer draws the iPhone shell around it), size the body to the exact
-  logical screen and emit `<meta name="figura:artboard" content="WxH">` matching
-  it (iPhone portrait `393x852` / landscape `852x393`). For OS-chrome insets
-  prefer `var(--fig-safe-top, 59px)` / `.fig-safe-top` over hardcoded pixels —
-  the stamp fills the value, the fallback keeps you correct if the kit is absent.
-- **A document-style fig NEVER gets an artboard.** The artboard meta is the
-  viewer's opt-in signal for "size me to exactly WxH and wrap me in a device
-  shell" — stamped on an overview ⇄ focus redesign page (or any compare /
-  variations document with its own masthead, pills, or hand-drawn device
-  frames), it crams the whole document into a phone frame. A document fig
-  renders full-page precisely because it carries NO artboard meta, even when
-  every screen it depicts is a mobile app.
-- **Always:** emit `<meta name="figura:context" content="...">` (design intent).
-- **Optional but valued:** if the fig grounds a specific feature or flag, emit
-  `<meta name="figura:feature" content="<flag-or-slug>">` so it links back to the
-  feature it depicts.
+So when you **hand-build** a fig (the default path), you do your part of the
+contract — but the exact rules are **fetched, not restated here**: the
+presentation model (frameless single vs canvas composition), when to emit or
+omit the whole-fig `<meta name="figura:artboard">`, the `.fig-device` /
+`data-device` frame markup (and NOT authoring its CSS — Figura stamps the bezel,
+Dynamic Island, and safe-area insets), the `figura:context` / `figura:feature`
+metas, and the valid devices all live in the canonical scaffold.
+
+- **`figura_fig_scaffold`** (CLI: `figura fig scaffold`) is authoritative for the
+  presentation model, the frame markup, and the output contract. Fetch it and
+  follow it verbatim (step 2 above) — do NOT restate design/format rules from
+  memory. A bundled skill can pin stale; the scaffold is always current.
+- **`figura_fig_devices`** (CLI: `figura fig devices`) is the full valid-
+  `data-device` catalog — every framed-device id + its geometry (logical dims,
+  safe-area insets, cutout, corner radius). Pick a real id from it for a canvas
+  composition's `<div class="fig-device" data-device="…">`; an unknown id
+  silently gets no frame.
 
 ## Notes