@nurix/etna 0.19.51 → 0.19.53

package/data/harnesses/apollo/skills/design/data/motion/number-ticker-roll.md

@@ -0,0 +1,18 @@
+---
+id: number-ticker-roll
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/animation-vocabulary/SKILL.md (Number ticker; Tabular numbers) + review-animations/STANDARDS.md (sub-300ms rule; interruptibility)"
+license: open
+feel: "digits rolling to the new value at ~250ms read like a live counter; an instant jump-cut reads like the number just glitched"
+aliases: { glitched: "value changes with no roll/interpolation at all", "tabular-drift": "digits set without tabular figures, so the number visibly shifts width as it rolls", janky: "keyframe roll restarting from zero on each rapid update instead of retargeting" }
+---
+Live counters, stat tiles, KPI cards, running totals — system-driven value changes, so the sub-300ms UI rule applies. Requires tabular figures so surrounding layout doesn't shift while digits roll. Rapid successive updates retarget the roll (transition, not keyframes), never restart from zero.
+
+```yaml values
+duration: 250ms
+easing: cubic-bezier(0.23, 1, 0.32, 1)
+element-class: control
+interruptible: required
+budget: { control: 200-300ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/onboarding-bounce.md

@@ -0,0 +1,18 @@
+---
+id: onboarding-bounce
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/review-animations/STANDARDS.md (springs — bounce 0.1-0.3, reserved for playful moments) + improve-animations/AUDIT.md §1 (rare/first-time → delight)"
+license: open
+feel: "a springy overshoot on a first-run welcome card reads warm and considered; the same bounce on anything seen daily reads gimmicky"
+aliases: { gimmicky: "spring bounce applied outside a rare/first-time identity moment — the same overshoot on a daily-use control", overdone: "bounce pushed above the 0.1-0.3 range into cartoonish territory" }
+---
+Onboarding welcome screens, first-run tours — rare, high-emotion, seen once or a handful of times ever. The scoped exception where springy/physical vocabulary is admissible; it does not license bounce anywhere else.
+
+```yaml values
+duration: 500ms (spring; no fixed duration)
+easing: spring(bounce 0.3)
+element-class: identity-moment
+interruptible: n/a
+budget: { identity-moment: 400-600ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/panel-slide.md

@@ -0,0 +1,18 @@
+---
+id: panel-slide
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/review-animations/STANDARDS.md (--ease-drawer curve; duration table, modal/drawer row) + apple-design/SKILL.md §3 (interruption; velocity continuity)"
+license: open
+feel: "a 260ms slide on the iOS drawer curve reads native and grabbable; a keyframe slide that restarts on repeated taps reads broken"
+aliases: { broken: "keyframes restarting from zero instead of a transition/spring retargeting mid-slide", floaty: "duration pushed past the panel budget" }
+---
+Side panels, drawers, bottom sheets. Must be interruptible and carry velocity on a gesture-driven close — grabbing a closing panel should follow the pointer, not fight it.
+
+```yaml values
+duration: 260ms
+easing: cubic-bezier(0.32, 0.72, 0, 1)
+element-class: panel
+interruptible: required
+budget: { panel: 200-500ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/press-feedback.md

@@ -0,0 +1,18 @@
+---
+id: press-feedback
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/review-animations/STANDARDS.md (physicality — press feedback; duration table) + improve-animations/AUDIT.md §2-3"
+license: open
+feel: "160ms scale-to-0.97 on pointer-down reads tactile and instant; slower or absent reads dead under the finger"
+aliases: { dead: "no press feedback at all, or duration pushed above the 160ms control budget", mushy: "an easing softer than ease-out, delaying the visible response" }
+---
+Any pressable control — buttons, icon buttons, tap-target rows. The canon prescribes this on every pressable element while forbidding animation on keyboard-initiated actions: it fires on pointer-down only (a tap affordance, not a state transition), and keyboard activation (Enter/Space) never replays it.
+
+```yaml values
+duration: 160ms
+easing: cubic-bezier(0.23, 1, 0.32, 1)
+element-class: control
+interruptible: n/a
+budget: { control: 100-160ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/progress-linear-loop.md

@@ -0,0 +1,18 @@
+---
+id: progress-linear-loop
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/review-animations/STANDARDS.md (easing decision order — constant motion → linear) + animation-vocabulary/SKILL.md (Loop; Marquee); Material's linear token agrees as secondary"
+license: open
+feel: "a constant linear sweep reads honest about an unknown wait; any easing that speeds up and slows down reads like a fake promise"
+aliases: { "fake-promise": "eased (non-linear) motion on an indeterminate progress indicator, implying a completion point that doesn't exist", twitchy: "loop cycle faster than ~1s, reading anxious rather than calm" }
+---
+Indeterminate progress bars, loading spinners, marquees. Constant-speed motion only — the one place `linear` is correct and `ease` curves are wrong.
+
+```yaml values
+duration: 1200ms (loop)
+easing: linear
+element-class: control
+interruptible: n/a
+budget: { control: 1000-1500ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/route-crossfade.md

@@ -0,0 +1,18 @@
+---
+id: route-crossfade
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/animation-vocabulary/SKILL.md (Crossfade; Page transition) + review-animations/STANDARDS.md (sub-300ms rule; masking imperfect crossfades; easing decision order — opacity/color → ease)"
+license: open
+feel: "a single ~250ms crossfade between views reads like one continuous product; a staggered reveal of each panel on arrival reads like a slideshow"
+aliases: { slideshow: "child elements staggering in individually on route arrival instead of one crossfade", "double-exposed": "old and new view both fully visible mid-transition — mask with a subtle blur (~2px, never above 20px)" }
+---
+Navigating between routes or top-level views — a same-place opacity morph, not a spatial entrance, so `ease` rather than the entrance curve. One crossfade only; never an orchestrated sequence of the destination's own elements arriving one by one. A product loads into a task, not a reveal.
+
+```yaml values
+duration: 250ms
+easing: ease
+element-class: page
+interruptible: n/a
+budget: { page: 200-300ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/rubber-band-overscroll.md

@@ -0,0 +1,18 @@
+---
+id: rubber-band-overscroll
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/animation-vocabulary/SKILL.md (Rubber-banding) + apple-design/SKILL.md §8 (boundary resistance) and spring cheat-sheet (critically-damped default)"
+license: open
+feel: "resistance that grows the further you pull, then a quick snap-back, reads alive and physical; a hard stop at the edge reads frozen"
+aliases: { frozen: "a hard stop at the scroll boundary instead of progressive resistance", overshoot: "snap-back overshoots past the origin instead of settling cleanly" }
+---
+Scrollable containers and pull-to-refresh regions at their boundary. Resistance increases continuously with drag distance past the edge; release animates back with a critically-damped spring, never a linear tween.
+
+```yaml values
+duration: 300ms (snap-back)
+easing: spring(damping increases near boundary)
+element-class: page
+interruptible: required
+budget: { page: 200-400ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/skeleton-shimmer.md

@@ -0,0 +1,18 @@
+---
+id: skeleton-shimmer
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/animation-vocabulary/SKILL.md (Skeleton/Shimmer) + review-animations/STANDARDS.md (easing decision order — constant motion → linear)"
+license: open
+feel: "a slow, continuous sheen reads like content is genuinely on its way; a fast or jittery shimmer reads anxious"
+aliases: { anxious: "shimmer cycle faster than ~1s, reading twitchy instead of calm", stuck: "a static placeholder with no shimmer at all, giving no sense of progress" }
+---
+Loading placeholders for cards, rows, and detail panes before content resolves. Runs as a continuous ambient loop, exempt from the sub-300ms UI budget (constant-motion class); swap to real content with a quick crossfade, not a hard cut.
+
+```yaml values
+duration: 1400ms (loop)
+easing: linear
+element-class: list-item
+interruptible: n/a
+budget: { list-item: 1200-1600ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/stagger-arrive.md

@@ -0,0 +1,18 @@
+---
+id: stagger-arrive
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/review-animations/STANDARDS.md (stagger — 30-80ms, decorative, never blocks interaction)"
+license: open
+feel: "a ~50ms cascade with a small upward drift reads considered; everything landing at once reads dumped, and gaps above 80ms read slow"
+aliases: { dumped: "no stagger at all on a multi-item entrance", draggy: "per-item stagger delay above the 80ms budget" }
+---
+List and grid entrances for freshly-loaded content within a task (search results, new rows) — never on initial page load or route arrival (no orchestrated load sequences). Purely decorative — must never delay the list becoming interactive; keep the per-item delay inside 30-80ms so a ten-row list finishes well under half a second.
+
+```yaml values
+duration: 300ms
+easing: cubic-bezier(0.23, 1, 0.32, 1)
+element-class: list-item
+interruptible: n/a
+budget: { list-item: 250-350ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/toast-enter-stack.md

@@ -0,0 +1,18 @@
+---
+id: toast-enter-stack
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/review-animations/STANDARDS.md (interruptibility — toast transition example; cohesion — the Sonner register)"
+license: open
+feel: "a 400ms transition-based stack reads calm even when toasts pile up fast; a keyframe stack reads jumpy every time a new one lands"
+aliases: { jumpy: "@keyframes restarting already-stacked toasts instead of one continuous transition retargeting them", jarring: "no @starting-style/mount fallback, so the first toast snaps in with no entrance" }
+---
+Toast/notification stacks. A new arrival must not restart the position transition of toasts already stacked — everything reflows on one continuous transition, never per-toast keyframes.
+
+```yaml values
+duration: 400ms
+easing: ease
+element-class: overlay
+interruptible: required
+budget: { overlay: 300-450ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/tooltip-chain-instant.md

@@ -0,0 +1,18 @@
+---
+id: tooltip-chain-instant
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/emil-design-eng/SKILL.md (tooltip-chaining example) + review-animations/STANDARDS.md (duration table, tooltip row; perceived performance)"
+license: open
+feel: "the first tooltip's 125ms fade-and-lift reads considered; every later tooltip in the same toolbar should read instant, with zero animation"
+aliases: { "laggy-toolbar": "every tooltip in a group replaying the full delay+animation instead of chaining to instant after the first", floaty: "duration above the small-popover budget" }
+---
+Tooltips, especially adjacent ones in a toolbar. First open: full delay + animation. While the pointer stays within the tooltip group, later tooltips switch to 0ms — this is the frequency law being satisfied, not an exception to it.
+
+```yaml values
+duration: 125ms
+easing: cubic-bezier(0.23, 1, 0.32, 1)
+element-class: control
+interruptible: n/a
+budget: { control: 0-200ms }
+```

package/data/harnesses/apollo/skills/design/data/motion/trigger-anchored-reveal.md

@@ -0,0 +1,18 @@
+---
+id: trigger-anchored-reveal
+class: a6
+sourced: 2026-07-12
+source: "emilkowalski.skills/skills/review-animations/STANDARDS.md (physicality — origin-aware popovers; duration table, dropdown row) + improve-animations/AUDIT.md §3"
+license: open
+feel: "growing out of the trigger at ~200ms reads anchored and native; center-scale or scale(0) reads like a random popup"
+aliases: { disconnected: "transform-origin left at center instead of the trigger element", glitchy: "scale(0) start instead of scale(0.9-0.97) + opacity" }
+---
+Popovers, dropdowns, select menus, tooltips. `transform-origin` follows the trigger (Radix/Base UI expose it as a CSS var); never centers. Rapid open/close/open must retarget, not restart.
+
+```yaml values
+duration: 200ms
+easing: cubic-bezier(0.23, 1, 0.32, 1)
+element-class: overlay
+interruptible: required
+budget: { overlay: 150-250ms }
+```

package/data/harnesses/apollo/skills/design/data/tells.csv

@@ -0,0 +1,34 @@
+id,tell,category,provenance,sourced,status
+tell-001,"every shadow set to zero and every border the same 1px gray — structure without a single elevation decision",wireframe-smell,"design-skill 01 §E5; impeccable detector registry",2026-07-12,active
+tell-002,"rounded-square icon tile stacked above the heading on every card — the universal generated feature-card template",template,"impeccable detector registry (icon-tile-stack)",2026-07-12,active
+tell-003,"cards nested inside cards — double borders and stacked radii standing in for hierarchy",card-abuse,"impeccable detector registry (nested-cards); design-skill 01 §E5",2026-07-12,active
+tell-004,"thick colored stripe down one edge of a card as the accent device",accent-abuse,"impeccable detector registry (side-tab); design-skill 01 §E5",2026-07-12,active
+tell-005,"accent border wrapped around a rounded card — the stripe fighting the corner radius",accent-abuse,"impeccable detector registry (border-accent-on-rounded)",2026-07-12,active
+tell-006,"hero-metric template — a row of identical stat tiles each icon + label + big number, with no comparison, trend, state, or door",template,"design-skill 01 §E5; b2b-ux-patterns dashboards chapter",2026-07-12,active
+tell-007,"cream or warm-beige page surface reached by reflex as the tasteful default",palette,"impeccable detector registry (cream-palette); taste-skill §9.A; design-skill 01 §A2 anti-cream guardband",2026-07-12,active
+tell-008,"ghost cards — bordered or shadowed containers wrapping a single short text run or nothing at all",card-abuse,"design-skill 01 §E5",2026-07-12,active
+tell-009,"purple-violet gradients and cyan-on-dark as the default accent scheme",palette,"impeccable detector registry (ai-color-palette)",2026-07-12,active
+tell-010,"dark theme expressed as colored box-shadow glows instead of a surface-lightness ladder",palette,"impeccable detector registry (dark-glow); design-skill 01 §A3 dark ladder",2026-07-12,active
+tell-011,"gradient fills on heading or metric text",typography,"impeccable detector registry (gradient-text)",2026-07-12,active
+tell-012,"flat type ramp — adjacent sizes too close together to carry hierarchy anywhere on the surface",typography,"impeccable detector registry (flat-type-hierarchy)",2026-07-12,active
+tell-013,"one spacing value everywhere — no tight grouping of related controls, no generous seams between sections",layout,"impeccable detector registry (monotonous-spacing)",2026-07-12,active
+tell-014,"hairline border and a wide diffuse shadow on the same container — two elevation systems at once",elevation,"impeccable detector registry (generated-UI signature set)",2026-07-12,active
+tell-015,"decorative two-axis hairline grid background behind a surface that is not a canvas, map, or measurement view",template,"impeccable detector registry (generated-UI signature set)",2026-07-12,active
+tell-016,"numbered section markers (01 / 02 / 03) as structural scaffolding",template,"impeccable detector registry (numbered-section-markers); taste-skill §9.F",2026-07-12,active
+tell-017,"tiny uppercase letter-spaced kicker label repeated above every section heading",template,"impeccable detector registry (repeated-section-kickers)",2026-07-12,active
+tell-018,"colored status dots decorating every nav item, row, or badge with no real state behind them",chrome,"taste-skill §9.F production-observed tells",2026-07-12,active
+tell-019,"middle-dot chains as the default separator for every metadata strip",chrome,"taste-skill §9.F production-observed tells",2026-07-12,active
+tell-020,"top and bottom hairline borders on every row of a long table or spec list",wireframe-smell,"taste-skill §9.F production-observed tells",2026-07-12,active
+tell-021,"fake build or version strings as decoration where no real build data exists",demo-content,"taste-skill §9.F production-observed tells",2026-07-12,active
+tell-022,"placeholder-generic person names in demo data (the John Doe class)",demo-content,"taste-skill §9.D (Jane Doe effect); design-skill 01 §E5",2026-07-12,active
+tell-023,"the same gray egg or user-icon avatar on every person row",demo-content,"taste-skill §9.D production-observed tells",2026-07-12,active
+tell-024,"fake-perfect numbers — round percentages, sequential IDs, totals that reconcile too neatly",demo-content,"taste-skill §9.D; design-skill 01 §E5",2026-07-12,active
+tell-025,"startup-slop company names in demo data (the Acme / Nexus / Cloudly class)",demo-content,"taste-skill §9.D production-observed tells",2026-07-12,active
+tell-026,"marketing buzzwords in interface copy (streamline, empower, supercharge, enterprise-grade)",copy,"impeccable detector registry (marketing-buzzword); taste-skill §9.D",2026-07-12,active
+tell-027,"em-dash-heavy microcopy — the character recurring across labels, empty states, and tooltips",copy,"taste-skill §9.G; impeccable detector registry (em-dash-overuse)",2026-07-12,active
+tell-028,"transition: all on interactive elements",motion,"design-skill 02 ship-gate Tier-2 motion tells",2026-07-12,active
+tell-029,"ease-in easing on an entrance",motion,"design-skill 02 ship-gate Tier-2 motion tells; emilkowalski motion canon",2026-07-12,active
+tell-030,"animation attached to a keyboard-triggered action",motion,"design-skill 02 ship-gate Tier-2 motion tells; emilkowalski frequency law",2026-07-12,active
+tell-031,"bounce or elastic easing on product chrome",motion,"impeccable detector registry (bounce-easing)",2026-07-12,active
+tell-032,"width, height, padding, or margin animated instead of transform and opacity",motion,"impeccable detector registry (layout-transition)",2026-07-12,active
+tell-033,"orchestrated staggered entrance choreography on a work surface — a product loads into a task",motion,"design-skill 01 §A6 admission criteria; emilkowalski motion canon",2026-07-12,active

package/data/harnesses/apollo/skills/design/data/voices/bright-collaborator.md

@@ -0,0 +1,29 @@
+---
+id: bright-collaborator
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Slack's voice & tone guidance (api.slack.com/best-practices/voice-and-tone) — confident not cocky, witty not silly, clear-concise-human, tone as seasoning not the dish."
+license: open
+---
+# Voice: bright-collaborator
+
+**Feel:** Confident and a little playful, but the point always lands first.
+
+Conversational rhythm — short sentences mixed with one longer one for cadence, contractions standard, second person throughout. Personality is seasoning: light wit is reserved for confirmations and empty states, never for errors. Actions open with a verb. Numbers are digits. One idea per sentence — never two clauses competing for attention.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** verb-first with a light conversational lift
+- **error:** personality drops out entirely — plain statement, then the fix
+- **success:** wit is allowed, one line, never stacked
+- **destructive confirmation:** playfulness fully off, states the stakes plainly
+
+## Examples
+
+- **button:** "Invite teammate"
+- **empty state (heading + motivation):** "Quiet in here" / "Invite a teammate and this space starts filling up."
+- **error:** "That invite didn't go through. Check the email and send it again."
+- **tooltip:** "Only workspace admins can see this."
+- **confirmation:** "Teammate invited — welcome aboard."

package/data/harnesses/apollo/skills/design/data/voices/direct-operator.md

@@ -0,0 +1,29 @@
+---
+id: direct-operator
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Atlassian's 'bold, optimistic, practical' brevity mandate (atlassian.design/content/voice-and-tone-principles) and Material Design's clarity-to-anyone standard (m3.material.io/foundations/content-design)."
+license: open
+---
+# Voice: direct-operator
+
+**Feel:** Brisk and task-first — reads like a command line, not a conversation.
+
+Imperative mood by default; sentence fragments are acceptable where a full sentence adds nothing ("Upload failed. Retry."). No adjectives unless load-bearing. Numerals are always digits, units abbreviated once established. No exclamation points, no rhetorical questions, no throat-clearing openers ("Please note that…"). Density over politeness — every word has to justify its presence.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** imperative, fragments allowed
+- **error:** states failure plus count or reason, no softening
+- **success:** single clipped phrase, no embellishment
+- **destructive confirmation:** same flat register as everything else — no added urgency language, the plainness is the safeguard
+
+## Examples
+
+- **button:** "Create workspace"
+- **empty state (heading + motivation):** "No records" / "Import a file or add one manually to begin."
+- **error:** "Save failed. 3 fields are invalid."
+- **tooltip:** "Locks the row for editing by others."
+- **confirmation:** "Workspace created."

package/data/harnesses/apollo/skills/design/data/voices/earnest-helper.md

@@ -0,0 +1,29 @@
+---
+id: earnest-helper
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Intercom's PREACH framework (intercom.com/blog/preach-framework-for-customer-support-tone) — Proud, Responsible, Empathetic, Articulate, Concise, Human."
+license: open
+---
+# Voice: earnest-helper
+
+**Feel:** Owns the failure, states the fix, never grovels.
+
+First-person-plural ownership when the product is at fault ("we couldn't…"), second person when guiding the user's next step. Sentences are short and declarative; empathy is shown through precision and a clear next step rather than apology words ("sorry," "oops" are avoided). No exclamation points, even on success — confidence doesn't need punctuation. Numbers are digits throughout.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** second person, concise, no flourish
+- **error:** first-person-plural ownership ("we couldn't…"), immediate next step
+- **success:** short, no exclamation, confidence without decoration
+- **destructive confirmation:** states irreversibility explicitly, still no apology language
+
+## Examples
+
+- **button:** "Submit request"
+- **empty state (heading + motivation):** "No requests yet" / "Submit one and track its progress here."
+- **error:** "We couldn't submit that request. Reconnect and try again."
+- **tooltip:** "Requests are visible to your whole team once submitted."
+- **confirmation:** "Request submitted."

package/data/harnesses/apollo/skills/design/data/voices/editorial-composed.md

@@ -0,0 +1,29 @@
+---
+id: editorial-composed
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Material Design's AP-style clarity standard (m3.material.io/foundations/content-design/style-guide/ux-writing-best-practices) and Atlassian's 'practical, with a wink' brand register (atlassian.design/content/writing-style), slowed to an editorial cadence."
+license: open
+---
+# Voice: editorial-composed
+
+**Feel:** Measured and literate — composed sentences, unhurried but exact.
+
+Longer, fully-formed sentences that favor a subordinate clause over a fragment; still one idea per sentence, but the idea is given room. Verbs remain the engine of the sentence rather than being buried under nominalizations. Numbers under ten are spelled out even in most UI text; digits are reserved for data-dense contexts (tables, counters, timestamps). Restraint reads as taste, not coldness — warmth comes from word choice, never from exclamation.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** a fuller sentence, still verb-led
+- **error:** composed, no blame, the fix named in a complete sentence
+- **success:** a complete, satisfying sentence rather than a clipped label
+- **destructive confirmation:** the most fully-formed of the four — consequence and reversibility spelled out in full
+
+## Examples
+
+- **button:** "Add collection"
+- **empty state (heading + motivation):** "Nothing archived yet" / "Items you archive will be kept here, in order, for as long as you need them."
+- **error:** "The collection couldn't be saved. Review the highlighted fields and try again."
+- **tooltip:** "Determines the order collections appear in for every viewer."
+- **confirmation:** "Collection added and ready to share."

package/data/harnesses/apollo/skills/design/data/voices/quiet-concierge.md

@@ -0,0 +1,29 @@
+---
+id: quiet-concierge
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Shopify Polaris content fundamentals (polaris-react.shopify.com — verb-first directness, plain language, 'remove until it breaks') and Atlassian voice & tone (atlassian.design — say it once, then get out of the way)."
+license: open
+---
+# Voice: quiet-concierge
+
+**Feel:** Understated and precise — says the necessary thing once, then steps back.
+
+Short-to-medium declarative sentences, verb-first for any instruction ("Add," "Move," "Archive"). Warmth comes from precision, not adjectives — no exclamation points, no stacked modifiers, no filler words ("just," "simply," "easily"). Numbers render as digits even under ten, to keep the eye moving. Contractions are allowed ("it's," "can't") to keep the register human. If a sentence can be cut without losing meaning, cut it.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** plain, verb-first, no ornament
+- **error:** flat statement of what happened, then the fix — no apology
+- **success:** states the fact and stops there
+- **destructive confirmation:** names exactly what's lost, in the same even register — precision is the only warning
+
+## Examples
+
+- **button:** "Add customer"
+- **empty state (heading + motivation):** "No reports yet" / "Reports appear here once your first one is generated."
+- **error:** "The file didn't upload. Check your connection and try again."
+- **tooltip:** "Archives the record without deleting its history."
+- **confirmation:** "Customer added."

package/data/harnesses/apollo/skills/design/data/voices/warm-guide.md

@@ -0,0 +1,29 @@
+---
+id: warm-guide
+class: c2
+sourced: 2026-07-12
+source: "Distilled from the Mailchimp Content Style Guide (styleguide.mailchimp.com) — voice & tone, writing principles, web elements, and grammar & mechanics pages: plainspoken warmth, dry humor, active voice, treats users as capable partners. Mailchimp's style guide content is published under a Creative Commons Attribution-NonCommercial 4.0 International License (CC BY-NC 4.0); reworded and distilled throughout, no verbatim reuse."
+license: licensed
+---
+# Voice: warm-guide
+
+**Feel:** Plainspoken and warm — talks to you like a colleague who respects your time.
+
+Medium sentences in active voice, contractions throughout. One dry aside is permitted per surface, never forced. Numbers under ten are spelled out in body copy, digits in dense UI (tables, counters). Confidence over cheerleading — no "Great job!"; encouragement is implied by clarity, not stated outright. The register never talks down to the reader.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** relaxed, active voice, one idea per sentence
+- **error:** takes ownership ("we couldn't…"), calm next step, no exclamation
+- **success:** quietly confident, still no exclamation
+- **destructive confirmation:** slows down a beat, spells out what's being removed and that it can't be undone
+
+## Examples
+
+- **button:** "Send invoice"
+- **empty state (heading + motivation):** "Nothing here yet" / "Once you add a project, it'll show up in this list."
+- **error:** "We couldn't send that invoice. Check the email address and try again."
+- **tooltip:** "Sends a copy to your own inbox too."
+- **confirmation:** "Invoice sent."

package/data/harnesses/apollo/skills/design/references/compose.md

@@ -6,20 +6,16 @@ Build the app — all surfaces in one continuous context, the chosen package's d
 
 Per the primitives switch recorded in the project's `design.md`:
 
-- **`nurix`** — compose chrome from `@nurix/components`. The chrome recipes (`get_entry`, kind `chrome` — fetch only the recipes for surfaces in the structure doc) carry composition, states, and when-to-use; the component reference folder (`components/`) carries props, imports, and usage — consult the index for what exists, and open the touched category's API reference on need.
+- **`nurix`** — compose chrome from `@nurix/components`. The chrome recipes (`data/chrome/` — read only the recipes for surfaces in the structure doc) carry composition, states, and when-to-use; the component dictionary (`components/`) carries props, imports, and usage across both provenances — consult the index for what exists, and open the touched category's API reference on need.
 - **`native`** — the recipes are *specifications*: anatomy, the eight states, keyboard behavior, token reach — implement them with the incumbent stack's own components. The index's shadcn/fallback columns carry the composition; category API references never load.
 
 Recipes are starting points, not jails: restyle or extend them in place when the package demands it.
 
-## The consult, at your discretion
-
-The composition consult is available here — a whole-app paragraph in, candidate shapes + a component list + rulings out. It is advisory, never binding: you compose. The judgment rule for *when* lives in the router (SKILL.md § The coupled server); the short form: consult on a real knowledge gap or a rework signal, stay local when the canvas is the answer, and `record` every consult and every deviation from its advice. Unavailable is normal — compose locally, record it, continue.
-
 ## Composition rules
 
-- **Every surface starts from a chosen layout blueprint** — `get_entry` the chosen archetype's blueprint (kind `blueprint`); pick the shape reading the brief, record it in one line. Structural variety, not visual variety, is what reads as designed.
+- **Every surface starts from a chosen layout blueprint** (`data/blueprints/<archetype>.md`) — pick the shape reading the brief, record it in one line. Structural variety, not visual variety, is what reads as designed.
 - **Values come from the token artifact** — components consume the emitted custom properties and never invent raw values ([emission.md](emission.md) has the pipe rules). Switching packages must re-skin the whole app.
-- **Positive obligations apply** — `get_entry` the surface's archetype checklist (kind `checklist`); the checklists are ceilings: a sidebar ships with brand block, icons, and user context; a dashboard tile ships with number + comparison + trend + state + door; every surface ships its state matrix.
+- **Positive obligations apply** — load the surface's archetype checklist (`data/checklists/<archetype>.md`); the checklists are ceilings: a sidebar ships with brand block, icons, and user context; a dashboard tile ships with number + comparison + trend + state + door; every surface ships its state matrix.
 - **The register scope holds**: the display face never touches cells, buttons, labels, or form chrome; data numerals run the mono face with `tabular-nums`.
 - **Motion follows the package's §7** and the frequency law: actions performed 100+ times a day, and any keyboard-initiated action, get no animation, ever; panel/drawer motion is interruptible; entrances never `ease-in`.
 - **No ownership jails.** Any file may be edited at any time, including generated ones and library compositions.

package/data/harnesses/apollo/skills/design/references/content.md

@@ -4,7 +4,7 @@ Author the demo data **before composing surfaces**. Data credibility is the sing
 
 ## From the corpus
 
-Fetch the chosen domain's corpus — `search_catalog` (kind `corpus`) to find it, `get_entry` to load it: the body (vocabulary, number-shape recipes, the invariants block) arrives with its `people` and `companies` rosters in one payload.
+Fetch the chosen domain's corpus — `search_catalog` (family `corpus`) to find it, `get_entry` to load it: the body (vocabulary, number-shape recipes, the invariants block) arrives with its `people` and `companies` rosters in one payload.
 
 - Names come from the corpus roster; emails derive from names; roles are domain-correct.
 - Activity strings use the corpus vocabulary — a CRM logs "Intro call with Elena — pricing discussion", never webhook noise.
@@ -14,13 +14,13 @@ Fetch the chosen domain's corpus — `search_catalog` (kind `corpus`) to find it
 
 ## Voice
 
-Fetch the package-bound voice pack — `get_entry` the voice the package's §9 names. All authored strings — buttons, empty states, errors, tooltips, confirmations — speak in that voice, with tone varying by situation per the pack's tone map.
+Load the package-bound voice pack (`data/voices/<id>.md` — the package's §9 names it). All authored strings — buttons, empty states, errors, tooltips, confirmations — speak in that voice, with tone varying by situation per the pack's tone map.
 
 ## Chart choice
 
-Every data-bearing surface consults the chart-selection engine — **one graph question per consult**. The census rows the engine evaluates are fetched **once per session** via `get_entry("chart-census")`:
+Every data-bearing surface consults the chart-selection engine — **one graph question per consult**. The census ships beside the engine; nothing is fetched:
 
-1. Author the data signature (the judgment half): the question, measures, dimensions, semantic flags (temporal, parts-form-whole, target-exists, …), constraints — plus the session's `census` rows. Decompose multi-question asks first.
+1. Author the data signature (the judgment half): the question, measures, dimensions, semantic flags (temporal, parts-form-whole, target-exists, …), constraints. Decompose multi-question asks first.
 2. Run `node scripts/select-chart.mjs <signature.json>` and read the typed output: admissible set, eliminations with reason codes, ranking, recommendation, or a refusal code.
 3. **Honor refusals** — a refusal means the question isn't chartable as posed (often: it's a table). Never invent a measure to force a chart.
 4. `record` the pick in one line. Taking a non-recommended admissible option needs a reason on that line; taking an eliminated option is out of contract.

package/data/harnesses/apollo/skills/design/references/existing-apps.md

@@ -4,7 +4,7 @@ The same machinery runs on existing UIs, under a preservation contract.
 
 ## Judge — a user-invoked service
 
-A critique of an existing UI against the brief, the project's `design.md`, the archetype checklists, and the project's taste profile (`get_project`), producing a **severity-ranked (never scored) report**. Judge is a service the user asks for — never a self-check the skill runs on its own output. Read the actual rendered state (screenshots the user provides, or captures the user asks for); refuse to critique from source alone when the ask is "does it look right", and never imagine what unrendered code looks like. Each finding: severity, the on-screen element, what's wrong, the exact fix.
+A critique of an existing UI against the brief, the project's `design.md`, the archetype checklists, and the workspace's taste profile (`get_preferences`), producing a **severity-ranked (never scored) report**. Judge is a service the user asks for — never a self-check the skill runs on its own output. Read the actual rendered state (screenshots the user provides, or captures the user asks for); refuse to critique from source alone when the ask is "does it look right", and never imagine what unrendered code looks like. Each finding: severity, the on-screen element, what's wrong, the exact fix.
 
 ## Improve — judge + the fix pass
 

package/data/harnesses/apollo/skills/design/references/foundations.md

@@ -0,0 +1,57 @@
+# Foundations — the brief fixed doctrine
+
+Cross-cutting decisions every build makes once, stated at the length they deserve and no longer (the obviousness rule: what competent intelligence already knows gets nothing). Load the touched entry at the step that decides it, never the file whole.
+
+## The five status palettes
+
+Pick **one** per project at intake and hold it everywhere — status colors are semantics, not decoration, and deltas color by *meaning* (down is green when down is good):
+
+| Palette | success | warning | danger | info | neutral | Feel |
+| --- | --- | --- | --- | --- | --- | --- |
+| `signal` | `oklch(0.64 0.15 150)` | `oklch(0.75 0.15 80)` | `oklch(0.58 0.20 25)` | `oklch(0.60 0.14 250)` | `oklch(0.65 0.02 260)` | the default — clear, saturated, unmistakable |
+| `muted-pro` | `oklch(0.60 0.09 155)` | `oklch(0.68 0.10 75)` | `oklch(0.55 0.13 25)` | `oklch(0.58 0.08 250)` | `oklch(0.62 0.015 260)` | desaturated for dense dashboards — readable without shouting |
+| `warm-ledger` | `oklch(0.62 0.11 140)` | `oklch(0.70 0.13 60)` | `oklch(0.56 0.17 30)` | `oklch(0.60 0.10 230)` | `oklch(0.64 0.02 80)` | warm-neutral products (finance, ops review) |
+| `cool-console` | `oklch(0.66 0.12 165)` | `oklch(0.74 0.12 85)` | `oklch(0.60 0.18 15)` | `oklch(0.62 0.12 265)` | `oklch(0.66 0.02 250)` | cool/dark consoles — holds up on deep backgrounds |
+| `high-contrast` | `oklch(0.55 0.17 150)` | `oklch(0.60 0.16 70)` | `oklch(0.50 0.21 27)` | `oklch(0.50 0.16 255)` | `oklch(0.50 0.02 260)` | accessibility-first; every value ≥4.5:1 on white |
+
+Each value is the light-theme anchor; derive the dark-theme sibling by raising lightness ~0.08 and trimming chroma ~0.02. Severity ladders (P0–P3 and kin) map onto danger → warning → info → neutral, never onto new hues.
+
+## Data-viz palettes
+
+No database — three constraints, values yours: **categorical** series need distinguishable hues that survive colorblind simulation (rotate hue ≥40° apart, vary lightness too, ≤8 series then facet); **sequential** ramps run light→dark in one hue for magnitude; **diverging** ramps put two hues around a *meaningful* zero, neutral at the middle. Validate every ramp in both themes; charts consume package tokens, never raw hex.
+
+## Number, date, unit formatting
+
+Tabular figures in tables and KPIs; thousands separators; unit or currency attached to the number; consistent decimals per column; large values truncate meaningfully (`1.2M`, never `1,200,000` in a tile); timestamps show relative when recent and absolute on hover; timezones explicit anywhere ambiguity costs money.
+
+## Spacing & density
+
+The 2/4/6/8 scale, period. Operator surfaces default **compact** (data rows 32–36px) with a comfortable mode only when `product.md` says reading, not scanning. Density is a per-project decision made once, not a per-surface mood.
+
+## Radius & stroke
+
+Radius is identity — sharp (0–2px), soft (4–6px), or round (10px+) — chosen by the package and applied consistently; mixing radii on one surface reads as templated. One border weight per surface; elevation *or* borders separate layers, never both at full strength.
+
+## Loading, skeleton, progress
+
+Skeletons for layout-known loads, spinners only for unknowable ones, optimistic updates for high-frequency mutations with undo. Skeletons mirror the real layout's bones (no generic gray blocks). Nothing pulses faster than 1.2s.
+
+## Empty states
+
+The three empties (first-use, no-results, cleared-filter) each say what happened and what to do next, in the project voice. Art direction follows the package's restraint: an icon or nothing for dense tools; illustration only where the package's feel says warm. Never a bare "No data".
+
+## Keyboard
+
+The operator vocabulary: `⌘K` command palette, `j/k` traversal where lists dominate, `esc` closes the topmost layer only, `enter` commits, focus visible always. Declare shortcuts in a discoverable surface (palette footer or `?` overlay).
+
+## Dark mode physics
+
+Elevation becomes lightness (surfaces lighten as they rise — shadows barely read); desaturate fills ~15%; never pure black (`oklch(0.13–0.18 …)` floors); borders drop to low-alpha white; charts re-derive from dark-theme tokens, never inherit light values.
+
+## Code, log, terminal surfaces
+
+Mono face with `tabular-nums`; a shiki theme paired to the package (dark identity → dark code surface even in light theme is legitimate); log levels use the status palette; wrap off by default with horizontal scroll.
+
+## Polish
+
+Focus rings on-brand (2px, offset, the accent — never browser default blue on a styled app); selection color derived from the accent at low alpha; scrollbars styled thin on dense panes; cursor changes only where affordance is real.