sheleg-design-skill 1.58.0 → 1.58.2

package/CHANGELOG.md

@@ -6,6 +6,78 @@ follow [SemVer](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [1.58.2] - 2026-08-31
+
+### Added
+
+**The evals ran, and the results table stops saying "never executed."** Every
+trigger case probed a genuinely blind fresh context — a headless session with
+no settings loaded, whose whole prompt was the query, the installed-skill list
+and one question — once per model: `claude-haiku-4-5-20251001` answered 15/15,
+`claude-sonnet-5` 14/15, and the one miss is recorded rather than smoothed
+(q10: a mechanical CSS-selector fix routed here, against the suite's
+"no visual decision required" negative). The three scenarios ran per model as
+fresh sessions with the skill on disk and are scored line by line; the lines
+that need a built page in a browser or a live Figma file are recorded as
+*not reproducible from this harness*, not guessed. Dated rows and the full
+method, including its limits, live in `test/evals/RESULTS.md` (SHD-08).
+
+**Three coexistence negatives name the installed neighbours that share this
+skill's ground.** `q13`–`q15` are near-miss queries that must NOT route here,
+and did not: an artifact styled with a pre-set theme went to `theme-factory`,
+a page rebuilt in Figma from its published design system went to
+`figma-generate-design`, and an explicitly bespoke no-pack brief went to
+`frontend-design` — on both models probed. They ride the same split and the
+same validator as the twelve authored cases.
+
+### Fixed
+
+**Both manifests declare their `$schema`.** `.claude-plugin/marketplace.json`
+names `json.schemastore.org/claude-code-marketplace.json` and
+`plugins/sheleg-design/.claude-plugin/plugin.json` names
+`json.schemastore.org/claude-code-plugin-manifest.json` — the shape
+`make-skill`'s own manifests ship — and `claude plugin validate` stays green
+over both (SHD-02).
+
+**The GitHub About description stops counting packs.** It said "35 style
+packs" while the tree shipped 39: the About box is not a file in this tree,
+and nothing in the release path can rewrite it — the release workflow's
+`GITHUB_TOKEN` cannot carry the `administration` permission that
+`PATCH /repos/{owner}/{repo}` requires — so the regenerated description
+states no count at all, and CONTRIBUTING records the decision beside the
+release procedure (SHD-04).
+
+## [1.58.1] - 2026-08-30
+
+### Fixed
+
+**The description was not valid YAML — again, and this time the gate lives here.**
+The 1.57.0 trigger rewrite put `Triggers: "design a landing" …` into the
+front-matter description as an unquoted scalar, and the `: ` after `Triggers`
+turns the whole block into an invalid mapping (*"mapping values are not allowed
+here"*, line 3). Identical class to 1.37.4, twelve days earlier: this repo's own
+5598 checks, the pinned house auditor and `claude plugin validate --strict` all
+read the field with a regex and stayed green, while the umbrella's YAML-parsing
+gate refused the file when pinning v1.58.0. The fix is one character class —
+`Triggers - "…"`, the shape every family sibling already uses — so all 35 routed
+trigger phrases survive byte-for-byte (`advertised_check.js` re-run against this
+tree: `ok: sheleg-design advertises all 35 routed trigger(s)`), and the `.cursor`
+mirror carries the same bytes.
+
+**Why 1.37.4's fix did not hold: its strict gate lived one repository up.**
+`check_routed_triggers_still_advertised()` asks the umbrella's checker, which
+exists only when the umbrella sits above this checkout — and CI is always a
+standalone clone, so the check disclosed instead of looking and the defect
+shipped twice. `validate_front_matter_is_yaml()` now parses every shipped
+front-matter block (bundle SKILL.md, `.cursor` mirror, plugin commands, cursor
+rules — 4 files, 17 checks) with `yaml.safe_load` in this repo's own gate, fails
+closed when PyYAML is absent, and refuses a `description` that nests into a
+mapping without a parse error. Watched failing on the real defect before the fix
+and on a permanent self-test plant that restores `Triggers: "` verbatim — caught
+by its own message, not by the mirror-drift check that also trips. The three CI
+workflows that run `validate.py` install PyYAML explicitly rather than assuming
+the runner image carries it.
+
 ## [1.58.0] - 2026-08-30
 
 ### The catalogue stops being the one surface nobody designed, and two blind reads land

package/package.json

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

@@ -1,8 +1,9 @@
 {
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "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.58.0",
+  "version": "1.58.2",
   "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 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.58.0
+  version: 1.58.2
 ---
 
 # SHELEG Design