sheleg-design-skill 1.14.0 → 1.15.0

package/CHANGELOG.md

@@ -4,6 +4,56 @@ All notable changes to this project are documented in this file. The format
 follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions
 follow [SemVer](https://semver.org/spec/v2.0.0.html).
 
+## [1.15.0] - 2026-08-12
+
+Two of the eight unrun scenarios were run. Both passed, and between them they
+found four things three green gates could not.
+
+### Added
+
+- **A core pack's missing half has an authored answer, and the bundle now says
+  where.** `npx sheleg-design-skill --kit <pack>` materializes `src/styles.css`,
+  whose component half is real CSS for `:hover`, `:focus-visible`, `:disabled` and
+  selected — the exact per-component states a **core** pack declines to specify.
+  `SKILL.md` said kits are not installed and stopped there, so an agent reading the
+  bundle invented those states from scratch while an authored version sat one
+  command away. Neither file pointed at the other.
+- **A precedence rule for the dial table.** "A quiet internal admin dashboard"
+  fires both *quiet like Linear* (DENSITY 2–3) and *product UI* (6–8) — a factor of
+  three, with nothing to break the tie. **The row that names the surface wins over
+  the row that names a mood**, and you say which fired.
+- **Two cases the reference-sweep pairing assumed away**, both common: only the
+  image server present (you are reading structure off screenshots — a weaker read,
+  say so) and a sweep that returns nothing (a null result is a result; "I swept"
+  with no findings and no statement of emptiness cannot be told apart from not
+  sweeping).
+
+### Fixed
+
+- **`workbench`'s accent gotcha named two surfaces of three.** It forbids accent
+  text on `--panel-2` and `--accent-weak` at 4.30:1 — but in light mode `--bg` **is**
+  `--panel-2` (`#F7F8FA`), so a plain accent link on the app ground fails identically
+  and read as covered for four releases. The most ordinary element in an admin panel.
+
+## [1.14.1] - 2026-08-12
+
+### Fixed
+
+- **1.14.0 said Refero was "alone among the three" in returning flows. Mobbin
+  returns them too.** `mcp__mobbin__search_flows` has always existed; it was
+  invisible because Mobbin was registered and unauthenticated, so the sentence
+  shipped as a claim nobody in that session could check — in a file whose own
+  rule, two paragraphs away, is **gate on the tools present in the session, not
+  on the config**. The rule was right and was not applied to its own author.
+  Corrected the hour Mobbin was signed in, against its live tool surface.
+- **The distinction that replaces it is the useful one: they answer in different
+  media.** Mobbin returns each step as an evenly-spaced *preview image* — its own
+  tool description says to look at those rather than trust the metadata — and
+  also searches web **sections** (hero, pricing, footer). Refero returns each step
+  as *structure*: a goal, an action, a system response. Drawing a diagram with
+  decision points and recovery paths reads Refero; judging whether a step works on
+  a phone looks at Mobbin.
+
 ## [1.14.0] - 2026-08-12
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sheleg-design-skill",
-  "version": "1.14.0",
+  "version": "1.15.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 thirteen locked style packs with ready-made design tokens — instrument-console, editorial-luxury, workbench, briefing-room, atrium, orchard, field-notes, cyclorama, showroom, blueprint, prism, maquette and scoreboard. 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 thirteen 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 (friendly consumer biotech), 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). 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.",
-  "version": "1.14.0",
+  "version": "1.15.0",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

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

@@ -88,13 +88,40 @@ A reference sweep answers *what a good version of this screen contains* — sect
 hierarchy, content order. It never answers what it looks like.
 
 Three servers can fill the slot and they are not interchangeable. **Lazyweb** is
-web-product screens and growth mechanics; **Mobbin** is strongest on native iOS and
-Android and carries web; **Refero** searches screens, returns visually and
-functionally *similar* screens for one you already like, and — alone among the three
-— returns **flows**: connected sequences with a goal, an action and a system response
-per step, which is what you read for step count, decision points, recovery paths and
-confirmation. Sweep whichever are present; with more than one, sweep them all and say
-which answered what.
+web-product screens and growth mechanics. **Mobbin** searches screens, **flows** and
+web **sections** (hero, pricing, footer), strongest on native iOS and also carrying
+web; its flows come back as evenly-spaced *preview images* per step, and its own tool
+description says to look at them rather than trust the metadata. **Refero** searches
+screens, returns visually and functionally *similar* screens for one you already
+have, and returns flows as *structure* — a goal, an action and a system response per
+step.
+
+**That is the split worth knowing: two of the three answer "flow", and they answer it
+in different media.** Mobbin shows you what each step looked like; Refero tells you
+what each step did. Drawing a diagram with decision points and recovery paths reads
+Refero; judging whether a step actually works on a phone looks at Mobbin. Sweep
+whichever are present; with more than one, sweep them all and say which answered
+what.
+
+Two cases the pairing above quietly assumes away, and both are the common one:
+
+- **Only the image server is present.** Then you are deriving structure from
+  pictures — reading step order and decision points off screenshots — which is a
+  weaker read than structured steps, not an equivalent one. Do it, and say that is
+  what you did. The failure is inferring a system response from a screenshot and
+  reporting it as if it had been stated.
+- **A sweep returns nothing.** A null result is a result: say the query and that it
+  came back empty. "I swept" with no findings and no statement of emptiness is
+  indistinguishable from not sweeping, and the next reader cannot tell which
+  happened.
+
+> **[CORRECTION — 1.14.1]** 1.14.0 shipped this paragraph saying Refero was "alone
+> among the three" in returning flows. It is not: `mcp__mobbin__search_flows` has
+> always existed. The claim was written while Mobbin was registered but
+> unauthenticated, so its tool surface was invisible and the sentence could not be
+> checked — which is the whole reason this file says to **gate on the tools present in
+> the session**. The rule was right and the paragraph next to it was written as if it
+> did not apply to the author.
 
 - **A swept reference does not become a component.** It informs how you compose the
   pack's components on a screen; it never justifies a new atom, a second accent, or a

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

@@ -3,7 +3,7 @@ name: sheleg-design
 description: Use when building or upgrading a cinematic scroll-driven landing page, marketing site or hero (particle/WebGL background, scroll-linked animation, parallax, scrubbed sections) — when such a page feels busy or janky or its motion layers drift out of sync — or when styling product UI with its style packs - dashboards, admin panels, internal/dev tools, mobile app screens, design tokens, light/dark themes - or when carrying a visual system across the Figma border (publishing tokens as variables, implementing a design without importing raw values). Triggers - "cinematic landing" / "кинематографичный лендинг", "scroll animation" / "скролл-анимация", "dashboard style" / "стиль дашборда", "design tokens" / "дизайн-токены", "light/dark theme" / "светлая/тёмная тема", "figma variables / figma to code" / "переменные фигмы, фигма в код", "chat/agent UI" / "интерфейс чата или агента", "streaming output" / "стриминг ответа", "mobile screen" / "мобильный экран".
 license: MIT
 metadata:
-  version: 1.14.0
+  version: 1.15.0
 ---
 
 # SHELEG Design
@@ -86,6 +86,14 @@ style pack in [`styles/`](./styles/):
 | [`cyclorama`](./styles/cyclorama.md) | a pale field cycling through six pastel stops on a 32s loop under fixed near-black ink, monospaced typewriter serif over mono, one orange used only as a fill, a particle organ that redeploys per section | enterprise AI transformation, applied-AI services and technical consultancies — a product whose argument is a change of state, not a screenshot |
 | [`scoreboard`](./styles/scoreboard.md) | warm paper and warm near-black ink, 2–3px radii, an ink primary button, one hot orange that only ever marks, and a dark ledger of dotted-leader rows whose numbers are set in an aliased pixel face | products whose argument is an accumulating number — ads and SEO operators, growth tools, revenue dashboards sold on results |
 
+**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 per-component states — `:hover`, `:focus-visible`, `:disabled`,
+selected — that a core pack declines to specify. It is not installed with this skill,
+so an agent reading only this bundle cannot see it and will invent those states from
+scratch. Fetch the kit before inventing them, and treat what differs between the kit
+and the pack as a defect in one of the two rather than a choice.
+
 **Six of the thirteen 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
@@ -138,6 +146,13 @@ what you announced.
 | redesign, preserve the existing identity | match | match +1 | match |
 | redesign, explicit overhaul | +2 | +2 | match |
 
+**A brief can match two rows, and they can disagree by a factor of three.** "A quiet
+internal admin dashboard" fires both *"quiet like Linear"* (DENSITY 2–3) and *"product
+UI"* (DENSITY 6–8). The precedence rule: **the row that names the surface wins over the
+row that names a mood.** A surface decides how much has to fit; a mood decides how it is
+handled — in a product-UI pack, "quiet" is bought with restraint in colour and motion,
+not with emptiness. Say which row you took and why when two fire.
+
 ### How they bind
 
 - **The pack wins on values, the dials win on amount.** A dial never invents a
@@ -270,11 +285,12 @@ its own.
 
 A pack fixes *how it looks*; it does not say what a good version of the screen
 contains. **Lazyweb** (`mcp__lazyweb__*`), **Mobbin** (`mcp__mobbin__*`) and
-**Refero** (`mcp__refero__*`) all answer that from shipped products — Mobbin is
-strongest on native iOS and Android and also carries web; Refero adds
-step-by-step flows and similar-screen lookup. **Use whichever is present, on web
-and mobile alike; with more than one, sweep them all.** Then map what you find
-onto the pack's tokens.
+**Refero** (`mcp__refero__*`) all answer that from shipped products. Mobbin is
+strongest on native iOS and also carries web sections; **Mobbin and Refero both
+return multi-step flows, in different media** — Mobbin as preview images per
+step, Refero as goal/action/system-response text. **Use whichever are present, on
+web and mobile alike; with more than one, sweep them all.** Then map what you
+find onto the pack's tokens.
 
 **Gate on the tools, not on the config** — a registered server nobody signed
 into exposes nothing, and Mobbin also needs a paid plan. Absent, proceed and say

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

@@ -165,7 +165,12 @@ hue.
   colour this pack does not own. **The resolutions, which are rules rather than
   new tokens:** the status word inside a chip renders in `--ink` (14–15:1 on all
   three tints) with the status colour carried by the dot or the fill; and
-  accent-coloured text never sits on `--panel-2` or on `--accent-weak` — inside a
+  accent-coloured text never sits on `--panel-2`, on `--accent-weak`, **or on
+  `--bg`** — in light mode `--bg` and `--panel-2` are the same `#F7F8FA`, so the app
+  ground carries that same 4.30 and a plain accent link sitting directly on the
+  dashboard background fails identically. This clause named only two of the three for
+  four releases, which made the most ordinary element in an admin panel look covered.
+  Inside a
   selected row or a sticky header, text is `--ink` or `--muted`.
 - **`--bg` and `--panel-2` are the same colour in light mode** (`#f7f8fa`) and
   different in dark. So the mandated row hover — a `--panel-2` fill — is