figura-cli 0.23.1 → 0.23.2

package/package.json

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

package/skills/fig/SKILL.md

@@ -143,6 +143,19 @@ so you hand it the studied structure in the brief (see step 3, "Server render").
      in that screen's `css`.
    - Plus `area`, `title`, `orientation`, and a real `description`.
 
+   **Small screens are the SERVER's job — with one exception that is yours.**
+   Below a catalog-derived breakpoint every multi-frame layout (`compare`,
+   `variations`, `overview-focus`) restructures itself: ONE frame at a time, as
+   large as fits (never under 0.72 scale), behind a sticky bottom switcher, with
+   the Overview grid dropped. You do not write a media query, a toggle, or a
+   scale for this, and there is nothing to remember — it is emitted for you.
+   What the server CANNOT do is name the frames: **each screen's `label` IS the
+   switcher button**, so `label: 'Empty state'` / `'After save'` works and a
+   missing label degrades to `1`, `2`, `3`. Give every screen a short, distinct,
+   thumb-sized label. Design each screen's CONTENT to survive a 0.72 scale too —
+   ~11px is the floor for body copy at that scale, so 10px annotations are yours
+   to avoid.
+
    This uses the caller's own Claude — no extra cost. Follow the scaffold's brand
    values verbatim; never invent brand values or restate design rules from memory.
    **Fallback if the scaffold fetch fails** (older engine/CLI): fetch just the
@@ -272,7 +285,7 @@ pattern must be hand-authored — plain CSS-only radio tabs, binary, no library:
 
 **★ FOCUS IS THE DEFAULT VIEW.** The fig opens on ONE full-size frame with state
 pills — on desktop AND mobile. Overview is the *alternative*, behind the second
-tab. Never open a redesign fig on the scaled grid: `layout: 'variations'` (a
+tab, and on a phone it is dropped entirely: there the pills ARE the interface. Never open a redesign fig on the scaled grid: `layout: 'variations'` (a
 scan-only grid at the kit's `--fig-scale:0.34`) is NOT a redesign presentation —
 using it for one shipped a 4-state fig as 134px phones with ~3px annotation
 chips. A Focus-only fig is **complete on its own**; add Overview only when there
@@ -283,6 +296,10 @@ are enough states that scanning them at once genuinely helps.
   reads as spot-the-difference. This is where the context lives, pinned on the
   frame as annotation chips: what's broken today, what each variation improves,
   what it trades away. Open on the first pill = the honest current state.
+- **Never put annotation chips inside a clipping box.** `position:absolute`
+  cannot escape an ancestor's `overflow:hidden`, so a chip that straddles a
+  rounded-corner frame ships sliced. Hang chips off a positioned wrapper as
+  siblings of the frame, anchored to grow away from its edge.
 - **Overview — side by side (alternative).** Every state at once: the honest
   current state first, then each variation, as scaled-down frames in a grid.
   Under each: a status chip and ONE condensed context line (`+ / –`). This view
@@ -315,16 +332,24 @@ are enough states that scanning them at once genuinely helps.
      giving it dimensions. It checks every injected component (device frame,
      status bar, control bar, browser chrome), cross-checks the manifest's
      `components` array, and reports the fig's own `frameKit` / `complete` /
-     `doubleFramed` checks; `--json` for machine output. The engine won't
-     silently drop the kit anymore, and create/revise now warns loudly if it
-     ever did — this is the check that *proves* a frame renders.
-  3. **Screenshot THAT** (the printed served HTML, saved to a deterministic
-     project-scoped path — the repo's `.figura/figs/` (gitignored), or
-     `~/.figura/figs/` outside a bound repo, never `/tmp`/`mktemp`), at a few
-     viewport widths: `document.scrollWidth` must equal the viewport in every
-     view and state (sideways scroll = broken), and no annotation chip may
-     cover the content it annotates. `figura fig open <id> --local` writes the
-     same served bytes to `<repo>/.figura/figs/figura-fig-<id>.html`.
+     `doubleFramed` checks; `--json` for machine output. This is the check that
+     *proves* a frame renders. These are static checks over the served bytes —
+     `verify` reads markup and CSS, it lays nothing out, so it cannot see
+     overflow or a clipped chip.
+  3. **Screenshot THAT yourself** — layout is nothing `verify` reports. Take the
+     printed served HTML, saved to a deterministic project-scoped path (the
+     repo's `.figura/figs/` (gitignored), or `~/.figura/figs/` outside a bound
+     repo, never `/tmp`/`mktemp`), and render it at a few viewport widths.
+     `document.scrollWidth` must equal the viewport in every view and state
+     (sideways scroll = broken), no annotation chip may cover the content it
+     annotates, and no chip may be cut by a clipping ancestor: walk each chip's
+     ancestors up to `<html>` and, wherever computed `overflow` is
+     `hidden`/`clip`, assert the chip's rect stays inside that ancestor's box —
+     the viewport box for `<body>`/`<html>`, whose overflow propagates there.
+     Comparing a chip to the frame's rect alone misses the vertical escape, and
+     no rect test sees a rounded clip, which is why the authoring rule above is
+     the real guarantee. `figura fig open <id> --local` writes the same served
+     bytes to `<repo>/.figura/figs/figura-fig-<id>.html`.
 
 A **wipe-slider** stays the narrow tool for exactly two states of the same
 layout with pixel-level tweaks. Never ship a squeezed side-by-side as the

package/skills/skills.json

@@ -1,7 +1,13 @@
 {
   "$comment": "Skill version manifest (#752) — the source of truth for each Figura skill's OWN version line, DECOUPLED from the figura-cli package version. A release bumps the version here when a skill's content changes, then regenerates the engine seed (bun packages/core/scripts/build-skill-seed.mjs) and re-seeds. Version is a date tag (YYYY.MM.DD[.n]); releasedAt is ISO-8601. The CLI/MCP stamp this version into .figura-version at install; the engine seeds the registry from it.",
   "skills": {
-    "fig": { "version": "2026.07.28", "releasedAt": "2026-07-28T00:00:00.000Z" },
-    "figura-brand": { "version": "2026.07.26", "releasedAt": "2026-07-26T00:00:00.000Z" }
+    "fig": {
+      "version": "2026.08.04",
+      "releasedAt": "2026-08-04T17:44:19.938Z"
+    },
+    "figura-brand": {
+      "version": "2026.07.26",
+      "releasedAt": "2026-07-26T00:00:00.000Z"
+    }
   }
 }