sheleg-design-skill 1.59.1 → 1.59.4

package/CHANGELOG.md

@@ -1,5 +1,106 @@
 ## [Unreleased]
 
+> **v1.59.3 is a burned tag.** It was pushed against `origin/main` before the release
+> PR had actually merged, so it names the v1.59.2 tree; the version-sync gate refuses
+> it and the remote forbids tag deletion. Nothing shipped under it — this version is
+> the same change, tagged on the verified merge commit.
+
+## [1.59.4] - 2026-09-06
+
+### Fixed
+
+- **The front matter declared the optional siblings and said nothing about the
+  hard requirement.** `compatibility:` named `dataviz`, `shadcn` and
+  `migrate-radix-to-base` — three skills the body can work without — while the
+  body REQUIRES node with npx and network twice (`npx sheleg-design-skill --kit
+  <pack>`, `npx sshlg-skills pack design --lane`) and named no path for a
+  machine where npx is unreachable. Found by the family audit (2026-09-06, wave
+  AUDIT-WAVE-0906). Both halves fixed: the front matter now opens with
+  *"Kit/lane commands need node>=16, npx, network"*, and the kit-authoritative
+  paragraph states the degraded path in the same voice v1.59.1 gave the
+  director's Act 2 — nothing is blocked, the pack and its token layer in
+  `styles/tokens/<pack>.css` still carry the rules by reading, and the component
+  states only a kit materializes are then **unverified**, said out loud rather
+  than presented as kit-checked.
+
+  **The honest first draft was refused by this repository's own gate, and the
+  refusal is the interesting part.** The full declaration measured 342 chars —
+  comfortably inside the Agent Skills spec's 500-char `compatibility` cap — and
+  `check_description_canon` refused it at **432 of a 256 overhead budget**,
+  because every non-description key is read every session and the budget exists
+  so front matter never becomes a place to write prose. Two limits, and the
+  binding one was the house budget, not the spec cap — the same lesson v1.59.2
+  paid for on the description. So the front matter carries the compressed form
+  (**253 of 256**) and the body carries the detail, which is where a reader who
+  hit the failure would look anyway.
+
+- **An empty recursive directory chain sat in checkouts, and the mirror
+  validator could not see the class it belongs to.**
+  `.cursor/skills/sheleg-design/styles/tokens/.cursor/skills/sheleg-design/` —
+  zero files, invisible to `git status` (git tracks no directory), to the npm
+  tarball (npm packs files), and to both directions of the mirror-drift check,
+  which walk `rglob("*")` filtered by `is_file()`. Measured on this machine
+  2026-09-06: the umbrella's submodule checkout at `skills/sheleg-design`
+  carried the chain at commit `0902ef6`; this repository's own checkout was
+  clean. The artefact is removed, and the CLASS is closed: the mirror block now
+  reads **directories** over both trees — a nested `.cursor` anywhere inside
+  either bundle is refused as a copy artefact whatever it contains, and an
+  empty directory is refused wholesale. Watched failing against a real planted
+  chain before being believed — both checks answered with their own messages,
+  not a neighbour's — and planted permanently in the self-test as two
+  **directory fixtures**, a shape `PLANTS` cannot express because its mutations
+  are text edits to a file, and each fixture asserts the plant landed before
+  trusting any red. Floor raised 5621 → 5641, measured by running the gate on
+  this tree.
+
+## [1.59.2] - 2026-09-03
+
+### Fixed
+
+- **The skill did not advertise the two words its own router text names.** The umbrella's
+  routing block says *"before design, **redesign**, **layout**, front-end or mobile-UI
+  work"*, and the trigger layer only ever fires on words a skill claims in its own
+  description. Measured 2026-09-03 against the real matcher: `редизайн сайта` → nothing,
+  `переделай дизайн` → nothing, `свёрстай дашборд` → nothing. The router text was inert
+  for exactly the vocabulary it was written for.
+
+  Four triggers added — `"redesign" / "редизайн, свёрстай, вёрстка"` — and paid for by
+  trimming prose no trigger depends on, verified against `lib/triggers.js` before cutting:
+  `layers that drift`, `or scrubbed`, `particle/`. Description **965 → 969, against a
+  working limit of 970.**
+
+- **`B-84` was right and this entry's first draft said it was stale — the correction is
+  recorded rather than quietly rewritten.** That row cites a *970 working limit* and calls
+  this fix blocked. Reading this repository's own `test/validate.py` finds only the Agent
+  Skills cap of 1024, so the draft concluded no 970 existed and shipped a description at
+  1014. **CI refused it**: the limit is a family HOUSE RULE, enforced by `make-skill`'s
+  `audit_skill.py --house` (`DESC_HEADROOM`), which runs in this repository's own
+  workflow — *"inside the 1024 cap but past the 970 working limit: leave room for the
+  'what this is NOT for' clause a near-miss neighbour will require."*
+
+  **Two limits, two enforcers, and only one of them lives here.** A number absent from the
+  validator you happen to open is not a number that does not exist.
+
+Headroom after this change is **ten characters**, at 960 of 970, bought by trimming
+  prose rather than by raising a limit. B-84's underlying claim — that the descriptions
+  which miss most cannot accept another trigger for free — holds.
+
+- **The first trim removed three phrases a second consumer depended on.** `particle`,
+  `scrubbed` and `drift` are not hook triggers, so a check against `lib/triggers.js`
+  called them free; they are `T1_CARRIERS` here, the phrases this repository's own eval
+  tasks are matched on, and its gate refused the edit. Every span in the shipping trim
+  was tested against **both** lists before being cut — *"a description edit that reads
+  as additive can still remove the only phrase carrying a task"*, which is that guard's
+  own sentence.
+
+- **The plant guarding that rule had gone quiet, and this release is why it was found.**
+  It hardcoded `"scroll-linked or scrubbed motion"`; the trim reworded exactly that
+  clause, the replace no-oped, and the self-test reported the guard as BROKEN while the
+  guard was fine. Standing instruction #6, on the anchor it warns about. The victim is
+  derived from `T1_CARRIERS` now and the assertion is made on the **parsed description,
+  read the way the guard reads it** — a plant that changed some other byte would still
+  be testing nothing.
+
 ## [1.59.1] - 2026-09-03
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sheleg-design-skill",
-  "version": "1.59.1",
+  "version": "1.59.4",
   "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"

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

@@ -3,7 +3,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-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.59.1",
+  "version": "1.59.4",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

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

@@ -1,10 +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 - "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.
+description: Use when deciding how something LOOKS or MOVES — cinematic landing pages and hero sections, particle/WebGL, scrubbed motion, drift, dashboards, admin or internal tools, mobile screens, chat or agent interfaces, tokens, 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" / "веб-презентация", "redesign" / "редизайн, свёрстай, вёрстка". 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.
+compatibility: Kit/lane commands need node>=16, npx, network. Optional siblings — dataviz, shadcn, migrate-radix-to-base. Each has an in-text fallback when absent or unreachable.
 metadata:
-  version: 1.59.1
+  version: 1.59.4
 ---
 
 # SHELEG Design
@@ -89,7 +89,11 @@ 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
+open. A widened pack's kit and `## Components` section must agree. Where `npx`
+is unreachable — no node, no registry — nothing is blocked: the chosen pack and
+its token layer in `styles/tokens/<pack>.css` still carry the rules by reading,
+but the component states only a kit materializes are then **unverified** — say
+so, rather than presenting a read-off state as a kit-checked one. 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.