sheleg-design-skill 1.50.0 → 1.50.2

package/CHANGELOG.md

@@ -6,6 +6,27 @@ follow [SemVer](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [1.50.2] - 2026-08-26
+
+### Router carriers and shared guard provenance
+
+The compact description again carries `hero`, `style pack` and `красивее`,
+the phrases the umbrella router actually matches. The eval and social-preview
+validators now identify their umbrella-owned shared mechanisms.
+
+## [1.50.1] - 2026-08-26
+
+### A catalogue that loads when it is needed
+
+The 35-pack chooser moved from the always-loaded skill body into
+`STYLE_PACK_INDEX.md`. The index remains exhaustive, contract-checked, mirrored
+to Cursor and shipped by both installers; the base skill drops to about 3.9k
+tokens and keeps every routing carrier. The repository also gains a root skill
+card, portable evals, a pinned house-audit CI job, a generated social preview and
+an install-first README viewport. The five catalogue self-test plants now mutate
+the new index rather than silently targeting the old location. No model
+evaluation result is claimed.
+
 ## [1.50.0] - 2026-08-25
 
 ### Onionskin, the thirty-fifth pack — two bases, and everything quiet is an alpha

package/README.md

@@ -5,6 +5,16 @@
 [![license: MIT](https://img.shields.io/badge/license-MIT-blue)](./LICENSE)
 [![site](https://img.shields.io/badge/docs-skills.sshlg.me-8ab0ff)](https://skills.sshlg.me/skills/sheleg-design/)
 
+**Give coding agents a deliberate visual system: style packs, tokens, motion doctrine and a clean Figma seam.**
+
+```bash
+npx skills add ssheleg/sheleg-design-skill
+```
+
+Ask: `Design a calm dark dashboard and map its tokens into the component layer.`
+
+**[Detailed docs →](https://skills.sshlg.me/skills/sheleg-design/)**
+
 **[Docs, and every skill →](https://skills.sshlg.me/)** · [this skill's page](https://skills.sshlg.me/skills/sheleg-design/) · [follow @sshlg93 on X](https://x.com/intent/follow?screen_name=sshlg93)
 
 Loads in **DeepSeek Harness** (`dsh`) with **no plugin to write**: it reads the

package/kits/field-notes/src/styles.css

@@ -250,6 +250,15 @@
    17.0:1 for body ink, 8.3:1 for verify, 5.9:1 for the brand. */
 [data-theme="dark"],
 .dark {
+  /* The dawn hero is a LIGHT-THEME object, and this is measured rather than decided.
+     The reference's own `.dark` block declares 43 tokens and not one of them is a
+     dawn stop — so the gradient has no dark counterpart there either. Left
+     un-redeclared, `--hero-dawn` kept its light ramp and ended on #e9ecdf at 98%
+     meeting the dark field at 100%: a near-white hard edge across two percent of the
+     gradient, which this pack's own Bans forbid. In dark the hero is the flat field.
+     Re-read 2026-08-26 (B-112). */
+  --hero-dawn: var(--bg);
+
   color-scheme: dark;
 
   --bg: #14110e;

package/kits/orchard/src/styles.css

@@ -24,7 +24,14 @@
   --primary: #78934a; /* sage — 3.4:1 on --bg: a FILL and large-text colour */
   --primary-deep: #61783b; /* the text-safe green: 4.9:1 on --bg under --on-primary */
   --primary-light: #aaca73; /* the mark / illustration green */
-  --primary-tint: rgba(120, 147, 74, 0.1); /* quiet rows, hover wash */
+  --primary-tint: rgba(120, 147, 74, 0.1); /* quiet rows and a quiet row's hover */
+  /* MEASURED 2026-08-26 by hovering the reference's own sage control in a browser:
+     the fill does not darken or tint, it INVERTS to a warm cream. A fetch cannot see
+     this and the earlier passes did not. A fill, never text. */
+  --primary-hover: #f9eedc; /* 1.13:1 on --bg */
+  /* MEASURED the same pass — the hero slab's fill, one element, 892px tall against a
+     900px viewport. A fill, never text. */
+  --surface-warm: #f7ecdc; /* 1.15:1 on --bg */
 
   /* ---- The one action colour ------------------------------------------- */
   --cta: #fa7241; /* candy orange — 2.8:1 on --bg: a fill only, never text */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sheleg-design-skill",
-  "version": "1.50.0",
+  "version": "1.50.2",
   "description": "Design taste as an installable agent skill. Cinematic scroll-driven landing pages built on one scroll clock and layered degrade-to-calm motion, a motion doctrine that decides whether to animate before it decides how, three calibration dials, and thirty-five locked style packs with ready-made design tokens — instrument-console, editorial-luxury, workbench, briefing-room, atrium, orchard, outrank, babylove, patchbay, nameplate, field-notes, cyclorama, showroom, blueprint, prism, maquette, scoreboard, datasheet, manpage, pigeonhole, roster, ora, tenor, paperclip, ledger, router, daylight, notation, almanac, vitrine, proscenium, awning, bulletin, rimlight and onionskin. Colour, slop and fork-reciprocity gates run as scripts, not opinions. Works with Cursor, Claude Code and any agent that reads a SKILL.md.",
   "bin": {
     "sheleg-design-skill": "bin/cli.js"

package/plugins/sheleg-design/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "sheleg-design",
   "displayName": "SHELEG Design",
   "description": "SHELEG Design methodology: cinematic scroll-driven landing pages (single scroll clock, layered degrade-to-calm motion, WebGL particle formations), a motion doctrine that decides whether to animate before it decides how, and thirty-five pluggable visual style packs — instrument-console (dark console), editorial-luxury (warm editorial), workbench (light/dark product UI for dashboards and tools), briefing-room (dark 16:9 deck), atrium (warm consumer health), orchard, outrank, babylove (friendly consumer biotech), patchbay (a dark live schematic: one mint-cyan, 8% hairlines and no shadow, and an architecture diagram whose cords carry SMIL particles), field-notes (warm paper for dev tools sold on auditability), cyclorama (a pastel field on a 32s cycle), showroom (the product as the exhibit), blueprint (a drawing sheet, zero radius), prism (one iridescent wash over mono body), maquette (cream axonometric models on a dark table), scoreboard (warm paper, pixel numerals, a dark ledger of results), datasheet (an off-white spec sheet whose live instrument goes dark when it detects the reader is hiding), manpage (a developer landing page set in the reader's own system monospace on cream paper, with coral label chips that are real headings and a dark code frame as the argument), pigeonhole (a white sorting wall whose nine pastel categories are a filing scheme rather than a mood, each a two-layer chip whose label word is mandatory), roster (a white field in a faint grid of squares whose argument is other people's marks — client logotypes in pill-labelled industry columns, an engine's wordmark inside the headline — where the proof is a name rather than a number), ora (a warm coal field with cream ink and no third hue — the accent is the inverted field — a serif carrying every human sentence over a monospace carrying every machine fact, a terminal surface cut below the page, and a six-step verdict ramp, for products whose output is a machine's verdict about the reader), tenor (warm paper with zero radius and zero shadow, one hairline weight, an orange that exists only on hover and on focus, a sans tracked negative against a mono tracked positive, display at a line-height below one in an eight-to-twelve-character measure, and product proof delivered as silent looping video, for products arguing that a new kind of thing must be managed like an existing organisation), paperclip (neutral coal with no functional colour at all — every control monochrome and elevation made of hairlines, with the whole chromatic budget spent on a curtain of gradient capsules and twelve gradient section badges that cannot be clicked — for products that ask a person to run something that runs itself: agent teams, autonomous back-office, schedulers and budget-governed compute), ledger (warm cream paper ruled by a hairline at 12% ink and no shadow on any card, radius 15 nested concentrically, an ink primary button and a terracotta accent that never fills a control — it labels, as a 10px monospace uppercase kicker — with a seal on every card stating how its number is known, for the console of a product that answers questions about data: AI analysts, BI surfaces, query workspaces), router (a near-white field with a trace of blue and white cards standing on it, hairline seams instead of shadows anywhere, body at 14px and weight 450, and a status triplet in which the colour you paint with is not the colour you write with, for product consoles and the landing pages that have to look like them), daylight (a cool near-white portal field with generous radii and one very large soft shadow spent on a single object per screen, for client portals), notation (a near-white page drawn entirely in hairlines with a light serif over a monospace, no bold anywhere and an ink primary, for developer products sold on restraint), almanac (oatmeal paper with 2px seams and no 1px anywhere, a display set below a line-height of one, and mono tags notched through drawn boxes, for pages that assert a category), vitrine (a white hairline field with a serif display, an ink primary and one framed record carrying the evidence, for the front door of a product sold on trust). Ships the sheleg-design skill, the architecture reference, the motion doctrine, the Figma and Claude Design bridges, AI-surface patterns, style packs with ready-made token CSS, and the /sheleg-design command, and awning (a white forecourt where the accent is black and no hue reaches the chrome at all, a pill whose radius is a declared component token, one variable grotesque at 420/550 with no 700, and a single three-layer shadow, for commerce and platform front doors), and proscenium (a white field carrying two cool acts and one deep indigo act at the middle, an electric violet filling a control that stays nearly square at 4px against cards at 16, one family at nine weights, and a framed product panel the fold cuts off, for product-led marketing front doors whose argument is a demonstration), and bulletin (warm cream paper cut by flat pastel bands, every card and control a 1px ink outline standing on a hard zero-blur ink offset it travels into when pressed, a display face at 800 inside controls and 700 in the headline, and no tracking at any size, for front doors whose argument is breadth), and nameplate (a cool near-white slab under a page that is square on 87% of its elements, where the one round shape is reserved for a white 1px-bordered pill carrying somebody else's publication name as type, one family with the body at weight 500, and two uppercase registers tracked 0.06em and 0.175em, for pages whose argument is that named third parties will vouch for you: press placement, trust marks, certification and review aggregation), and rimlight (a white field with a cool grey act separator and one near-black act, a grotesque for every sentence and a monospace for every piece of chrome, square on 84% of its elements and tracked negative at every size, whose only elevation is a sixteen-layer coloured light rig — six layers lit and ten held at alpha 0, thrown from below-left — for a studio's own front door and the pages that sell what it makes), and onionskin (a white technical sheet at 96.5% zero radius — the squarest page in the library — where two bases do all the work and everything quiet is one of them at an alpha: text dims through the ink, structure dims through a navy that is never a word, over a dot grid with dashed hairlines and three faces at an 11px working size, for developer and AI infrastructure whose front page is a working document).",
-  "version": "1.50.0",
+  "version": "1.50.2",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/sheleg-design/skills/sheleg-design/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: sheleg-design
-description: Use when deciding how something LOOKS or MOVES. Cinematic scroll-driven landing pages and heroes — particle/WebGL backgrounds, scroll-linked animation, parallax, scrubbed sections — or when one feels busy or its motion drifts. Product UI through its style packs — dashboards, admin panels, internal tools, mobile screens, chat and agent interfaces. Design tokens, light/dark themes, palettes and colours, typography and fonts. Triggers - "design a landing" / "дизайн лендинга", "build a landing page" / "сделай лендинг", "scroll animation" / "скролл-анимация", "dashboard style" / "стиль дашборда", "design tokens" / "дизайн-токены", "light/dark theme" / "светлая/тёмная тема", "figma variables" / "переменные фигмы, фигма в код", "mobile screen" / "мобильный экран", "palette" / "палитра", "colors" / "цвета", "typography" / "типографика", "font" / "шрифт", "how it looks" / "выглядит", "make it prettier" / "красиво, красивее", "visual reference" / "визуальные референсы", "investor deck" / "презентация".
+description: Use when deciding how something LOOKS or MOVES — cinematic landing pages and hero sections, particle/WebGL backgrounds, scroll-linked or scrubbed motion, layers that drift, dashboards, admin or internal tools, mobile screens, chat or agent interfaces, tokens, themes, palettes, typography and the Figma border. Triggers include "design a landing" / "дизайн лендинга", "build a landing page" / "сделай лендинг", "scroll animation" / "скролл-анимация", "dashboard style" / "стиль дашборда", "design tokens, style pack" / "дизайн-токены", "light/dark theme" / "светлая/тёмная тема", "figma variables" / "переменные фигмы, фигма в код", "mobile screen" / "мобильный экран", "palette, colors" / "палитра, цвета", "typography, font" / "типографика, шрифт", "how it looks, make it prettier" / "выглядит, красиво, красивее", "visual reference" / "визуальные референсы", "investor deck" / "презентация". Not for structure, copy or backend behavior.
 license: MIT
 metadata:
-  version: 1.50.0
+  version: 1.50.2
 ---
 
 # SHELEG Design
@@ -60,80 +60,22 @@ the style-pack half and nothing else.
 
 ## Style packs
 
-The motion methodology is style-agnostic; the visual identity comes from a style
-pack in [`styles/`](./styles/). Each pack file opens with its own full description —
-this table is for choosing, not for reading instead of the pack:
-
-| Pack | Look | Choose for |
-|---|---|---|
-| [`instrument-console`](./styles/instrument-console.md) | near-black aerospace console | technical / systems / infra · **core contract** |
-| [`editorial-luxury`](./styles/editorial-luxury.md) | cream and espresso ink | editorial / research / premium B2B · **core contract** |
-| [`workbench`](./styles/workbench.md) | quiet light/dark product UI | dashboards / admin / internal & dev tools (standalone) · **core contract** |
-| [`briefing-room`](./styles/briefing-room.md) | dark 16:9 deck | investor & board decks, briefings, talks as a page (standalone) · **core contract** |
-| [`atrium`](./styles/atrium.md) | cream daylight | consumer health, longevity, wellness, high-trust DTC |
-| [`babylove`](./styles/babylove.md) | white + one orange | the same job answered with **seven tokens** — SEO/AI-visibility SaaS on Tailwind defaults, long time-to-value, first-class disconnected states · **widened** |
-| [`patchbay`](./styles/patchbay.md) | near-black + one mint-cyan | a **live schematic** — 8% hairlines and no shadow, and an architecture diagram whose cords carry SMIL particles on a 2–3.5s clock under light layers on an 8.5–11s one; for engines, buses, pipelines and open-source front doors · **widened** |
-| [`nameplate`](./styles/nameplate.md) | cool near-white slab + one coral ramp | **square on 87% of its elements** — 1,091 of 1,251 measured — with the one round shape reserved for a white 1px-bordered pill carrying somebody else's publication name as type; one family with the body at weight 500, two uppercase registers tracked 0.06em and 0.175em; for pages whose argument is that named third parties will vouch for you — press placement, trust marks, certification, review aggregation (standalone) · **widened** |
-| [`rimlight`](./styles/rimlight.md) | white + one blue + coloured light | **elevation made of light rather than shadow** — a sixteen-layer rig, six lit and ten held at alpha 0, on one control per viewport; a monospace carrying every label and button against a grotesque carrying every sentence, no bold anywhere, and one near-black act; for a studio's front door and its service and case-study pages (standalone) · **widened** |
-| [`onionskin`](./styles/onionskin.md) | white sheet + one blue, **96.5% square** | **two bases and everything quiet is an alpha of one** — text dims through the ink, structure through a navy that is never a word, so the pack has no grey ramp at all; a dot grid, dashed hairlines, three faces and an 11px working size; for developer and AI infrastructure whose front page is a working document (standalone) · **widened** |
-| [`outrank`](./styles/outrank.md) | white + one violet | a **marketing page and a working tool in one brand** — SEO/growth SaaS, agent-run back-office, anything shipping a landing and a dashboard together · **widened** |
-| [`orchard`](./styles/orchard.md) | warm oat slabs | friendly consumer biotech, DTC wellness, kits & supplements · **core contract** |
-| [`field-notes`](./styles/field-notes.md) | green-cast paper ruled by hairlines | open-source & developer tools sold on auditability (standalone) |
-| [`showroom`](./styles/showroom.md) | white gallery | product-led companies whose best argument is the app on screen |
-| [`blueprint`](./styles/blueprint.md) | white stock | infrastructure sold on precision — vector search, storage, query engines |
-| [`prism`](./styles/prism.md) | iridescent wash with a hard edge | an OSS infrastructure project's front door, where step one is a command |
-| [`maquette`](./styles/maquette.md) | near-black table | enterprise data infrastructure sold to an architecture buyer |
-| [`cyclorama`](./styles/cyclorama.md) | pastel field on a 32s loop | enterprise AI transformation and applied-AI consultancies |
-| [`scoreboard`](./styles/scoreboard.md) | warm paper | products whose argument is an accumulating number — growth, ads, SEO |
-| [`datasheet`](./styles/datasheet.md) | off-white spec sheet | B2B SaaS whose product is a verdict about the visitor, request or device — fraud, bot and device intelligence, identity, API products |
-| [`manpage`](./styles/manpage.md) | cream paper | developer products whose buyer reads code — APIs, SDKs, CLIs, MCP servers, developer infrastructure |
-| [`pigeonhole`](./styles/pigeonhole.md) | white field | products that file the reader's incoming mess into named categories — email triage, ticket routing, digests, organisers, CRM inboxes |
-| [`roster`](./styles/roster.md) | white field in a faint square grid | products whose argument is **who already carries them** — AI-search visibility, SEO and content platforms, agencies, marketplaces |
-| [`ora`](./styles/ora.md) | warm coal field | products whose output is **a machine's verdict about the reader** — agent-readiness and crawlability scores, SEO/AEO audits, agent-run traces, MCP and protocol surfaces · **dark by default** (standalone) |
-| [`tenor`](./styles/tenor.md) | warm paper | products arguing a **management thesis** — AI-workforce and agent-operations platforms, autonomous back-office, revenue and sales operations, sold to the director who will have to manage it (standalone) |
-| [`ledger`](./styles/ledger.md) | warm cream paper ruled by a hairline at 12% ink — no shadow on any card — radius 15 nested concentrically | the console of a product that answers questions **about data** — AI analysts, BI surfaces, query workspaces, agents that read a warehouse and write back a figure (standalone) |
-| [`paperclip`](./styles/paperclip.md) | neutral coal with **no functional colour at all** — every control monochrome | products that ask a person to **run something that runs itself** — agent teams and orchestrators, autonomous back-office, schedulers, job runners, budget-governed compute (standalone) |
-| [`awning`](./styles/awning.md) | white forecourt where **the accent is black** and no hue reaches the chrome at all; a pill whose radius is a declared component token | commerce and platform front doors — the surface that sells a system other businesses will run their storefront, payroll, billing or logistics on (standalone) · **core contract** |
-| [`router`](./styles/router.md) | near-white field with a trace of blue, white cards standing on it, **hairline seams instead of shadows anywhere** — body at 14px and weight 450 | **product consoles and the pages that have to look like them** — dashboards, admin and developer platforms, billing and usage surfaces, and a landing page whose argument is an inventory rather than a promise (standalone) |
-| [`daylight`](./styles/daylight.md) | cool near-white portal field with generous radii and **one very large soft shadow spent on a single object per screen** | **client-facing portals and the pages that sell them** — onboarding, workspaces a customer logs into, service dashboards, scheduling and billing (standalone) |
-| [`notation`](./styles/notation.md) | near-white page drawn **entirely in hairlines**, radii of 2 and 4px, a slab serif at weight 300 against a monospace, **no bold anywhere** | **developer and technical products sold on restraint** — open source front pages, workspaces for people who dislike being sold to, documentation homes (standalone) |
-| [`almanac`](./styles/almanac.md) | **oatmeal paper rather than white**, seams at 2px with **no 1px anywhere**, a display set below a line-height of one, mono tags notched through drawn boxes | **pages that assert a category** — a manifesto, a company saying what this kind of thing is, a product whose argument is editorial rather than functional (standalone) |
-| [`vitrine`](./styles/vitrine.md) | white field drawn **entirely in hairlines**, a serif display over a sans body, an ink primary, and one framed record with a 1px inset highlight | **the front door of a product sold on trust** — B2B software under evaluation, security and compliance surfaces, specification and comparison pages (standalone) |
-| [`proscenium`](./styles/proscenium.md) | white field carrying two cool acts and **one deep indigo act at the middle**, an electric violet filling a control that stays nearly square at 4px against cards at 16, one family at nine weights, and a framed product panel the fold cuts off | **product-led marketing front doors whose argument is a demonstration** — SaaS home pages, launch and tour pages, any page with six or more acts that needs a repeated beat (standalone) |
-| [`bulletin`](./styles/bulletin.md) | warm cream paper cut by flat pastel bands, every card and control a 1px ink outline standing on a **hard zero-blur ink offset it travels into when pressed**, a display face at 800 inside controls and 700 in the headline, and **no tracking at any size** | **front doors whose argument is breadth** — a tool doing many things across many channels for many clients, sold cheerfully to a small team or an agency: social and content platforms, scheduling and inbox products, all-in-one SMB SaaS (standalone) |
-
-**A materialized kit answers part of what a core pack leaves out.** `npx
-sheleg-design-skill --kit <pack>` produces `src/styles.css`, whose component half is
-authored CSS for the states a core pack declines to specify — `:hover`,
-`:focus-visible`, `:disabled`, selected. It does not ship with this skill, so an agent
-reading only this bundle will invent them. **A kit exists for every pack, not only
-the core ones** — fetch it whenever you are building components, and treat any
-difference between kit and pack as a defect in one of them rather than a choice.
-For a widened pack the kit and the pack's `## Components` must agree; for a core
-pack the kit is the only answer either of them gives.
-
-**Six of the thirty-five are on the core contract, and it changes what you get.**
-A pack marked **core contract** does not specify `## Components`, `## Hero`,
-`## Responsive` or `## Signature element` — so per-component states, the
-opening viewport and its line ceiling, the collapse rules, and the single
-element the page is remembered by are **yours to decide**, and you say so out
-loud when you do. The other twenty-nine answer all four. This asymmetry is the one
-thing about the library most likely to make you invent a value and believe you
-read it: what a core pack *does* state is measured to two decimals, and that
-precision is not evidence about the half it leaves silent. Each pack declares
-its own level on a `Contract:` line above its Register.
-
-Read the chosen pack in full before styling anything — it supplies the
-palette, type, texture, motion-token values, signature motifs, and bans.
-Each pack ships a ready-made token layer in `styles/tokens/<pack>.css` —
-copy that file verbatim instead of transcribing tables. For a new style,
-copy [`styles/STYLE_PACK_TEMPLATE.md`](./styles/STYLE_PACK_TEMPLATE.md) and
-keep every heading — Register / Palette / Type / Texture & surface /
-Components / Hero / Responsive / Motion tokens / Signature motifs / Signature
-element / Motion flavor (cinematic packs only) / Micro-interactions / Bans /
-Gotchas — then author its `tokens/<pack>.css` in the same change; never invent
-token values ad hoc.
+The visual identity comes from a style pack. Before choosing one, read
+[the style-pack index](./STYLE_PACK_INDEX.md); then read the chosen pack in full
+and copy its token layer from `styles/tokens/<pack>.css`. Do not transcribe token
+tables or infer values from screenshots.
 
+A materialized kit supplies component states:
+
+```bash
+npx sheleg-design-skill --kit <pack>
+```
+
+The generated `src/styles.css` is authoritative for states a core pack leaves
+open. A widened pack's kit and `## Components` section must agree. To author a
+pack, start from
+[`styles/STYLE_PACK_TEMPLATE.md`](./styles/STYLE_PACK_TEMPLATE.md) and ship its
+token file in the same change.
 ## Calibration — three dials
 
 A pack answers *which register*. It does not answer *how far*. Two landing

package/plugins/sheleg-design/skills/sheleg-design/STYLE_PACK_INDEX.md

@@ -0,0 +1,67 @@
+# Style-pack index
+
+Load this file only when selecting or authoring a visual system. The pack file,
+not this index, is authoritative for tokens, components, responsive behavior,
+motion and bans.
+
+## Defaults
+
+- Product UI with no stronger signal: [workbench](./styles/workbench.md).
+- Marketing page with no stronger signal: [showroom](./styles/showroom.md).
+- Presentation or board deck: [briefing-room](./styles/briefing-room.md).
+- Cinematic systems or infrastructure page: [instrument-console](./styles/instrument-console.md).
+
+**Six of the thirty-five are on the core contract.
+The other twenty-nine answer all four widened sections.** A pack marked **core contract** leaves component
+states, hero, responsive rules and the signature element open. Generate its kit
+before building components.
+
+## Catalogue
+
+| Pack | Register | Good fit |
+|---|---|---|
+| [`instrument-console`](./styles/instrument-console.md) | near-black aerospace console | technical systems and infrastructure · **core contract** |
+| [`editorial-luxury`](./styles/editorial-luxury.md) | cream and espresso | editorial, research, premium B2B · **core contract** |
+| [`workbench`](./styles/workbench.md) | quiet light/dark UI | dashboards, admin, internal tools · (standalone) · **core contract** |
+| [`briefing-room`](./styles/briefing-room.md) | dark 16:9 deck | investor and board presentations · (standalone) · **core contract** |
+| [`atrium`](./styles/atrium.md) | cream daylight | consumer health and high-trust DTC |
+| [`babylove`](./styles/babylove.md) | white with orange | SEO SaaS, long time-to-value, disconnected states |
+| [`patchbay`](./styles/patchbay.md) | black with mint-cyan | engines, buses, pipelines, OSS front doors |
+| [`nameplate`](./styles/nameplate.md) | cool slab with coral | press, certification and third-party trust · (standalone) |
+| [`rimlight`](./styles/rimlight.md) | white with blue light | studios, services and case studies · (standalone) |
+| [`onionskin`](./styles/onionskin.md) | white working sheet | developer and AI infrastructure · (standalone) |
+| [`outrank`](./styles/outrank.md) | white with violet | one brand across marketing and product |
+| [`orchard`](./styles/orchard.md) | warm oat slabs | friendly biotech and wellness · **core contract** |
+| [`field-notes`](./styles/field-notes.md) | ruled green paper | auditable open-source developer tools · (standalone) |
+| [`showroom`](./styles/showroom.md) | white gallery | product-led companies selling the app |
+| [`blueprint`](./styles/blueprint.md) | white technical stock | vector, storage and query infrastructure |
+| [`prism`](./styles/prism.md) | iridescent hard edge | command-first OSS infrastructure |
+| [`maquette`](./styles/maquette.md) | near-black table | enterprise data infrastructure |
+| [`cyclorama`](./styles/cyclorama.md) | looping pastel field | applied-AI consultancies |
+| [`scoreboard`](./styles/scoreboard.md) | warm paper | growth, ads and accumulating metrics |
+| [`datasheet`](./styles/datasheet.md) | off-white specification | fraud, identity and device intelligence |
+| [`manpage`](./styles/manpage.md) | cream manual | APIs, SDKs, CLIs and MCP servers |
+| [`pigeonhole`](./styles/pigeonhole.md) | filed white field | inbox, ticket and CRM triage |
+| [`roster`](./styles/roster.md) | faint square grid | platforms sold through who uses them |
+| [`ora`](./styles/ora.md) | warm coal | machine verdicts, audits and protocol traces · (standalone) |
+| [`tenor`](./styles/tenor.md) | warm management paper | agent operations and autonomous back office · (standalone) |
+| [`ledger`](./styles/ledger.md) | cream ruled console | analysts, BI and warehouse agents · (standalone) |
+| [`paperclip`](./styles/paperclip.md) | monochrome coal | orchestrators, schedulers and job runners · (standalone) |
+| [`awning`](./styles/awning.md) | white commerce forecourt | storefront, payroll and billing platforms · (standalone) · **core contract** |
+| [`router`](./styles/router.md) | pale console with hairlines | dashboard, billing and inventory surfaces · (standalone) |
+| [`daylight`](./styles/daylight.md) | bright portal with one shadow | client onboarding and service portals · (standalone) |
+| [`notation`](./styles/notation.md) | restrained technical hairlines | OSS, docs and developer workspaces · (standalone) |
+| [`almanac`](./styles/almanac.md) | oatmeal editorial paper | manifestos and category-defining pages · (standalone) |
+| [`vitrine`](./styles/vitrine.md) | serif trust display | evaluated B2B, security and compliance · (standalone) |
+| [`proscenium`](./styles/proscenium.md) | white demo sequence | product tours and launch pages · (standalone) |
+| [`bulletin`](./styles/bulletin.md) | cheerful outlined bands | broad SMB and agency platforms · (standalone) |
+
+## Selection protocol
+
+When candidates overlap, mount both on the same populated page behind
+`?variant=<pack>`; change only the token layer. Pick from real content and
+density, record the decision, then remove the comparison harness. A placeholder
+route cannot expose the difference.
+
+The pack wins on values. The calibration dials in `SKILL.md` win on amount.
+Neither may invent a token the chosen pack does not define.

package/plugins/sheleg-design/skills/sheleg-design/styles/field-notes.md

@@ -125,9 +125,9 @@ thirty overrides. What it changes:
 
 | Token | Dark value | Note |
 |---|---|---|
-| `--bg` / `--surface` | `#14110E` / `#1C1815` | the warm-brown family — **see the Gotchas below, this contradicts the pack's own stated decision** |
-| `--surface-2` / `--surface-3` | `#262019` / `#262019` | **the same value**: the deepest step this table names in light does not exist in dark |
-| `--ink` / `--ink-2` | `#F7F3EC` / `#F7F3EC` | also collapsed — light distinguishes them |
+| `--bg` / `--surface` | `#14110E` / `#1C1815` | the warm-brown family, **measured**: the reference's own `.dark` declares `--background #14110e` and `--card #1c1815` |
+| `--surface-2` / `--surface-3` | `#262019` / `#262019` | **the same value, and faithfully so**: the reference's dark has two steps above the field — `#1c1815` and `#262019` — and no third |
+| `--ink` / `--ink-2` | `#F7F3EC` / `#F7F3EC` | also one value, and also faithful: the reference's dark carries `--foreground` and `--muted-foreground` and nothing between them |
 | `--ink-soft` | `#A89E8F` | 7.1:1 on `--bg` in this theme |
 | `--brand` / `--brand-ink` | `#CF7A52` / `#CF7A52` | the light theme's `--brand-on-dark`, now the brand itself |
 | `--verify` | `#2BC0A8` | 8.3:1 on `--bg` — **safe as text here**, which it is not in light |
@@ -137,8 +137,11 @@ thirty overrides. What it changes:
 **The dawn does not follow.** No `--dawn-*` stop is re-declared in the dark block,
 so `--hero-dawn` still ends `--dawn-7` `#E9ECDF` at 98% and `--bg` at 100% — in
 dark that is near-white meeting `#14110E` across two percent of the gradient,
-which is the hard edge this pack's own Bans forbid. Fixing it is a value decision
-this pack has not made; until it does, **do not ship the hero in dark**.
+which is the hard edge this pack's own Bans forbid. **Settled 2026-08-26**: the
+reference's `.dark` declares no dawn stop of any kind, so the gradient has no dark
+counterpart there either — and the layer now redeclares `--hero-dawn: var(--bg)` in
+dark. **In dark the hero is the flat field**, which is a rule with a measurement
+behind it rather than a hold.
 
 Three rules carry this palette:
 
@@ -469,20 +472,22 @@ first thing to correct when porting this look:
   theme, so UA form controls and scrollbars follow the OS while the page follows
   the class. This token layer sets it **per theme** — the same trap that bit
   `workbench`; never `light dark`.
-- **This pack's stated dark decision and its shipped dark theme disagree, and the
-  decision has not been re-made.** The paragraph below says the forest family is
-  kept; `tokens/field-notes.css:255` ships `--bg: #14110e`, which is the
-  warm-brown it says was set aside. Measured 2026-08-20, and the reference cannot
-  settle it: `graphify.com` serves **no dark theme at all today** — no
-  `[data-theme="dark"]`, no `.dark`, no `prefers-color-scheme`, and none of the
-  thirty dark values appears anywhere in the 488 KB it returns. So the two
-  readings are that the reference dropped its dark mode after 2026-08-04, or that
-  the block was never read off it. **Neither is guessed at here**; see the board.
+- **The dark theme was read off the reference after all, and the prose was what was
+  wrong.** An earlier pass concluded the reference serves no dark mode — measured
+  against the served HTML, where nothing carries the class. Re-read 2026-08-26 against
+  the two stylesheets it loads: `.dark { … }` declares **43 tokens**, and the layer
+  here matches them value for value — `--background #14110e` = `--bg`, `--card
+  #1c1815` = `--surface`, `--secondary/--muted/--accent #262019` = `--surface-2`,
+  `--foreground #f7f3ec` = `--ink`, `--muted-foreground #a89e8f` = `--ink-soft` at
+  7.12:1. So the warm brown is MEASURED, not a slip, and the sentence claiming the
+  forest family was kept in dark is the thing that was false. It is corrected below.
 - **The reference runs three unrelated dark palettes**: a warm-brown `.dark`
   theme (`#14110E`), forest bands on the page (`#072820`), and a navy terminal
-  (`#0B101D`). This pack keeps the forest family, because it is the hero's own
-  gradient and the only one the page argues for; the terminal takes a darker
-  step of the same family. If you port the reference verbatim you inherit three
+  (`#0B101D`). **The forest is the hero's own gradient and belongs to the light
+  theme**; the dark theme takes the reference's `.dark` block, which is the warm
+  brown, and the terminal takes a darker step of the forest family in light. Reading
+  "keeps the forest family" as a claim about the dark theme is what made this pack
+  look self-contradicting for six days. If you port the reference verbatim you inherit three
   systems and no rule for choosing between them.
 - **Its app layer drifts from its page layer.** The reference's `--sidebar-*`
   neutrals are browner than the page's green-cast ones and its sidebar ring is a

package/plugins/sheleg-design/skills/sheleg-design/styles/manpage.md

@@ -395,6 +395,48 @@ mono, `--success` for `GET`, `--info` for `POST`, each on its `-weak` tint at
 Focus: `--focus-color` ring, border `--accent-ink`. Error: border `--danger`, with
 the message in `--danger` **and** an icon.
 
+**Loader — the reference paints none, and this pack's answer is a swap rather
+than a spinner.** Measured 2026-08-26 by rendering the origin at 1440 and at 900:
+the whole page runs **two** perpetual animations and both are 8px round dots at 2s
+`cubic-bezier(0.4, 0, 0.6, 1)` — one green beside *579,406 posts this week*, one
+violet beside *22,271 accounts connected this week*, each sitting above a 200×40
+sparkline tinted to its own dot. Those are the opposite of a loader: a loader says
+the number has not arrived, a liveness dot says the number is still moving. There
+is no spinner, no skeleton and no shimmer anywhere in the render, and the page
+carries zero `aria-live`, zero `role="status"` and zero `aria-busy`. So the rules
+below are this pack's decisions, stated rather than left to the reader — a
+documentation register acquires async surfaces a marketing page never has: a
+playground call, a key being minted, a log tail.
+
+- **A pending control keeps its width.** Everything here is mono, so a pending
+  label is padded to the settled label's cell count and the button never resizes.
+  This is the one register where that is exact rather than approximate.
+- **A waiting region is a skeleton, and the skeleton holds still.** `--surface-2`
+  blocks at the row's own height inside the same `--rule` card at `--r-control`,
+  and no shimmer: the page's entire perpetual budget is two 8px dots, and a
+  shimmer would be the third and by far the largest.
+- **A long-running region reuses the reference's own dot** — 8px, `--success` or
+  `--info`, with its word beside it, and it takes the `aria-live="polite"` the
+  reference omits.
+- **Never a spinner.** Motion flavor here is entry only and Bans calls this the
+  calmest pack in the family; a rotating glyph is perpetual motion carrying a
+  status with no word beside it.
+
+**Empty state — the reference has a surface that could be empty and paints no
+empty variant of it.** Same pass: the only data surfaces are the two sparklines
+and their counters, every list on the page is editorial — a numbered list of
+setup steps — and zero elements name themselves empty, no-results or placeholder.
+So this is a decision too, and it is prose rather than a picture: the same
+`--r-card` card on `--surface` with its `--rule` hairline, one 14px line in
+`--ink` naming what is not there, one in `--ink-soft` saying how to fill it, and
+the **secondary** button where there is an action — never the primary, which
+belongs to the page's one argument. No illustration: the code frame is the only
+image this pack allows itself, and a drawing in a documentation register reads as
+a different product. An emptiness that is a failure rather than a state is not
+this component at all — it carries `--danger`, its word and an icon, exactly as
+the input's error does.
+
+
 ## Hero
 
 The opening viewport, in order:

package/plugins/sheleg-design/skills/sheleg-design/styles/orchard.md

@@ -1,10 +1,11 @@
 # Style pack — Orchard
 
 Origin: **gutgutgoose.com** (2026), a production consumer-biotech site built in
-Framer. Every value below was read off its live computed styles. A warm oat
-field carrying a stack of **rounded slabs**, a sage-green brand, one candy
-orange reserved entirely for the action, a rounded geometric display face, and
-buttons made of light rather than of shadow. It reads the way good packaging
+Framer. Every value below was read off its live computed styles, **with one role
+that the page as served today does not confirm** — the orange, and the Gotchas carry
+the measurement. A warm oat field carrying a stack of **rounded slabs**, a sage-green
+brand, one candy orange the pack reserves for the action, a rounded geometric display
+face, and buttons made of light rather than of shadow. It reads the way good packaging
 does: friendly enough to pick up, precise enough to trust.
 
 Contract: core — this pack does **not** specify `## Components`, `## Hero`,
@@ -179,8 +180,9 @@ to read as a fact.
   sheen, wearing `--shadow-cta` (both inset white hairlines plus the orange
   ambient glow) at pill radius, `16px 24px 14px` padding — the extra top pad is
   what makes the label sit optically centred. Exactly one of these per view.
-  It is the only orange object on the page, which is what makes it unmissable
-  without being loud.
+  Exactly one per view is the pack's rule, and it is a **pack decision rather than
+  a reading of the reference** — see the Gotchas: on the page as served today the
+  orange fills no control at all.
 - **Slabs as sections.** Each section is a rounded rectangle with its own fill:
   oat for explanation, sage for invitation, cacao for emphasis. Adjacent slabs
   never repeat a fill; the field between them is the separator.
@@ -257,6 +259,50 @@ button.
 
 ## Gotchas
 
+**The sage control's hover INVERTS, and a white label does not survive it.** Measured
+2026-08-26 by hovering the reference's own control in a browser — which is the only way
+to see it; a fetch shows nothing. At rest the primary is `--primary` sage `#78934a` at a
+50px radius, 42px tall, `8px 18px`; on hover the fill becomes `--primary-hover`, the warm
+cream `#f9eedc`. **The label must therefore be `--surface-ink` `#3a1b13`, which is 4.51:1
+on the sage and 13.59:1 on the cream — it survives both.** White is 3.46:1 on the sage
+and **1.15:1 on the cream**: a white label on this control is legible at rest, fails AA
+at rest, and *disappears entirely* the moment a pointer touches it.
+
+**The reference ships no focus style and no disabled state.** Both controls compute
+`outline: 1px auto rgb(0, 95, 204)` — the user agent's own ring — and the page carries
+zero `[disabled]` or `[aria-disabled]` elements at any of the three widths. Neither is
+copied here: a pack that inherited a UA focus ring would ship a different ring in every
+browser.
+
+**The secondary control has no hover at all.** Measured: cream `#fffef4` at rest, cream
+on hover, nothing else changes. If you give it one, you are extending the reference
+rather than reading it.
+
+
+**The orange is the pack's decision, not the served page's behaviour, and the
+difference is measured.** Re-read on 2026-08-26 by rendering the reference at 1440×900
+and walking all 1,115 visible elements of 1,223: `#fa7241` appears as a
+`background-color` **0 times**, as `color` **0 times** and as a border colour **0
+times**. It survives on **2 SVG `<path>` fills** — illustration — and inside 18
+gradients. What fills a control there is the sage `#78934a`: the primary action on the
+served page is `background-color: rgb(120, 147, 74)` at a 50px radius, 42px tall.
+
+**Three readings were possible and the render eliminates one of them.** The pill is
+*not* hydrated late — 1,115 elements render and the controls among them carry their
+fills statically. Of the two that remain, neither can be settled: the pack may have
+read a page this site no longer serves (`/pricing`, `/shop` and `/product` all answer
+**404** as of 2026-08-26), or the role may have been assigned to a colour sampled from
+artwork. **The pack is not rewritten on that ambiguity** — `--cta` stays the action
+colour here, because a pack is a design decision and this one is coherent. What
+changes is that it no longer claims to be a measurement of the current page, and the
+claim that the pill *"is the only orange object on the page"* is gone, because on that
+page there are eighteen gradients and two illustration paths carrying the same hue and
+no control carrying it at all.
+
+**If you are matching the reference rather than using the pack**, the action fill you
+will see is `--primary`, and `--cta` will look like an invention. Both readings are
+legitimate; the pack tells you which one it is.
+
 The reference is strong on composition and weak on contrast. All three failures
 below are real, measured, and fixable from inside the palette — treat them as
 the first thing to correct when porting this look:

package/plugins/sheleg-design/skills/sheleg-design/styles/pigeonhole.md

@@ -325,6 +325,55 @@ height, `--ink-faint` treatment. It is the one continuous animation in the pack,
 under reduced motion it is **paused** rather than shortened — see Motion flavor,
 because collapsing its duration would strobe it.
 
+**Loader — the reference paints none, and the budget for one is already spent.**
+Measured 2026-08-26 by rendering the origin at 1440: the page runs **four**
+`marquee` tracks and nothing else perpetual — one row, 112px tall, 36 logos, each
+track 1484px wide at 100s linear, which is `--dur-marquee` and the logo wall
+above. No spinner, no skeleton, no shimmer. The one `aria-live` region on the page
+is an empty invisible `<section>`, the framework's route announcer rather than a
+loader, and it should not be read as one. So:
+
+- **A skeleton is a tint, never a shimmer.** `--surface-2` inside the panel it
+  stands in, at `--radius-panel`, and it holds still. A shimmer would be the
+  page's second continuous animation, and under reduced motion — where the logo
+  wall is **paused** rather than shortened — it would be the only thing still
+  moving, which inverts the rule it stands next to.
+- **A chip's skeleton keeps both layers.** Outer `--radius-chip`, inner
+  `--radius-chip-inner`, and the inner takes the outer's own `--cat-step-150` to
+  `--cat-step-200` pair rather than the light `--cat-step-50` to `--cat-step-100`
+  one, so the shape reads as solid rather than as a chip with a blank label. The
+  1px between the two radii is the inner layer's padding, and a single-layer
+  placeholder therefore resizes the chip when the word lands. A skeleton never
+  borrows a category ramp: a hue that names a category before the category is
+  known is the hue-only chip this pack bans.
+- **A pending primary button keeps its gradient, its `--shadow-cta` and its word,
+  and does not translate.** The −1px belongs to `:hover`, and a control already
+  pressed must not look liftable. The `:disabled` pair is wrong here —
+  `--surface-2` with `--ink-faint` says *cannot be used*, and a pending control is
+  one that is working.
+
+**Empty state — the reference's only depiction of one is a photograph.** Same
+pass: the page ships eleven images wider than 200px, three of them full-width
+product screenshots, and the largest at 1152×703 is captioned *an organized
+inbox*. The product is named for an empty state and the page paints that state as
+a raster screenshot, so there is nothing in markup to read values off — every
+`<ul>` on the page is a pricing feature list and zero elements name themselves
+empty or no-results. This pack's decision, then:
+
+- **An empty state is a panel, not a page.** `--surface`, `--radius-panel`, the
+  `--rule` hairline and `--shadow-card` — the same card as everything else,
+  because the surface is not broken.
+- **One `--size-body-lg` `--weight-emphasis` line naming what is not there, one
+  `--size-body` `--ink-soft` line saying how to fill it, and the primary button.**
+  Never `--ink-faint`, which the token layer confines to a disabled control's
+  label; this prose is live text.
+- **No pastel, with one exception.** A feature card may swap its fill for a
+  category's 50→100 gradient; an empty state may not, because the pastel names a
+  category and an empty surface has none yet. The exception is a surface that IS a
+  category — an empty view of one takes that category's pair and carries the
+  ordinary chip with its word, which is the rule the chip already obeys.
+
+
 ## Hero
 
 The first viewport, at 1440×900, holds exactly this and in this order: the nav,

package/plugins/sheleg-design/skills/sheleg-design/styles/roster.md

@@ -269,6 +269,35 @@ shadow. The chevron rotates 180°.
 `--surface` fill, a `--radius-control` accent CTA at the right, and a 1px `--rule` bottom
 edge that appears on scroll.
 
+**Input — two shapes, and the second lives on a dark panel.** Measured 2026-08-26 by
+rendering the reference and reading its four visible fields.
+
+The *light* one is the hero's URL field: **44px tall, zero radius, 16px**, a transparent
+background and **no border of its own** — it sits inside a bordered wrapper ruled by
+the pack's own `--rule`, which the render resolved to the same `#e5e7eb` the token layer
+carries. `#e5e7eb` measures 1.24:1 on `#ffffff`: a rule rather than a mark.
+Its text is `--ink`, which is 17.93:1 on `--bg`.
+Its placeholder is `--ink-faint`, which WCAG exempts as a placeholder and which this
+pack forbids as live text.
+
+The *dark* one is the closing form's email and URL fields: **52px tall, 12px radius,
+14px, `0 16px` padding**, filled with **white at 8%** and bordered with **white at 15%**
+on the dark panel. The two shapes are not interchangeable — the zero-radius one belongs
+to a field standing on the white sheet, the 12px one to a control on ink.
+
+**Loaders — none, and that is the answer.** The reference runs exactly three perpetual
+animations and none of them is a loader: `ebook-float-primary`, `-secondary` and
+`-tertiary`, at 5.5s, 6.5s and 7.5s, which drift the ebook mockups. There is no async
+surface on the page to wait for. If you build one, the pack's Motion tokens have no
+loader duration to spend, and inventing a shimmer here would be the only perpetual motion
+on a page whose whole budget is entrance, hover and two slow floats.
+
+**Empty states — none, and for the same reason.** Three forms and no data surface: there
+is nothing on this page that can be empty. A product built on this pack that *does* have
+one should take the `--surface-2` band, a `--rule` hairline, body copy at `--ink-soft`
+and no illustration — the page's own vocabulary for a quiet region — but that is an
+extension of the pack rather than a reading of it, and it is marked as one here.
+
 ## Hero
 
 The first viewport at 1440×900 holds, in this order: the sticky nav; the display headline

package/plugins/sheleg-design/skills/sheleg-design/styles/tokens/field-notes.css

@@ -250,6 +250,15 @@
    17.0:1 for body ink, 8.3:1 for verify, 5.9:1 for the brand. */
 [data-theme="dark"],
 .dark {
+  /* The dawn hero is a LIGHT-THEME object, and this is measured rather than decided.
+     The reference's own `.dark` block declares 43 tokens and not one of them is a
+     dawn stop — so the gradient has no dark counterpart there either. Left
+     un-redeclared, `--hero-dawn` kept its light ramp and ended on #e9ecdf at 98%
+     meeting the dark field at 100%: a near-white hard edge across two percent of the
+     gradient, which this pack's own Bans forbid. In dark the hero is the flat field.
+     Re-read 2026-08-26 (B-112). */
+  --hero-dawn: var(--bg);
+
   color-scheme: dark;
 
   --bg: #14110e;

package/plugins/sheleg-design/skills/sheleg-design/styles/tokens/orchard.css

@@ -24,7 +24,14 @@
   --primary: #78934a; /* sage — 3.4:1 on --bg: a FILL and large-text colour */
   --primary-deep: #61783b; /* the text-safe green: 4.9:1 on --bg under --on-primary */
   --primary-light: #aaca73; /* the mark / illustration green */
-  --primary-tint: rgba(120, 147, 74, 0.1); /* quiet rows, hover wash */
+  --primary-tint: rgba(120, 147, 74, 0.1); /* quiet rows and a quiet row's hover */
+  /* MEASURED 2026-08-26 by hovering the reference's own sage control in a browser:
+     the fill does not darken or tint, it INVERTS to a warm cream. A fetch cannot see
+     this and the earlier passes did not. A fill, never text. */
+  --primary-hover: #f9eedc; /* 1.13:1 on --bg */
+  /* MEASURED the same pass — the hero slab's fill, one element, 892px tall against a
+     900px viewport. A fill, never text. */
+  --surface-warm: #f7ecdc; /* 1.15:1 on --bg */
 
   /* ---- The one action colour ------------------------------------------- */
   --cta: #fa7241; /* candy orange — 2.8:1 on --bg: a fill only, never text */