@nurix/etna 0.19.50 → 0.19.51

package/data/harnesses/apollo/skills/design/design-md/variants/terse-dense-operator.md

@@ -1,212 +0,0 @@
----
-schema: design-md/v2
-id: terse-dense-operator
-tier: variant
-segments: [ops, fintech, monitoring]
-keywords: [dense, terminal, mono, utilitarian, dark-first, cyan, cockpit]
-sourced: 2026-07-12
-sources: "authored for the v2 variant roster; JetBrains Mono specimen"
-license: open
----
-
-# terse-dense-operator — an engine control room at 03:00
-
-## 1 Visual Theme
-A container ship's engine control room at 03:00: black consoles bolted in
-rows, cyan phosphor readouts, hairline-etched panel labels, not one surface
-that reflects. Dark is the primary mood and is authored first; light is the
-daylight bridge — the same instruments with the sun on. Maximum data per
-pixel: 0–2px radius, hairlines as the only ornament, mono-forward type, no
-shadows pretending to be depth. One cyan accent marks the live thing; all
-else is instrument gray-blue.
-
-## 2 Color Roles
-Pale instrument `foreground` on near-black `background` (dark-first). Cyan
-`primary` marks the one live element — primary action, active nav, the
-`ring` — and nothing else; `accent` is its dim panel-glow tint for the
-selected row. Status hues are signal lamps: `destructive` red, `success`
-green, `warning` amber — on chips, cell states, and thresholds only, and
-they outrank the cyan when lit. The `sidebar` drops a step darker than the
-canvas; every separator is the hairline `border`, never contrast blocks.
-
-## 3 Typography
-JetBrains Mono (display and data) / IBM Plex Sans (chrome). The cockpit
-speaks mono: page titles are JetBrains Mono 700 at 20px — a stencil on a
-panel, not a headline — and every figure, ID, timestamp, and log line is
-mono with `tabular-nums`. IBM Plex Sans carries controls, labels, and body
-where mono would tire the eye. The ramp is compressed (body 13px, data 12px);
-weight changes are the only emphasis. Nothing exceeds 20px anywhere.
-
-## 4 Component Stylings
-Buttons `radius-sm` (0px), `primary` fill only on the single commit action;
-everything else is hairline-outlined `secondary` or ghost. Inputs are flat
-`background` fill with hairline `border`, focus a 2px cyan `ring` — no glow,
-no lift. Cards are hairline-bounded regions of the panel, never shadowed.
-Table rows run at maximum density with `muted` hover, `accent` selection,
-and mono numerals; column dividers are hairlines. Detail opens in a narrow
-side panel; modals confirm destructive acts and do nothing else.
-
-## 5 Layout
-4px base, spent sparingly. Sidebar 224/48px; topbar 44px; side panel
-400/560px; content runs full-bleed to 1920px — a cockpit wastes no glass.
-Gutters stay at 8–12px; density is compressed by default and never relaxes
-below standard even on empty states. Forms are narrow, label-left, built for
-the tab key.
-
-## 6 Depth
-None faked. Light theme: hairlines only; the two declared shadows are
-1px-ring outlines (tinted, near-invisible) that keep overlays legible on
-white, not elevation. Dark theme: the surface ladder is the only depth —
-`background` 0.14 L, `surface-raised` +0.04, `surface-overlay` +0.09, hue
-held at 230. Focus is the 2px `ring`; z-levels: content, sticky chrome,
-overlay. Nothing floats, nothing glows.
-
-## 7 Motion
-Near zero. Named moments: `panel-snap` (side panel, 160ms, interruptible),
-`fade-arrive` (page content, 90ms), `press` (60ms). Row hover, selection,
-sort, and every keyboard-initiated action render instantly — 0ms, by policy.
-Physicality is granted to auth alone, as a single 160ms fade. If a motion is
-noticed twice in a shift, it is too long.
-
-## 8 Iconography & Charts
-Lucide, 1.5px stroke, on a compact 14/16px grid, `muted-foreground` default;
-icons label systems, never decorate. Charts are instruments: hairline axes,
-no gridline fills, no area washes, the cyan-led categorical ramp
-(`chart-1..5`), tooltips on `surface-overlay` with mono numerals, thresholds
-drawn as hairline rules in status hues.
-
-## 9 Voice
-Log-terse: imperative verbs, no pleasantries, values before prose.
-"Ack alert" · "Queue empty — 0 pending, last drain 03:12:47Z" · "Write
-failed: partition 7 read-only since 02:58; retry blocked."
-
-## 10 Do's & Don'ts
-Do put a figure where prose could go. Do keep every radius at 0–2px and
-every separator a hairline. Do let status lamps outrank the cyan when lit.
-Don't shadow anything; the ladder is the only depth. Don't animate hover,
-sort, selection, or anything keyboard-initiated. Don't let mono display type
-grow past 20px — a cockpit has no headlines. Don't relax density for
-aesthetics; whitespace here is unread telemetry.
-
-## 11 Responsive
-375: sidebar → off-canvas rail, side panel → full sheet, tables keep mono
-figures and horizontal scroll — never card-ify telemetry. 768: sidebar holds
-at the 48px icon rail. 1024: two-pane queue+detail holds. 1440–1920:
-columns multiply; the grid fills all available glass, no centering cap
-below 1920px.
-
-## 12 Agent Prompt Guide
-Author dark first; light is the daylight variant of the same panel, not a
-separate look. Every surface leads with its densest useful table. Cyan on
-exactly one live element; when a status lamp lights, cyan yields. No motion
-on anything an operator repeats; 0ms is the default answer. Read the ladder
-from the block — never derive dark, never add a shadow.
-
-```yaml design-values
-color:
-  light:
-    background: oklch(0.965 0.006 230)
-    foreground: oklch(0.2 0.02 235)
-    card: oklch(0.975 0.005 230)
-    card-foreground: oklch(0.2 0.02 235)
-    popover: oklch(0.98 0.005 230)
-    popover-foreground: oklch(0.2 0.02 235)
-    primary: oklch(0.42 0.09 210)
-    primary-foreground: oklch(0.97 0.006 220)
-    secondary: oklch(0.93 0.009 230)
-    secondary-foreground: oklch(0.24 0.02 233)
-    muted: oklch(0.935 0.008 230)
-    muted-foreground: oklch(0.44 0.02 233)
-    accent: oklch(0.9 0.03 210)
-    accent-foreground: oklch(0.33 0.06 215)
-    destructive: oklch(0.53 0.19 27)
-    destructive-foreground: oklch(0.97 0.006 27)
-    success: oklch(0.55 0.12 155)
-    warning: oklch(0.62 0.13 75)
-    border: oklch(0.885 0.01 230)
-    input: oklch(0.885 0.01 230)
-    ring: oklch(0.42 0.09 210)
-    surface-raised: oklch(0.975 0.005 230)
-    surface-overlay: oklch(0.98 0.005 230)
-    chart-1: oklch(0.48 0.1 210)
-    chart-2: oklch(0.55 0.12 150)
-    chart-3: oklch(0.62 0.13 75)
-    chart-4: oklch(0.52 0.12 300)
-    chart-5: oklch(0.5 0.08 255)
-    sidebar: oklch(0.945 0.007 230)
-    sidebar-foreground: oklch(0.2 0.02 235)
-    sidebar-primary: oklch(0.42 0.09 210)
-    sidebar-primary-foreground: oklch(0.97 0.006 220)
-    sidebar-accent: oklch(0.9 0.03 210)
-    sidebar-accent-foreground: oklch(0.33 0.06 215)
-    sidebar-border: oklch(0.885 0.01 230)
-    sidebar-ring: oklch(0.42 0.09 210)
-  dark:
-    background: oklch(0.14 0.01 230)
-    foreground: oklch(0.89 0.012 220)
-    card: oklch(0.17 0.011 230)
-    card-foreground: oklch(0.89 0.012 220)
-    popover: oklch(0.23 0.013 230)
-    popover-foreground: oklch(0.89 0.012 220)
-    primary: oklch(0.8 0.12 200)
-    primary-foreground: oklch(0.14 0.02 225)
-    secondary: oklch(0.22 0.012 230)
-    secondary-foreground: oklch(0.86 0.014 220)
-    muted: oklch(0.2 0.012 230)
-    muted-foreground: oklch(0.68 0.02 225)
-    accent: oklch(0.25 0.035 210)
-    accent-foreground: oklch(0.85 0.08 200)
-    destructive: oklch(0.64 0.2 25)
-    destructive-foreground: oklch(0.11 0.02 25)
-    success: oklch(0.74 0.15 155)
-    warning: oklch(0.78 0.14 75)
-    border: oklch(0.25 0.013 230)
-    input: oklch(0.25 0.013 230)
-    ring: oklch(0.8 0.12 200)
-    surface-raised: oklch(0.18 0.012 230)
-    surface-overlay: oklch(0.23 0.013 230)
-    chart-1: oklch(0.8 0.12 200)
-    chart-2: oklch(0.72 0.13 150)
-    chart-3: oklch(0.78 0.13 75)
-    chart-4: oklch(0.7 0.12 300)
-    chart-5: oklch(0.68 0.1 255)
-    sidebar: oklch(0.12 0.009 230)
-    sidebar-foreground: oklch(0.86 0.014 220)
-    sidebar-primary: oklch(0.8 0.12 200)
-    sidebar-primary-foreground: oklch(0.14 0.02 225)
-    sidebar-accent: oklch(0.19 0.015 230)
-    sidebar-accent-foreground: oklch(0.87 0.014 220)
-    sidebar-border: oklch(0.22 0.012 230)
-    sidebar-ring: oklch(0.8 0.12 200)
-typography:
-  display: { family: "JetBrains Mono Variable", fallback: "ui-monospace, monospace", weights: [700] }
-  sans: { family: "IBM Plex Sans", fallback: "system-ui, sans-serif", weights: [400, 600] }
-  mono: { family: "JetBrains Mono Variable", fallback: "ui-monospace, monospace", weights: [400, 700] }
-  ramp:
-    display: { size: 20px, line: 26px, weight: 700, family: display, tracking: 0em }
-    h1: { size: 18px, line: 24px, weight: 600, family: sans }
-    h2: { size: 15px, line: 20px, weight: 600, family: sans }
-    body: { size: 13px, line: 18px, weight: 400, family: sans }
-    small: { size: 12px, line: 16px, weight: 400, family: sans }
-    caption: { size: 11px, line: 14px, weight: 500, family: sans, tracking: 0.02em }
-    data: { size: 12px, line: 18px, weight: 400, family: mono, features: [tnum] }
-  register-scope: { display: [page-title], sans: [chrome, controls, body], mono: [data, ids, timestamps] }
-elevation:
-  radius: { sm: 0px, md: 2px, lg: 2px }
-  hairline: border
-  shadow:
-    overlay: "0 0 0 1px oklch(0.32 0.015 230 / 0.55)"
-    popover: "0 0 0 1px oklch(0.32 0.015 230 / 0.55)"
-  dark-ladder: { background: 0.14, raised: 0.18, overlay: 0.23, hue-held: 230 }
-motion:
-  duration: { press: 60ms, fade: 90ms, panel: 160ms }
-  easing: { standard: "cubic-bezier(0.2, 0, 0, 1)", exit: "cubic-bezier(0.4, 0, 1, 1)" }
-  entrance-never: ease-in
-  identity-moments: [auth]
-iconography: { set: lucide, stroke: 1.5px, grid: [14px, 16px] }
-charts:
-  categorical: [chart-1, chart-2, chart-3, chart-4, chart-5]
-  sequential: { from: background, to: chart-1 }
-  diverging: { negative: destructive, mid: muted, positive: success }
-layout: { base: 4px, sidebar: [224px, 48px], topbar: 44px, side-panel: [400px, 560px], content-max: 1920px }
-```

package/data/harnesses/apollo/skills/design/design-md/variants/warm-approachable.md

@@ -1,216 +0,0 @@
----
-schema: design-md/v2
-id: warm-approachable
-tier: variant
-segments: [smb, hr, support]
-keywords: [warm, human, soft, rounded, terracotta, humanist, friendly]
-sourced: 2026-07-12
-sources: "authored for the v2 variant roster; Bricolage Grotesque and Nunito Sans specimens"
-license: open
----
-
-# warm-approachable — a neighborhood credit union at opening
-
-## 1 Visual Theme
-A neighborhood credit union at opening time: terracotta tile, an oak counter
-worn smooth at the corner, a hand-lettered welcome card beside the bell,
-coffee already on. Handshake software — light default, neutrals tinted
-toward clay (warm, never cream), one terracotta accent that greets rather
-than commands, gentle radius on everything you touch. The counter is still a
-counter: tables, forms, and figures stay crisp, dense-capable, and honest.
-Dark is the branch after close, lamps amber — an authored ladder, never an
-inversion.
-
-## 2 Color Roles
-Warm graphite `foreground` on a clay-washed `background` — the wash sits at
-the warm-white edge, deliberately clear of the cream band. `primary` is the
-terracotta — primary actions, active nav, the `ring`; `accent` is its peach
-wash for selection and hover. Status hues are conventional but softened:
-`destructive` red for real danger only, `success` leaf green, `warning`
-honey amber — chips and validation, never chrome. The `sidebar` warms a
-half-step below the canvas; nothing on it competes with the counter.
-
-## 3 Typography
-Bricolage Grotesque (display) / Nunito Sans (text) / Red Hat Mono (data).
-Bricolage speaks in page titles, empty states, and auth — a warm,
-characterful voice that never touches cells, buttons, labels, or form
-chrome. Nunito Sans, a humanist sans, carries all chrome and body at a
-comfortable 15px with generous line-height. Red Hat Mono owns figures, IDs,
-and timestamps with `tabular-nums`. Emphasis bumps weight, never size.
-
-## 4 Component Stylings
-Buttons `radius-md`, `primary` fill, comfortable padding — soft-cornered,
-never pill. Inputs are `background` fill with hairline `border` and
-`radius-md`; focus draws the 2px terracotta `ring`, no glow. Cards sit on
-`card` behind a hairline with the faintest clay-tinted shadow. Table rows
-run standard height with `muted` hover and `accent` selection; numerals stay
-mono. Detail opens in the side panel with a warm rule at its head; modals
-confirm, they don't host work.
-
-## 5 Layout
-4px base. Sidebar 260/64px; topbar 56px; side panel 440/680px; content caps
-at 1360px. Comfortable gutters (16–24px); density is standard, stepping
-denser on queue and table archetypes without ever feeling like a terminal.
-Forms run single-column with roomy field spacing — a form here is a
-conversation, not an interrogation.
-
-## 6 Depth
-Soft but honest: hairlines structure everything; cards may carry one faint
-clay-tinted shadow; overlays carry a slightly deeper one. Never gray-black
-shadows, never stacked elevation. Focus is the 2px `ring`. Dark expresses
-depth as the surface ladder: `background` 0.16 L, `surface-raised` +0.05,
-`surface-overlay` +0.10, hue held at 35 — the lamps get warmer, not the
-shadows deeper.
-
-## 7 Motion
-Gentle and brief. Named moments: `panel-slide` (side panel, 260ms,
-interruptible), `fade-arrive` (page content, 180ms), `press` (130ms), and
-`welcome-fade` (first-run empty state, 260ms, the one indulgence). Easing is
-a soft ease-out; nothing springs or bounces. No animation on
-keyboard-initiated or high-frequency actions — friendliness is never
-latency.
-
-## 8 Iconography & Charts
-Lucide at 1.75px stroke — slightly rounded presence to match the humanist
-type — 16/20px grid, `muted-foreground` default; nav and empty states always
-carry icons. Charts: hairline axes, no gridline fills, a warm five-hue
-categorical ramp led by terracotta (`chart-1..5`), tooltips on
-`surface-overlay` with mono numerals.
-
-## 9 Voice
-Front-desk neighborly: plain words, first person welcome, no corporate
-distance, numbers stated honestly. "Add a member" · "No requests waiting —
-enjoy the quiet, or invite your team" · "We couldn't save that: the start
-date is after the end date."
-
-## 10 Do's & Don'ts
-Do keep the warmth in the neutrals and the type, not in extra color — one
-terracotta, spent once per surface. Do give forms room to breathe. Do keep
-figures mono and tables crisp — warm is not vague. Don't drift the
-background into cream; the wash stays at the clay edge, above the band.
-Don't pill buttons or inflate radius past the scale. Don't let Bricolage
-near a cell, button, or label. Don't soften error states into ambiguity —
-kindness is clarity.
-
-## 11 Responsive
-375: sidebar → sheet, side panel → full sheet, tables → stacked cards with
-mono figures; type holds at 15px — small screens get no less warmth. 768:
-sidebar collapses to the icon rail. 1024: two-pane queue+detail holds. 1440:
-content centers under the 1360px cap; empty states earn the full display
-treatment.
-
-## 12 Agent Prompt Guide
-Greet, then serve: every surface opens with its work object in Bricolage,
-then gets out of the way. Terracotta on exactly one action per surface. Keep
-the counter honest — dense tables, mono figures, clear errors — and the
-warmth in surfaces, corners, and copy. Dark is authored — consult the block,
-never derive.
-
-```yaml design-values
-color:
-  light:
-    background: oklch(0.977 0.008 30)
-    foreground: oklch(0.27 0.025 35)
-    card: oklch(0.984 0.006 30)
-    card-foreground: oklch(0.27 0.025 35)
-    popover: oklch(0.984 0.006 30)
-    popover-foreground: oklch(0.27 0.025 35)
-    primary: oklch(0.5 0.13 35)
-    primary-foreground: oklch(0.975 0.008 30)
-    secondary: oklch(0.94 0.012 30)
-    secondary-foreground: oklch(0.31 0.03 35)
-    muted: oklch(0.945 0.01 30)
-    muted-foreground: oklch(0.46 0.025 35)
-    accent: oklch(0.92 0.025 30)
-    accent-foreground: oklch(0.38 0.08 35)
-    destructive: oklch(0.53 0.19 27)
-    destructive-foreground: oklch(0.975 0.008 27)
-    success: oklch(0.57 0.12 150)
-    warning: oklch(0.65 0.13 70)
-    border: oklch(0.905 0.013 30)
-    input: oklch(0.905 0.013 30)
-    ring: oklch(0.55 0.13 35)
-    surface-raised: oklch(0.984 0.006 30)
-    surface-overlay: oklch(0.988 0.005 30)
-    chart-1: oklch(0.55 0.13 35)
-    chart-2: oklch(0.55 0.1 160)
-    chart-3: oklch(0.55 0.09 250)
-    chart-4: oklch(0.68 0.13 85)
-    chart-5: oklch(0.55 0.12 350)
-    sidebar: oklch(0.958 0.01 30)
-    sidebar-foreground: oklch(0.27 0.025 35)
-    sidebar-primary: oklch(0.5 0.13 35)
-    sidebar-primary-foreground: oklch(0.975 0.008 30)
-    sidebar-accent: oklch(0.92 0.025 30)
-    sidebar-accent-foreground: oklch(0.38 0.08 35)
-    sidebar-border: oklch(0.905 0.013 30)
-    sidebar-ring: oklch(0.55 0.13 35)
-  dark:
-    background: oklch(0.16 0.012 35)
-    foreground: oklch(0.91 0.012 35)
-    card: oklch(0.19 0.014 35)
-    card-foreground: oklch(0.91 0.012 35)
-    popover: oklch(0.26 0.016 35)
-    popover-foreground: oklch(0.91 0.012 35)
-    primary: oklch(0.72 0.13 40)
-    primary-foreground: oklch(0.15 0.02 35)
-    secondary: oklch(0.24 0.016 35)
-    secondary-foreground: oklch(0.88 0.014 35)
-    muted: oklch(0.23 0.015 35)
-    muted-foreground: oklch(0.7 0.02 38)
-    accent: oklch(0.29 0.035 35)
-    accent-foreground: oklch(0.86 0.05 40)
-    destructive: oklch(0.63 0.19 25)
-    destructive-foreground: oklch(0.12 0.02 25)
-    success: oklch(0.7 0.12 150)
-    warning: oklch(0.77 0.13 75)
-    border: oklch(0.28 0.016 35)
-    input: oklch(0.28 0.016 35)
-    ring: oklch(0.72 0.13 40)
-    surface-raised: oklch(0.21 0.015 35)
-    surface-overlay: oklch(0.26 0.016 35)
-    chart-1: oklch(0.72 0.13 40)
-    chart-2: oklch(0.7 0.1 160)
-    chart-3: oklch(0.68 0.09 250)
-    chart-4: oklch(0.8 0.12 85)
-    chart-5: oklch(0.7 0.11 350)
-    sidebar: oklch(0.14 0.011 35)
-    sidebar-foreground: oklch(0.89 0.013 35)
-    sidebar-primary: oklch(0.72 0.13 40)
-    sidebar-primary-foreground: oklch(0.15 0.02 35)
-    sidebar-accent: oklch(0.22 0.02 35)
-    sidebar-accent-foreground: oklch(0.89 0.013 35)
-    sidebar-border: oklch(0.26 0.015 35)
-    sidebar-ring: oklch(0.72 0.13 40)
-typography:
-  display: { family: "Bricolage Grotesque Variable", fallback: "system-ui, sans-serif", weights: [600] }
-  sans: { family: "Nunito Sans Variable", fallback: "system-ui, sans-serif", weights: [400, 700] }
-  mono: { family: "Red Hat Mono", fallback: "ui-monospace, monospace", weights: [400] }
-  ramp:
-    display: { size: 30px, line: 38px, weight: 600, family: display, tracking: -0.01em }
-    h1: { size: 24px, line: 32px, weight: 600, family: display }
-    h2: { size: 18px, line: 26px, weight: 700, family: sans }
-    body: { size: 15px, line: 24px, weight: 400, family: sans }
-    small: { size: 13px, line: 20px, weight: 400, family: sans }
-    caption: { size: 12px, line: 16px, weight: 700, family: sans }
-    data: { size: 14px, line: 21px, weight: 400, family: mono, features: [tnum] }
-  register-scope: { display: [page-title, empty-state, auth], sans: [chrome, controls, body], mono: [data, ids, timestamps] }
-elevation:
-  radius: { sm: 6px, md: 10px, lg: 16px }
-  hairline: border
-  shadow:
-    overlay: "0 10px 30px oklch(0.35 0.05 35 / 0.12)"
-    popover: "0 3px 12px oklch(0.35 0.05 35 / 0.09)"
-  dark-ladder: { background: 0.16, raised: 0.21, overlay: 0.26, hue-held: 35 }
-motion:
-  duration: { press: 130ms, fade: 180ms, panel: 260ms }
-  easing: { standard: "cubic-bezier(0.25, 0, 0, 1)", exit: "cubic-bezier(0.4, 0, 1, 1)" }
-  entrance-never: ease-in
-  identity-moments: [auth, first-run-empty]
-iconography: { set: lucide, stroke: 1.75px, grid: [16px, 20px] }
-charts:
-  categorical: [chart-1, chart-2, chart-3, chart-4, chart-5]
-  sequential: { from: background, to: chart-1 }
-  diverging: { negative: destructive, mid: muted, positive: success }
-layout: { base: 4px, sidebar: [260px, 64px], topbar: 56px, side-panel: [440px, 680px], content-max: 1360px }
-```

package/data/harnesses/code/skills/design/data/blueprints/browse.md

@@ -1,38 +0,0 @@
----
-id: browse
-class: d3
-sourced: 2026-07-12
-source: "design-skill-phase1 D3 sweep — distilled from Salesforce list views, GitHub search/Explore, Retool templates, Zendesk views, Notion gallery view, Airtable interfaces, Linear command menu"
-license: open
----
-Composition shapes for the browse archetype — unordered lookup across a record catalog. View-types (table, cards, board) are projections that may appear inside any shape.
-
-## Shape: Filter Rail Browse
-Regions: search/sort bar (full-width, top) / filter rail (left, fixed ~20%, checkboxes and facets) / result area (remaining ~80%, table or card grid) / optional saved-view tabs above the results.
-The eye lands on: the result count and the first few rows or cards immediately right of the rail.
-When to use: users know roughly what they want and need to narrow a large catalog by attributes before picking one.
-Seen in: Salesforce list views with filter tabs, GitHub code/issue search with its left filter sidebar, Retool admin-panel search-and-table patterns.
-
-## Shape: Topic Shelf Browse
-Regions: search bar (top, secondary) / stacked horizontal shelves (full-width, each a named topic or collection) / each shelf scrolls independently left-right.
-The eye lands on: the first shelf's title and its lead card — curation, not a filter control, drives attention.
-When to use: the goal is inspiration or discovery across a broad catalog rather than narrowing toward a known target.
-Seen in: GitHub Explore (Trending repositories, Topics, Collections), Retool's template gallery landing page.
-
-## Shape: Faceted Table Browse
-Regions: saved-view tab strip (top, full-width) / facet and group controls (top-right, compact) / dense table body (full-width, below) with grouped row headers.
-The eye lands on: the active view's name and its row count in the tab strip, then the grouped section headers.
-When to use: the same underlying record set is browsed through several standing, shareable slices rather than one ad hoc filter.
-Seen in: Salesforce list views (Table/Split/Kanban toggle on one saved view), Zendesk ticket views grouped and ordered by field.
-
-## Shape: Gallery Card Browse
-Regions: toolbar (top, thin) / uniform card grid (full-width, cover-forward cards with a small property strip beneath each) / no persistent side rail.
-The eye lands on: the cover or lead property of the first card, not on chrome or filters.
-When to use: the records are visually distinguishable (people, assets, campaigns) and recognition beats reading fields.
-Seen in: Notion gallery view, Airtable's gallery-style interface layouts.
-
-## Shape: Command-First Browse
-Regions: a single centered search/command input (top, dominant) that expands into a ranked result list beneath it as the user types / no visible content before a query.
-The eye lands on: the input caret, then the top-ranked result as it appears.
-When to use: the catalog is too large or too varied to shelf or facet usefully, and users already have a query in mind.
-Seen in: GitHub's global search entry point, Linear's Cmd+K command menu used as a navigation-and-discovery surface.

package/data/harnesses/code/skills/design/data/blueprints/creation-flow.md

@@ -1,38 +0,0 @@
----
-id: creation-flow
-class: d3
-sourced: 2026-07-12
-source: "design-skill-phase1 D3 sweep — distilled from Stripe Connect onboarding, Linear issue creation, GitHub new-repository page, Retool App IDE, Airtable Interface Designer, wizard-pattern references"
-license: open
----
-Composition shapes for the creation-flow archetype — how a new object enters the system. The object's field count, orderedness, and context-sensitivity pick the shape.
-
-## Shape: Linear Stepper Wizard
-Regions: step rail (left or top, numbered, shows progress and lets users jump to completed steps) / one focused form panel per step (center, only the current step's fields are visible) / persistent progress indicator.
-The eye lands on: the current step's label, highlighted in the rail.
-When to use: creation requires many required fields best collected in a specific order, especially with validation or document upload between groups.
-Seen in: Stripe's hosted/embedded Connect account onboarding, generic SaaS setup wizards built around a stepper.
-
-## Shape: Slide-Over Quick Create
-Regions: a right-hand panel or modal (slides over the current screen, ~⅓–½ width) capturing a minimal field set / the underlying list or board stays visible and dimmed behind it.
-The eye lands on: the title/name field, auto-focused at the top of the slide-over.
-When to use: the object being created is simple enough not to need its own page, and preserving the user's current context matters more than a guided sequence.
-Seen in: Linear's issue-creation modal (triggered by `C` or `Cmd+K`, preserves a draft if dismissed).
-
-## Shape: Single-Page Form
-Regions: one dedicated page (full-width, no steps) with fields grouped into clearly labeled sections top to bottom / primary submit action at the bottom of the page.
-The eye lands on: the first required field at the top of the page (commonly a name field).
-When to use: the object has a small, fixed set of fields that don't benefit from being split across steps.
-Seen in: GitHub's "Create a new repository" page (name, description, visibility, template, initialization options all on one page).
-
-## Shape: Builder Canvas Creation
-Regions: component/element palette (left, narrow) / live authoring canvas (center, widest, shows the artifact being built and previewed simultaneously) / property inspector (right, contextual to whatever is selected).
-The eye lands on: whatever element on the canvas was most recently added or selected.
-When to use: the thing being created is itself a visual composition (an app, a page, an interface) rather than a record with fixed fields.
-Seen in: Retool's App IDE; Airtable's Interface Designer when building a new interface from scratch.
-
-## Shape: Guided Checklist Launcher
-Regions: a persistent checklist/progress tracker (top or side, shows completion percentage) / each checklist item expands into its own focused step or opens a separate flow / dismissible and resumable at any time.
-The eye lands on: the next incomplete checklist item, usually highlighted or bolded.
-When to use: setup spans many optional or asynchronous sub-tasks (some requiring external verification) that shouldn't block each other.
-Seen in: Stripe's embedded onboarding requirements flow, generic SaaS account-setup checklists.

package/data/harnesses/code/skills/design/data/blueprints/dashboard.md

@@ -1,38 +0,0 @@
----
-id: dashboard
-class: d3
-sourced: 2026-07-12
-source: "design-skill-phase1 D3 sweep — distilled from Stripe Dashboard home, Datadog dashboards and Dependency Map Navigator, Airtable Interface Designer, network-operations-center layout conventions, BI single-metric report layouts"
-license: open
----
-Composition shapes for the dashboard archetype — many signals summarized for scan or narrative. Which shape fits follows from whether the audience scans for anomalies or reads for a story.
-
-## Shape: KPI Strip + Chart Grid
-Regions: KPI strip (full-width, top, 4–6 tiles each with a value, delta, and inline sparkline) / flexible chart-and-table grid beneath, arranged in a 12-column layout.
-The eye lands on: the single largest number in the leftmost KPI tile.
-When to use: a general operator or executive audience needs the headline health of the business before anything else.
-Seen in: Stripe Dashboard's home page ("Your overview" widgets).
-
-## Shape: Dense Monitoring Grid
-Regions: named tabs (top, grouping widgets into sections) / a 12-column responsive grid packed edge-to-edge with many small, same-scale widgets (graphs, single-value tiles, status lists).
-The eye lands on: whichever widget is currently in an alert/error color state, not a fixed position.
-When to use: the goal is at-a-glance anomaly-spotting across many signals at once, not narrative or storytelling.
-Seen in: Datadog dashboards in high-density mode.
-
-## Shape: Freeform Canvas Dashboard
-Regions: an unconstrained drag-anywhere canvas mixing number tiles, charts, filtered record lists, and text blocks, each element independently sourced from a different underlying table.
-The eye lands on: whichever element the dashboard's author placed largest or first — no default focal convention.
-When to use: the dashboard's authors need full control over juxtaposing heterogeneous content (not just uniform charts) for a specific audience.
-Seen in: Airtable's Interface Designer dashboard layout.
-
-## Shape: Command-Center Split
-Regions: relationship/topology map or geographic overview (left or center, dominant, ~⅔) / live list or table of affected entities (right, ~⅓, sorted by severity, updates in real time).
-The eye lands on: whatever node or row is currently flagged in an alert color.
-When to use: operators must go from "something is wrong somewhere" to "which specific thing" without leaving one screen.
-Seen in: Datadog's Dependency Map Navigator; the video-wall convention of a dominant overview display paired with secondary alert panels used in network operations centers.
-
-## Shape: Narrative Single-Column Report
-Regions: one hero chart or metric (top, full-width) / supporting breakdown tables and secondary charts stacked below it in reading order / minimal or no side chrome.
-The eye lands on: the hero chart's headline trend line.
-When to use: the dashboard is meant to be read top-to-bottom like a report, telling one story, rather than scanned for many independent signals.
-Seen in: single-metric deep-dive report layouts common to BI tools built around one hero visualization followed by supporting cuts of the same data.

package/data/harnesses/code/skills/design/data/blueprints/grid.md

@@ -1,38 +0,0 @@
----
-id: grid
-class: d3
-sourced: 2026-07-12
-source: "design-skill-phase1 D3 sweep — distilled from Airtable grid view and grouped views, Notion table side peek, Retool App IDE and admin templates, spreadsheet-style admin tables"
-license: open
----
-Composition shapes for the grid archetype — many records edited or scanned across many fields at once, spreadsheet-fashion.
-
-## Shape: Frozen-Header Spreadsheet
-Regions: toolbar (top, view switch / row-height / filter controls) / grid body (full-width, first column(s) frozen while scrolling horizontally) / add-row affordance pinned to the bottom edge.
-The eye lands on: the frozen leftmost column, which anchors every row as the grid scrolls.
-When to use: users need to scan and bulk-edit many records across many fields the way they would in a spreadsheet.
-Seen in: Airtable grid view, Google-Sheets-style admin data tables.
-
-## Shape: Grid + Side Peek
-Regions: grid (majority of width, ~70–80%) / record detail panel (right, slides in on row selection, ~20–30%, doesn't navigate away from the grid).
-The eye lands on: the selected row's highlighted state in the grid, then the panel that opens beside it.
-When to use: editing one record's full detail is common but shouldn't cost the user their place in the larger table.
-Seen in: Airtable's expand-record-from-grid interaction, Notion's table view opening records in a side peek.
-
-## Shape: Grouped Grid with Subtotals
-Regions: grid body (full-width) organized into collapsible group bands, each with a header row carrying aggregate stats (count, sum, average) for that group.
-The eye lands on: the group header's aggregate figure, before any individual row.
-When to use: the grid's job is roll-up reporting on structured data, not just record-by-record editing.
-Seen in: Airtable's grouped grid view with per-group summary bars.
-
-## Shape: Builder Canvas Grid
-Regions: component palette (left, narrow, categorized list) / authoring canvas (center, widest, a 12-column grid used to place UI components rather than data rows) / inspector (right, contextual to the selected component).
-The eye lands on: the component currently selected on the canvas, highlighted against the grid.
-When to use: the "grid" is the structural device for assembling an interface or app, not for displaying records.
-Seen in: Retool's App IDE (canvas + component tree + Inspector panel).
-
-## Shape: Bulk-Action Grid
-Regions: search/filter bar (top) / grid with a persistent selection checkbox column (left edge) / sticky bulk-action toolbar that appears above the grid only once rows are selected.
-The eye lands on: the selection-count indicator in the bulk-action toolbar once it appears.
-When to use: the primary job is applying one action to many rows at once (delete, export, reassign), not editing cells individually.
-Seen in: Retool admin-panel table/search/form templates built for internal operators.

package/data/harnesses/code/skills/design/data/blueprints/queue.md

@@ -1,38 +0,0 @@
----
-id: queue
-class: d3
-sourced: 2026-07-12
-source: "design-skill-phase1 D3 sweep — distilled from Zendesk Agent Workspace, Salesforce Split View, Intercom inbox, Superhuman Split Inbox, Gmail preview pane, Jira-style backlog tables"
-license: open
----
-Composition shapes for the queue archetype — prioritized, claimable work processed toward empty. The list order is the product; view-types are projections.
-
-## Shape: Split Triage
-Regions: item list (left, ~⅓, one row per item, unread/priority state visible) / reading pane (right, ~⅔, shows the selected item in full) / action bar pinned to the reading pane's top edge.
-The eye lands on: the subject or title of the item open in the reading pane.
-When to use: operators process items one at a time but need the surrounding list visible to keep their place and jump ahead.
-Seen in: Gmail's preview-pane layout, Salesforce Split View, Intercom's conversation table with a preview panel.
-
-## Shape: Three-Column Context Triage
-Regions: ticket properties (left, narrow, editable fields) / conversation thread (center, widest, scrolls independently) / context panel (right, collapsible, customer/account data pulled from other systems).
-The eye lands on: the newest message in the center conversation thread.
-When to use: resolving one item requires both editing structured fields and reading unstructured context side by side.
-Seen in: Zendesk Agent Workspace's ticket interface.
-
-## Shape: Card-Stack Triage
-Regions: a single focal card (center, dominant, full item detail) with decision controls (approve/reject/skip) directly beneath it / no persistent list visible at all.
-The eye lands on: the one card currently in front of the operator.
-When to use: throughput and low cognitive load matter more than seeing what's next or re-ordering the queue.
-Seen in: moderation/review-queue patterns built around one-decision-at-a-time keyboard flows (the pattern Superhuman's and Zendesk's triage conventions both borrow from).
-
-## Shape: Grouped Table Queue
-Regions: standing view tabs (top, each a saved filter) / dense table (full-width, grouped by a status or priority field with collapsible group headers) / row click opens detail rather than a separate pane.
-The eye lands on: the group header counts, which signal where backlog is piling up.
-When to use: triage is about prioritizing across the whole backlog first, and deep work on one item happens after selection, not alongside it.
-Seen in: Zendesk's saved Views grouped and ordered by field, Jira-style backlog triage tables.
-
-## Shape: Zero-Chrome Queue
-Regions: a single wide column (full-width, no folders/menus/sidebar) listing items as compact single-line rows / a shortcuts overlay appears on demand rather than living in permanent chrome.
-The eye lands on: the top unprocessed row.
-When to use: expert operators triage at very high volume and any persistent chrome would slow them down.
-Seen in: Superhuman's Split Inbox list view.