sheleg-design-skill 1.56.0 → 1.58.0

package/CHANGELOG.md

@@ -6,6 +6,157 @@ follow [SemVer](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [1.58.0] - 2026-08-30
+
+### The catalogue stops being the one surface nobody designed, and two blind reads land
+
+**The site is now built from a pack.** The two generators behind
+`ssheleg.github.io/sheleg-design-skill` carried **sixty-seven colour literals**
+between them — a dark-only scheme that appears in no pack, answers no
+`prefers-color-scheme`, and had never been through the contrast gate every pack must
+pass. A library that ships thirty-nine measured token layers and paints its own
+catalogue in an undocumented one is arguing against itself.
+
+`tools/chrome.py` is the shell now: it inlines `styles/tokens/workbench.css`
+**verbatim** and the site's own CSS consumes `var(--…)` and nothing else.
+`workbench` for two checkable reasons — it is the library's stated default for
+product UI, which is what a catalogue is, and it is one of only two packs shipping a
+full `[data-theme="dark"]` twin, which a public page needs. The theme follows the
+pack's own written instruction (*"keep one switch, never two sources of truth"*): a
+`prefers-color-scheme` listener sets `data-theme`, and the two `theme-color` meta
+tags are **derived** from the layer's `--bg` rather than typed. `no_literals()` runs
+on every build and in `npm test`, so this cannot rot back.
+
+The site's links honour the pack rather than override it: `--accent` is declared
+`@role non-text` at 4.30:1, so a link is `--ink` wearing an accent underline, and
+hover thickens the rule instead of recolouring the word.
+
+**The front door had been publishing 39 blank cards.** `tools/gallery.py` parsed the
+pack catalogue out of `SKILL.md` long after that table moved to
+`STYLE_PACK_INDEX.md`. The regex matched nothing, `look` and `for` came back empty
+for **every** pack, and the live site shipped *"Choose for"* followed by silence on
+all thirty-nine — with the JSON-LD `ItemList` descriptions and the `llms.txt`
+entries empty behind it. Nothing failed, because an empty string is a valid string.
+Fixed, and the parse is now asserted: a run that finds no catalogue rows stops
+instead of publishing a catalogue with no prose in it.
+
+### Scenario T37 ran, both branches passed, and cost 29 findings
+
+Written on 2026-08-30 with its debt stated; run the same day once subagents were
+available. Both branches blind against the bundle directory, both correct — `T37a`
+reached `chorus` from a quoted-thread brief, `T37b` **stayed on `surveyor`** from an
+enterprise-tracker brief, which is the failure a positive-only branch cannot detect.
+
+**Twelve of `T37a`'s sixteen findings on `chorus` are fixed here.** The three that
+mattered were invisible to every gate:
+
+- `--on-status` stayed at its root white inside the slab block, putting **white on
+  the mint at 1.32:1** — in the one surface the pack invented the mint for. The
+  comment above that block said it owed "two tokens" while the block changed five.
+  It now re-declares six, and the count is stated.
+- The slab's overrides **inherited into light descendants**: a white card nested in a
+  slab took a white hairline and re-admitted the mint the pack's own Bans forbid on
+  paper. A nested light surface takes its tokens back.
+- The Responsive section's opening sentence contradicted its own table two lines
+  below: *"768 and 1440 differ only in the frame, not in the type"*, against a table
+  giving the display 40px at 768 and 56px at 1440.
+
+Also: `--track-h2-sm` now exists for the narrow section head the Responsive table
+asks for; the Delta chip's "wash" is two real tokens (`--good-weak`,
+`--danger-weak`); the provenance legend names the family it actually uses
+(**PACK DECISION**, and no SELECTED); one ratio was wrong (`--parchment` on `--bg` is
+1.14:1, not 1.15); "a factor of three" was 2.8; the eyebrow was two objects with two
+sizes; three things were called a pill and none of them used `--r-pill`; and the
+slab hook is now the library's own unprefixed `[data-surface="slab"]` — chorus had
+been the only pack you could not A/B by swapping the token layer alone.
+
+**One of `T37b`'s thirteen findings on `surveyor` is fixed here**, because it is an
+accessibility hole with a one-token remedy: `--focus-color` is `--action`, and
+`#0a7269` on the pack's own `--accent` closer panel measures **1.55:1** — under the
+3:1 mark floor, on the surface carrying the final CTA. `[data-surface="accent"]` now
+re-declares the ring to the pack's `--bg` at 3.54:1. The other eight are verified and
+filed as B-137 for the pack's author, per the B-134/B-135 precedent.
+
+**Both branches found the same third-party defect, and neither pack could have
+caught it.** `MOTION_DOCTRINE.md` called `bulletin` at 3 *"the lowest ceiling in the
+library"* — false for four releases, while four packs pin **2**. Corrected, and
+`validate_motion_ceiling_floor()` now recomputes both the minimum and the count from
+the packs' own Register lines; it was watched failing against a planted 3 before it
+went green.
+
+### Ledgers
+
+B-136 closed. B-137 and B-138 opened with the verified remainder. `REQ-CHORUS-3`
+moves off `never`, taking the ledger from two `never` rows to one. The `chorus`
+acceptance record's REQ-10/11/12 are closed against receipts — including the one
+that is only **partly** met and says so: the launcher's pin still names v1.54.0,
+because that repository holds ~2,100 lines of another session's uncommitted work.
+
+## [1.57.0] - 2026-08-30
+
+### The siblings are declared, the maps are derived, the descriptions stop scarring
+
+Five closures from the family audit of 2026-08-29 (SHD-05, SHD-01, SHD-03, SHD-09,
+SHD-11), one release.
+
+**The three sibling skills are declared, and every one has a written absent-branch
+(SHD-05, the audit's HIGH).** `SKILL.md` handed charts to a `dataviz` skill that
+exists on no consumer machine this skill ships to, and asserted `shadcn` /
+`migrate-radix-to-base` "are installed" — a promise this repository has no way to
+keep. Three changes, none of them a removal:
+
+- A `compatibility` front-matter line names all three as optional siblings with
+  in-text fallbacks — the Agent Skills field for environment expectations, spent on
+  the one expectation this skill actually has.
+- The chart handoff is now conditional in both homes: where a `dataviz` skill is
+  installed it consumes the pack as its parameter set, and **where none is
+  installed, the role table in `SURFACE_COMPOSITION.md` IS the chart contract**,
+  applied by hand — which is what that table always was, stated instead of implied.
+- The component-layer section says what absence costs: nothing. `npx shadcn@latest
+  add` does the adding without the skill, and the token mapping binds either way.
+
+**Every long reference now carries a derived `## Contents` list (SHD-01).** The
+authoring rule — a reference over 100 lines carries a map, because that is what a
+partial read sees — held in 2 of 46 qualifying files. Hand-adding 44 lists creates
+44 lists that rot, so the list is **derived**: `scripts/gen_contents.py` writes the
+entries from the file's own `## ` headings (fenced code blocked out), `--write`
+regenerates bundle + mirror + template source together, and
+`validate_contents_lists()` refuses a file whose list is missing *or drifted* —
+including the one pre-existing list whose entries had already wandered from the
+headings they mapped (`MOBILE_SURFACES.md`). A new pack without a Contents list now
+fails the gate with the remedy in the message.
+
+**Both host-facing manifest descriptions are generated, never hand-appended
+(SHD-03).** `plugin.json` and the plugin entry in `marketplace.json` had converged
+to what per-release appending always produces: `patchbay` and `nameplate` glossed
+twice, `deskmate` never glossed, and `chorus` carrying `deskmate`'s orphaned
+parenthesis. Both descriptions are now derived from `STYLE_PACK_INDEX.md`'s
+catalogue — the register and good-fit columns packs are already chosen by — via
+`scripts/gen_manifest_descriptions.py` (`npm run gen-descriptions`), and
+`validate_manifest_descriptions()` refuses a manifest that differs from the
+derivation. The generator also refuses to run when the catalogue and `styles/`
+disagree, so the index parity gate fires first, not silently.
+
+**The deck trigger names the register it owns (SHD-09).** "investor deck" /
+«презентация» was broad enough to catch every presentation request, including the
+`.pptx` files the pptx/pitch-deck neighbours own. Now: *"investor deck as a web
+page" / "веб-презентация"*, with the file-based register explicitly declined in the
+description tail. The T1 carrier word `deck` survives, and the umbrella advertises
+no presentation trigger for this skill, so no routing hook loses a word.
+
+**The layout deviation is recorded where a retrofit would look (SHD-11).**
+References at the skill root and tokens two levels deep predate the layout
+guidance, and every deep link, the `.cursor` byte-mirror and `install.sh`'s file
+list depend on them. CONTRIBUTING.md now records the deviation as deliberate so the
+next standards pass reads a decision instead of an accident.
+
+Gate: 5060 → 5598 checks (the floor moves with it); both new checks watched
+failing against the real tree first — 46 references and 2 manifests red before the
+regeneration, green after — and each ships a planted defect in the self-test. The
+Contents gate's first live catch was the next release's own file: v1.56.0's
+`MOTION_PRODUCTION.md` landed mid-flight without a list, and the rebase gate
+refused it until `npm run gen-contents` wrote one.
+
 ## [1.56.0] - 2026-08-30
 
 ### The render seam — what changes when motion stops being a page

package/kits/chorus/src/Slab.md

@@ -5,8 +5,10 @@ category: Surfaces
 The dark band cut into the paper: `--slab` at `--r-panel`, inset `--slab-inset` (30px,
 measured against the viewport rather than a parent), full width otherwise.
 
-It carries `data-chorus-surface="slab"`, which is what re-declares `--focus-color`,
-`--line` and the three status tokens inside it. That re-declaration is not decoration:
+It carries `data-surface="slab"` — the library's own unprefixed hook, so this pack
+can be A/B'd against any other by swapping the token layer alone — and that
+attribute is what re-declares the six tokens that would otherwise resolve to a
+light-field value on a dark ground. That re-declaration is not decoration:
 the ink focus ring measures 1.00:1 against `--slab` and would vanish on the band that
 carries the closing CTA.
 

package/kits/chorus/src/Slab.tsx

@@ -8,7 +8,7 @@ export interface SlabProps {
 export function Slab({ children, className }: SlabProps) {
   return (
     <section
-      data-chorus-surface="slab"
+      data-surface="slab"
       className={['ch-slab', className].filter(Boolean).join(' ')}
     >
       {children}

package/kits/chorus/src/styles.css

@@ -39,10 +39,16 @@
 
    MEASURED — the literal was computed on the live page or read from an authored
    Framer token that the census confirmed paints.
-   SELECTED — a value the reference ships in another role, taken because a floor
-   forces the move; only the role changes.
    DERIVED — computed from a token here because the reference's own value fails a
    floor. Hue is held; lightness moves and chroma is clipped to gamut.
+   PACK DECISION — a value the reference does not carry at all, so there was
+   nothing to measure. Two of them, and both are named where they sit: the
+   mirrored cut corner, which the reference ships in one direction only, and the
+   state clock, because the reference's controls compute to 0s.
+
+   There is no SELECTED family here. The reference offers no darker step of its own
+   in any hue that fails, so every correction below had to be DERIVED — which is
+   the opposite of `surveyor`, whose whole remedy was its reference's own ladder.
 
    The corrections are in the pack's Gotchas, and there are six. */
 
@@ -150,6 +156,13 @@
   --danger: #d03950;
   --info: #1167f4;
   --on-status: #ffffff; /* 4.84:1 on --good, 4.79:1 on --danger, 4.92:1 on --info */
+  /* The delta chip's ground. The reference paints its rose at two alphas over the
+     field (10% and 15%); the green wash is the same construction at the same
+     alpha, which is a PACK DECISION stated rather than a measurement implied.
+     @role non-text: --good-weak, --danger-weak — a tint under a figure that
+     carries its own solid; nothing is written ON them. */
+  --good-weak: rgba(25, 132, 0, 0.1);
+  --danger-weak: rgba(208, 57, 80, 0.1);
 
   /* ---- Status on the slab: a separate ladder, and the mint lives only here */
   /* MEASURED on the dark wells. The mint is the identity of the reading — 36
@@ -215,7 +228,10 @@
   --focus-w: 2px;
   --focus-offset: 2px;
   --focus-color: var(--ink-strong);
-  --focus-color-on-dark: var(--paper); /* 16.54:1 on --slab */
+  /* It points at the ink token rather than at --paper: a ring on the dark IS ink,
+     and two names for one value is what this file's own coral comment argues
+     against. The ratio it has to clear is the one --on-slab already states. */
+  --focus-color-on-dark: var(--on-slab);
 
   /* ---- Radii: a measured ladder, and one corner that is not there -------- */
   /* MEASURED across the census: 8px on a badge, 10px on a chip and eyebrow, 12px
@@ -240,8 +256,13 @@
   --r-bubble: 24px 0 24px 24px;
   --r-bubble-mirror: 0 24px 24px 24px;
 
-  /* ---- Spacing: a 4-based ladder and a 100px section -------------------- */
-  /* MEASURED. The card's padding is 32px and its internal gap is 32px, and
+  /* ---- Spacing: the measured steps, named by their step number ---------- */
+  /* The suffix is the ladder's INDEX, not the value in quarters — `--space-10`
+     is the tenth step and it is 32px. That is worth stating because the values
+     are the reference's own measured gaps (4, 6, 8, 10, 12, 16, 24, 32, 40, 100)
+     and two of them are not multiples of four, so no arithmetic reading of the
+     name survives contact with the ladder. Read the comment, not the number.
+     MEASURED. The card's padding is 32px and its internal gap is 32px, and
      NEITHER CHANGES at 390 — the card keeps desktop padding on a 350px sheet,
      which is a deliberate property of the reference and is stated in Responsive.
      The section rhythm is 100px at desktop. */
@@ -310,6 +331,9 @@
   --track-display: -0.0625em; /* MEASURED — -3.5px at 56px */
   --track-display-sm: -0.025em; /* MEASURED — -1px at 40px; it RELAXES */
   --track-h2: -0.032em; /* MEASURED — -1.4px at 44px */
+  --track-h2-sm: -0.025em; /* MEASURED — -1px at 34px, the narrow section head.
+     It exists because the Responsive table asks for it: a size step with no
+     tracking token forces the literal this library bans everywhere else. */
   --track-quote: -0.02em; /* MEASURED — -0.48px at 24px */
 
   --weight-body: 400;
@@ -339,11 +363,21 @@
   line-height: var(--lh-body);
 }
 
-/* The slab is a surface, not a theme — the page never inverts. What it does owe
-   is the two tokens that would fail silently on it: the focus ring, which is ink
-   and therefore invisible — #1b181c on #1b181c is 1.00:1 — and the rule ink. */
+/* The slab is a surface, not a theme — the page never inverts. The hook is the
+   library's own `[data-surface]`, unprefixed: every other surface-variant pack in
+   this collection uses that attribute, and the index's selection protocol says to
+   compare candidates by changing the token layer alone. A namespaced hook would
+   have made chorus the one pack you cannot A/B without editing the markup, which
+   is a cost paid by every reader to buy nothing. `.chorus-slab` is kept beside it
+   as an alias, because a class is what a component library reaches for.
+
+   What the block owes is every token that would otherwise resolve to a light-field
+   value on a dark ground. There are SIX, and the count is stated because the first
+   version of this block listed two, changed five, and left the sixth — --on-status
+   — at its root white, which put white on the mint at 1.32:1 inside the one
+   surface the pack invented the mint for. */
 .chorus-slab,
-[data-chorus-surface="slab"] {
+[data-surface="slab"] {
   background-color: var(--slab);
   color: var(--on-slab);
   --focus-color: var(--focus-color-on-dark);
@@ -351,6 +385,24 @@
   --good: var(--good-on-dark);
   --danger: var(--danger-on-dark);
   --info: var(--info-on-dark);
+  /* The sixth. On the on-dark ladder the label is INK, not white: --slab on the
+     mint is 13.31:1, on the rose 6.01:1, on the periwinkle 7.40:1. White on those
+     three is 1.32:1, 2.93:1 and 2.38:1 — the first of them invisible. */
+  --on-status: var(--slab);
+}
+
+/* Custom properties inherit, and a slab is a section rather than a leaf: a white
+   card placed inside one would take the slab's white hairline and its mint, which
+   is the pack's own ban ("No mint on paper") arriving by inheritance. A light
+   surface nested in a slab therefore takes its tokens back. */
+.chorus-slab :is(.ch-card, .ch-well--paper, [data-surface="paper"]),
+[data-surface="slab"] :is(.ch-card, .ch-well--paper, [data-surface="paper"]) {
+  --focus-color: var(--ink-strong);
+  --line: rgba(70, 72, 77, 0.12);
+  --good: #198400;
+  --danger: #d03950;
+  --info: #1167f4;
+  --on-status: #ffffff;
 }
 
 /* The reference ships ZERO prefers-reduced-motion rules across 274KB. This block

package/kits/surveyor/src/styles.css

@@ -152,6 +152,13 @@
   --focus-w: 2px;
   --focus-offset: 2px;
   --focus-color: var(--action);
+  /* The ring VANISHES on the one surface the pack fills with --accent: #0a7269 on
+     #0d9488 is 1.55:1, under the 3:1 mark floor, and the closer panel is where the
+     pack puts its final CTA. So the accent slab re-declares the ring in the pack's
+     own paper — #fff7f3 on #0d9488 is 3.54:1, over the floor. Found by a blind
+     read of the shipped pack, not by a gate: a token that resolves is a token the
+     gates accept, whatever it resolves to underneath. */
+  --focus-color-on-accent: var(--bg);
 
   /* ---- Radii: a 10px hand, a 24px card, a 32px panel ------------------- */
   /* MEASURED. The control is the se-uikit's own 10px on every button and
@@ -284,6 +291,13 @@ b {
   font-weight: var(--weight-heading);
 }
 
+/* The closer panel is the pack's only saturated surface, and the only place the ink
+   ring cannot be seen. It is a SURFACE variant, not a theme: nothing else changes. */
+[data-surface="accent"] {
+  background-color: var(--accent);
+  --focus-color: var(--focus-color-on-accent);
+}
+
 /* ── components ── */
 /* Everything below consumes tokens only. The pack's rules in one place: the
    page is flat — elevation is a tint, the one shadow belongs to the detached

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sheleg-design-skill",
-  "version": "1.56.0",
+  "version": "1.58.0",
   "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-nine 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, onionskin, deskmate, test-drive, surveyor and chorus. 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"
@@ -19,13 +19,17 @@
     "node": ">=16"
   },
   "scripts": {
-    "test": "python3 test/validate.py && python3 test/validate_palette.py && python3 test/sloplint.py && node --check bin/cli.js && node test/installer_test.js && npm run selftest",
+    "test": "python3 test/validate.py && python3 test/validate_palette.py && python3 test/sloplint.py && python3 tools/chrome.py && node --check bin/cli.js && node test/installer_test.js && npm run selftest",
     "validate": "python3 test/validate.py && python3 test/validate_palette.py && python3 test/sloplint.py",
     "smoke": "node bin/cli.js --help",
     "palette": "python3 test/validate_palette.py",
     "sync-kits": "python3 scripts/sync-kit-tokens.py",
+    "gen-descriptions": "python3 scripts/gen_manifest_descriptions.py --write",
+    "gen-contents": "python3 scripts/gen_contents.py --write",
     "sloplint": "python3 test/sloplint.py",
-    "selftest": "python3 test/validate.py --self-test && python3 test/validate_palette.py --self-test && python3 test/sloplint.py --self-test"
+    "selftest": "python3 test/validate.py --self-test && python3 test/validate_palette.py --self-test && python3 test/sloplint.py --self-test",
+    "site": "python3 tools/site.py --out _site",
+    "chrome": "python3 tools/chrome.py"
   },
   "keywords": [
     "skill",

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

@@ -1,8 +1,8 @@
 {
   "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-nine 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), deskmate, test-drive, surveyor, and chorus (warm off-white paper under a faint construction grid with a crosshair at every intersection, where the set piece is somebody else's question in a cut-corner bubble — 24px on three corners and 0 on the top right — over near-black slabs cut into the sheet, one coral that fills but never writes, and a periwinkle that only exists inside a gradient, for AI-search visibility, brand monitoring and community marketing whose proof is other people's conversations) (a warm beige working day lit from one source above the top edge, where a single four-stop ramp — peach, lilac, violet, deep navy — washes the field, fills a panel and fills one word of a heading, everything a hand touches is a pill at 56px and everything else a 32px slab, elevation is a field step with two shadows on a 10,211px page, and the set piece is a framed transcript whose quoted chat client keeps its own face, ink and status colours under a --quoted-* namespace, for products sold as a colleague rather than a tool: AI employees and chat-native agents).",
-  "version": "1.56.0",
+  "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-nine pluggable visual style packs, each with a ready-made token layer — instrument-console (near-black aerospace console; technical systems and infrastructure), editorial-luxury (cream and espresso; editorial, research, premium B2B), workbench (quiet light/dark UI; dashboards, admin, internal tools), briefing-room (dark 16:9 deck; investor and board presentations), atrium (cream daylight; consumer health and high-trust DTC), babylove (white with orange; SEO SaaS, long time-to-value, disconnected states), patchbay (black with mint-cyan; engines, buses, pipelines, OSS front doors), nameplate (cool slab with coral; press, certification and third-party trust), rimlight (white with blue light; studios, services and case studies), onionskin (white working sheet; developer and AI infrastructure), deskmate (warm beige with a dusk bleed; AI coworkers and chat-native agents), test-drive (warm paper with one coral; self-serve SaaS proven by the live product), surveyor (peach paper with teal and pink; visibility, monitoring and benchmark tools), chorus (warm paper under a crosshair grid, with a cut-corner bubble; AI-search visibility, brand monitoring and community marketing), outrank (white with violet; one brand across marketing and product), orchard (warm oat slabs; friendly biotech and wellness), field-notes (ruled green paper; auditable open-source developer tools), showroom (white gallery; product-led companies selling the app), blueprint (white technical stock; vector, storage and query infrastructure), prism (iridescent hard edge; command-first OSS infrastructure), maquette (near-black table; enterprise data infrastructure), cyclorama (looping pastel field; applied-AI consultancies), scoreboard (warm paper; growth, ads and accumulating metrics), datasheet (off-white specification; fraud, identity and device intelligence), manpage (cream manual; APIs, SDKs, CLIs and MCP servers), pigeonhole (filed white field; inbox, ticket and CRM triage), roster (faint square grid; platforms sold through who uses them), ora (warm coal; machine verdicts, audits and protocol traces), tenor (warm management paper; agent operations and autonomous back office), ledger (cream ruled console; analysts, BI and warehouse agents), paperclip (monochrome coal; orchestrators, schedulers and job runners), awning (white commerce forecourt; storefront, payroll and billing platforms), router (pale console with hairlines; dashboard, billing and inventory surfaces), daylight (bright portal with one shadow; client onboarding and service portals), notation (restrained technical hairlines; OSS, docs and developer workspaces), almanac (oatmeal editorial paper; manifestos and category-defining pages), vitrine (serif trust display; evaluated B2B, security and compliance), proscenium (white demo sequence; product tours and launch pages), bulletin (cheerful outlined bands; broad SMB and agency platforms). Ships the sheleg-design skill, the architecture reference, the motion doctrine, the Figma and Claude Design bridges, AI-surface patterns, the packs' token CSS, and the /sheleg-design command.",
+  "version": "1.58.0",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

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

@@ -14,6 +14,19 @@ and states, not a palette. Every token named here is workbench's.
 
 ---
 
+## Contents
+
+- 1. The five states of a model call
+- 2. Streaming beats spinners
+- 3. Latency has two numbers
+- 4. Provenance and uncertainty
+- 5. Agent actions: the confirm is the design
+- 6. Empty states carry the capability
+- 7. Chat is a shape, not the shape
+- 8. Cost, quota and scope
+- 9. Bans
+- Evidence
+
 ## 1. The five states of a model call
 
 Design all five before building any. Most AI UI ships state 2 and 3 only, then

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

@@ -15,6 +15,16 @@ agent that does not have it — the pack stands on its own and nothing below app
 
 ---
 
+## Contents
+
+- 1. What crosses, and in what shape
+- 2. Style packs — the pack is the source of truth
+- 3. Figma — one border at a time
+- 4. Reference sweeps (Lazyweb, Mobbin, Refero) — layout crosses, identity does not
+- 5. Live-site extraction — the pack first, the sync second
+- 6. What cannot cross
+- 7. Round-trip discipline
+
 ## 1. What crosses, and in what shape
 
 A kit ships **three layers**, and they are a stack rather than a menu:

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

@@ -15,6 +15,13 @@ stands on its own and nothing below applies.
 
 ---
 
+## Contents
+
+- 1. Code → Figma (publish the pack as variables)
+- 2. Figma → code (implement a design without importing slop)
+- 3. What cannot cross
+- 4. Round-trip discipline
+
 ## 1. Code → Figma (publish the pack as variables)
 
 Use when a project has the pack in code and needs the design file to match — or

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

@@ -9,7 +9,7 @@ pack's `## Responsive` section covers that, and this file does not repeat it.
 
 - What a pack decides here, and what it does not
 - The six rules every pack already carries — and one no pack answers
-- Reference sweeps (Lazyweb, Mobbin) — structure crosses, identity does not
+- Reference sweeps — structure crosses, identity does not
 
 ## What a pack decides here, and what it does not
 

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

@@ -8,6 +8,20 @@ Every number here is a decision someone else already paid for. Use them.
 
 ---
 
+## Contents
+
+- 1. Should this animate at all?
+- 2. Easing
+- 3. Duration
+- 4. Springs
+- 5. Forbidden forms
+- 6. Scroll motion
+- 7. Motion that came from a design tool
+- 8. Anti-drift
+- 9. Reduced motion
+- 10. Pre-flight
+- How the calibration dials bind
+
 ## 1. Should this animate at all?
 
 The first question is not "what animation" — it is "how often will a person see
@@ -339,10 +353,14 @@ parallax and `animation-timeline`; it keeps a sticky nav, which is the only diff
   **Four more standalone packs pin their own, and each states it in its own Register:**
   `ora` at **4**, `tenor` at **4**, `paperclip` at **5** — the last one higher because it
   is the only pack in the family that spends a native scroll-driven parallax —
-  and `bulletin` at **3**, the lowest ceiling in the library, because its whole
-  measured motion budget is an entrance fade, a 0.12s press and a 0.3s hover.
-  Its depth is drawn as a hard ink offset rather than animated, and animating
-  that offset is precisely what flattens it.
+  and `bulletin` at **3**, because its whole measured motion budget is an entrance
+  fade, a 0.12s press and a 0.3s hover. Its depth is drawn as a hard ink offset
+  rather than animated, and animating that offset is precisely what flattens it.
+  **The lowest ceiling in the library is 2**, and four of them pin it. This sentence
+  called `bulletin` the lowest for four releases while two others already sat under
+  it, which is why the number is now derived: `validate_motion_ceiling_floor()`
+  recomputes the minimum from the packs' own Register lines and fails when this
+  paragraph disagrees with them.
   `field-notes` is standalone **by default** and may opt into the cinematic layer — it carries a `## Motion flavor` section saying
   how — so it is the one standalone pack without a hard ceiling. Read that
   section before turning the dial up on it.

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

@@ -9,6 +9,16 @@ plays.
 That is a different medium with different physics, and treating it as "the same
 animation, exported" is the mistake this document exists to prevent.
 
+## Contents
+
+- The boundary
+- Before the tool: what a rendered asset costs
+- The two tools, measured
+- The recommendation, and the three conditions that reverse it
+- The token seam
+- Reduced motion, on the other side of the render
+- Pre-flight for a rendered asset
+
 ## The boundary
 
 | The motion is… | It belongs to | Read |

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

@@ -26,6 +26,25 @@ build new sites on the same principles and understand *why* each piece works.
 
 ---
 
+## Contents
+
+- 0. The one-paragraph thesis
+- 1. Architecture at a glance
+- 2. Layer 1 — The scroll store (the single clock)
+- 3. Layer 2 — Smooth scroll (one position per frame)
+- 4. Layer 3 — The particle field (the scene-formation engine)
+- 5. Layer 4 — The 2D fallback (SignalMesh)
+- 6. Layer 5 — The projection bridge (fusing DOM and WebGL)
+- 7. Layer 6 — DOM choreography
+- 8. Layer 7 — Reveal primitives (act-themed entrances)
+- 9. Layer 8 — Scrubbed instruments (GSAP recipe)
+- 10. Cross-cutting rules
+- 11. Recipe — build a new SHELEG site from scratch
+- 12. Why it works (the deeper principles)
+- 13. File map (one file per idea)
+- Quick reference — each rule, and the failure it prevents
+- Three looks that are defaults, not decisions
+
 ## 0. The one-paragraph thesis
 
 A landing page feels "alive" not because it has many animations, but because a

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

@@ -1,9 +1,10 @@
 ---
 name: sheleg-design
-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.
+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: "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 as a web page" / "веб-презентация". Not for structure, copy, backend behavior, or .pptx decks.
 license: MIT
+compatibility: Optional siblings — dataviz, shadcn, migrate-radix-to-base; each has an in-text fallback when absent.
 metadata:
-  version: 1.56.0
+  version: 1.58.0
 ---
 
 # SHELEG Design
@@ -156,10 +157,14 @@ as a definition of done, in that order:
 - **Scene depth — six layers** ([`SURFACE_COMPOSITION.md`](./SURFACE_COMPOSITION.md)),
   before writing CSS for a cinematic page. A scene has planes; everything on one
   plane is the failure no amount of easing repairs.
-- **Charts — hand the pack to `dataviz`** (same file), before drawing a chart in
-  any pack. Token names are not uniform across the thirty-nine packs — only `--bg`
-  and `--ink` resolve in every one — and an undefined custom property does not error,
-  it silently falls back. Guessing one is the quietest way to ship a wrong chart.
+- **Charts — the role contract in the same file, plus the `dataviz` handoff
+  where that skill exists**, before drawing a chart in any pack. Token names are
+  not uniform across the thirty-nine packs — only `--bg` and `--ink` resolve in
+  every one — and an undefined custom property does not error, it silently falls
+  back. Guessing one is the quietest way to ship a wrong chart. A `dataviz`
+  skill is an optional neighbour this skill does not ship: where none is
+  installed, the role table in `SURFACE_COMPOSITION.md` IS the chart contract,
+  applied by hand.
 - **Mobile surfaces** ([`MOBILE_SURFACES.md`](./MOBILE_SURFACES.md)), when the
   brief is a native app screen or a mobile-web view — not a desktop page whose
   only mobile concern is collapse. Five mobile rules the packs each state alone,
@@ -232,9 +237,13 @@ there, the work is bespoke scroll and WebGL, and reaching for a component kit is
 how a hero ends up looking like a settings screen.
 
 **Who does the work.** This section decides *whether* and *against which tokens*.
-The `shadcn` skill does the adding, searching and composing, and
-`migrate-radix-to-base` handles the Radix→Base move; both are installed and
-trigger on their own words. Do not restate their component docs here.
+Where the `shadcn` skill is installed it does the adding, searching and
+composing, and `migrate-radix-to-base` handles the Radix→Base move; both are
+**optional neighbours** this skill declares in its `compatibility` line and does
+not ship, and they trigger on their own words where present. Where they are
+absent nothing is blocked: the kit's own CLI (`npx shadcn@latest add
+<component>`) does the adding, and the token mapping above binds either way. Do
+not restate their component docs here.
 
 ## Optional — Figma (design ↔ code)
 

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

@@ -53,9 +53,15 @@ A pack that bans grain and blur leaves the slot empty rather than filling it —
 
 ## Charts and data — hand the pack to `dataviz`
 
-Do not restyle charts from the pack by hand, and do not let a chart library pick
-its own colours. The `dataviz` skill already owns chart form, colour roles and
-the runnable palette validation; a pack is the *parameter set* it consumes.
+Do not let a chart library pick its own colours. Where a `dataviz` skill is
+installed, it owns chart form, colour roles and the runnable palette validation,
+and a pack is the *parameter set* it consumes — hand it the values mapped below.
+That skill is an **optional neighbour**: this skill declares it in its
+`compatibility` front-matter and does not ship it, so its absence is an ordinary
+state, not a broken install. **Where no dataviz skill is installed, the role
+table below is the contract** — resolve each role from the chosen pack's token
+layer by hand, and the status map and the two rules at the end of this section
+bind exactly the same, with nobody to hand them to.
 
 **Read the chosen pack's own token names before you write a single `var()`.**
 This table is by *role*, not by token, because the names are not uniform across