sheleg-design-skill 1.64.2 → 1.65.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,21 @@
1
+ ## 1.65.0 — a rendered surface is checked in WebKit (Safari) first
2
+
3
+ - **Engine order in the visual-review contract.** `VISUAL_REVIEW.md` gains
4
+ *Engine order — WebKit (Safari) first*: Safari through `safaridriver`,
5
+ Playwright's `webkit` (`--browser webkit`, `npx playwright install webkit`),
6
+ Safari Web Inspector, and `open -a Safari <url>` on macOS rather than the
7
+ system default browser. Chromium is a stated fallback for a task that needs
8
+ Chrome itself (a Chrome-only API, Lighthouse, a CDP trace, the chrome-devtools
9
+ MCP), on the Chrome Dev build, with a temporary profile and every started
10
+ process closed. A Chromium-only check is reported as exactly that.
11
+ - The capture record gains an `engine` field. Capture stays tool-agnostic:
12
+ any working browser capability still qualifies and Playwright is still not required.
13
+ - Motion review (`MOTION_DOCTRINE.md` §12) and the director's verify lane
14
+ (`CREATIVE_DIRECTOR.md`) put the WebKit route first and keep the Chrome
15
+ DevTools tooling as the stated Chromium fallback.
16
+ - New regression `test/audit_regressions/safari-first.py`, with mutations that
17
+ drop each point. Text integrity only; no claim that a model follows it.
18
+
1
19
  ## 1.64.2 — derived palette facts and explicit calm fallback
2
20
 
3
21
  - Dark theme documentation now includes source-derived tables for almanac,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sheleg-design-skill",
3
- "version": "1.64.2",
3
+ "version": "1.65.0",
4
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 \u2014 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.",
5
5
  "bin": {
6
6
  "sheleg-design-skill": "bin/cli.js"
@@ -3,7 +3,7 @@
3
3
  "name": "sheleg-design",
4
4
  "displayName": "SHELEG Design",
5
5
  "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.",
6
- "version": "1.64.2",
6
+ "version": "1.65.0",
7
7
  "author": {
8
8
  "name": "ssheleg",
9
9
  "url": "https://x.com/sshlg93"
@@ -323,9 +323,12 @@ until the judge has been measured against a labelled set. The verdict goes into
323
323
  the record's `ADA` field.
324
324
 
325
325
  **Run them where the thing runs.** A screenshot in a browser at the target
326
- viewport beats reading the diff, every time; `webapp-testing` and the Chrome
327
- DevTools tooling exist for this, and the `verify` lane in Act 2 casts them. A
328
- quality claim made from source is a claim about source.
326
+ viewport beats reading the diff, every time. WebKit first
327
+ ([`VISUAL_REVIEW.md`](./VISUAL_REVIEW.md#engine-order)): Safari through
328
+ `safaridriver`, or Playwright's `webkit` under `webapp-testing`; the Chrome
329
+ DevTools tooling is the stated Chromium fallback when the task needs Chrome
330
+ itself. The `verify` lane in Act 2 casts them. A quality claim made from source
331
+ is a claim about source.
329
332
 
330
333
  ### Render critique — the soft half, made actionable
331
334
 
@@ -425,8 +425,11 @@ meant; the frames say what ships. Four steps, in this order, on the real build
425
425
  1. **Capture a frame strip and a run video.** One frame per phase — start,
426
426
  mid, settle; one per step of a stagger — not smooth playback, plus the video
427
427
  of one full run.
428
- - Web: a performance trace with screenshots in DevTools, or a Playwright
429
- video; frames pulled from it at the phase times.
428
+ - Web: WebKit first ([`VISUAL_REVIEW.md`](./VISUAL_REVIEW.md#engine-order))
429
+ — a Playwright `webkit` video or a Safari Web Inspector timeline
430
+ recording; a Chromium DevTools performance trace with screenshots is the
431
+ stated fallback when the task needs the CDP trace itself. Frames are
432
+ pulled from it at the phase times.
430
433
  - Native: the simulator's or device's screen recording
431
434
  (`xcrun simctl io <device> recordVideo`, `adb shell screenrecord`).
432
435
  - A rendered file ([`MOTION_PRODUCTION.md`](./MOTION_PRODUCTION.md)):
@@ -4,7 +4,7 @@ description: Use when deciding how something LOOKS or MOVES — landing/hero pag
4
4
  license: MIT
5
5
  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.
6
6
  metadata:
7
- version: 1.64.2
7
+ version: 1.65.0
8
8
  ---
9
9
 
10
10
  # SHELEG Design
@@ -13,6 +13,7 @@ rather than dressed up as a reading.
13
13
  - Fitness — what disqualifies a frame
14
14
  - Worst-case data before the capture
15
15
  - Capture is tool-agnostic
16
+ - Engine order — WebKit (Safari) first
16
17
  - Visual evidence is its own class — do not launder others into it
17
18
  - Rendered copy — the design/copywriting seam
18
19
 
@@ -33,6 +34,7 @@ screenshot with no record is an image, not evidence:
33
34
  | `motion` | reduced or full — a still of an animated surface says which |
34
35
  | `captured-at` | ISO-8601 UTC, so staleness is computable |
35
36
  | `source` | the capability that took it (see below) — never assumed |
37
+ | `engine` | the rendering engine behind it — WebKit, Chromium or Gecko; a frame from one engine says nothing about another |
36
38
 
37
39
  ## Fitness — what disqualifies a frame
38
40
 
@@ -75,6 +77,32 @@ not fail because one specific tool is absent, and it does not install a tool to
75
77
  manufacture a pass. If no capability is present, that is the `unverified` case
76
78
  above, stated plainly.
77
79
 
80
+ <a id="engine-order"></a>
81
+ ## Engine order — WebKit (Safari) first
82
+
83
+ Which tool takes the frame is open; which engine renders it first is not.
84
+ **Check a rendered surface in WebKit first.** Its support envelope is the
85
+ narrowest of the three big engines, so a pass there is the stricter claim.
86
+
87
+ | Need | WebKit route (first) |
88
+ |---|---|
89
+ | a real browser, driven | Safari through `safaridriver` (WebDriver); enable remote automation once with `sudo safaridriver --enable` |
90
+ | automation and captures | Playwright's `webkit` — the `webkit` project, `--browser webkit`, installed with `npx playwright install webkit` |
91
+ | debugging a render | Safari Web Inspector |
92
+ | opening a page by hand on macOS | `open -a Safari <url>` — not the system default browser, which may be another engine |
93
+ | an automation library (browser-use and the like) | its WebKit/Safari backend, where it has one |
94
+
95
+ **Chromium is a stated fallback, never the default.** Use it only when the task
96
+ needs Chrome itself — a Chrome-only API, Lighthouse, a CDP trace, the
97
+ chrome-devtools MCP — and say which and why in the record. Prefer the Chrome Dev
98
+ build for that run. When you launch your own Chrome or Chromium for a UI run,
99
+ give it a temporary profile (never the user's), record what you started, and
100
+ close every process you started before you finish.
101
+
102
+ A surface checked only in Chromium is reported as exactly that — `engine:
103
+ Chromium`, "checked only in Chromium" — never as "tested in a browser". Where
104
+ the claim is about cross-engine behaviour, both engines appear in the record.
105
+
78
106
  ## Visual evidence is its own class — do not launder others into it
79
107
 
80
108
  Four kinds of evidence answer different questions, and one may not be relabelled