sheleg-design-skill 1.61.0 → 1.61.2

package/CHANGELOG.md

@@ -1,3 +1,22 @@
+## 1.61.2 — rendered copy is part of visual review
+
+Visual review now inspects headings, hero fragments, captions and labels against
+the project's copy policy, preserving meaningful punctuation and ordinary prose.
+The review records visible text and source-role coverage; a successful linter
+that never checked headings cannot stand in for this review. Copywriting keeps
+ownership of its rules and parser. The existing load trigger and director route
+to one review home, covered by mutation-tested contract probes. These are
+instruction-integrity checks, not measured improvements in model behavior.
+
+## 1.61.1 — the WebGL boundary names who owns the engine
+
+The skill owns particle and WebGL backgrounds tied to scroll, and until now said nothing
+about the engine underneath them — renderer, shaders, glTF assets, character animation —
+which a new family member, `web3d-dev`, now owns. The boundary is stated where a reader
+decides: the *When to Use* line for WebGL backgrounds. (`compatibility` was tried too and
+refused by the front-matter budget — 305 of 256 characters.) The body stays inside the house limit by displacement (4749/4750 tokens):
+two phrases about the video tools were tightened, nothing was removed.
+
 ## 1.61.0 — 17 KB of doctrine no agent could load
 
 `LAYOUT_CRAFT.md`, `TYPE_CRAFT.md`, `KNOWLEDGE_PROVENANCE.md` and `VISUAL_REVIEW.md`

package/kits/deskmate/src/Empty.md

@@ -11,7 +11,7 @@ one control that changes the condition.
 
 ```tsx
 <Empty
-  title="No integrations match “zzq”."
+  title="No integrations match “zzq”"
   detail="Check the spelling, or clear the filter to see all of them."
   action={<Button variant="secondary" size="sm">Clear filter</Button>}
 />

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sheleg-design-skill",
-  "version": "1.61.0",
+  "version": "1.61.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 \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.",
   "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.61.0",
+  "version": "1.61.2",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

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

@@ -367,6 +367,9 @@ direction, or run every lens for a single local correction.
 | **State adaptation** | Walk empty, long-content, error, pending, keyboard and recovery states relevant to the scenario. Separate browser prototype behavior from native platform expectations. | State/viewport identifiers, declared versus walked coverage and explicit simulations. No invented latency or claim that a browser preview proves native behavior. |
 | **Finish** | Revisit the already identified defects and check what the changes introduced. Keep useful details that were already working. Stop when no actionable finding remains or the agreed budget is reached. | Each previous finding is resolved, partial or unresolved, with current captures and any regressions. The number of edits is not a success metric. |
 
+At the copy/design seam, use the [rendered-copy review](VISUAL_REVIEW.md#rendered-copy)
+for visible text roles, project policy, counterexamples and coverage receipts.
+
 Before visual review, check that each capture belongs to the expected build,
 screen, state, viewport and content. A stale screenshot or one taken before an
 overlay opened cannot prove that overlay correct. If the capture cannot be

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

@@ -4,7 +4,7 @@ description: Use when deciding how something LOOKS or MOVES — cinematic landin
 license: MIT
 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.61.0
+  version: 1.61.2
 ---
 
 # SHELEG Design
@@ -62,7 +62,8 @@ cannot produce a conformance row — a receipt where it did is refused, because
 ## When to Use
 
 - Landing/marketing/hero pages where motion is a stated goal; particle or WebGL
-  backgrounds tied to scroll; scroll-linked charts, step flows, rails, parallax
+  backgrounds tied to scroll (3D engine: web3d-dev); scroll-linked charts, step flows,
+  rails, parallax
 - An existing scroll site that feels nervous, janky, or out of phase
 - Product UI needing a locked visual system — dashboards, admin, internal/dev tools,
   tokens, light/dark — **style-pack only**, via [`workbench`](./styles/workbench.md)
@@ -70,8 +71,8 @@ cannot produce a conformance row — a receipt where it did is refused, because
   generated-content and confirmation states ([`AI_PRODUCT_PATTERNS.md`](./AI_PRODUCT_PATTERNS.md))
 - Moving a visual system across the Figma border either way ([`FIGMA_BRIDGE.md`](./FIGMA_BRIDGE.md))
 - Motion that has to leave the page as a rendered file — a launch video, a feature
-  loop, a social cut ([`MOTION_PRODUCTION.md`](./MOTION_PRODUCTION.md)), which also
-  names the two programmatic-video tools and which one to reach for
+  loop, a social cut ([`MOTION_PRODUCTION.md`](./MOTION_PRODUCTION.md)), naming both
+  programmatic-video tools
 
 **Never apply the cinematic motion layer to:** product UI, docs sites, static content
 sites — or any page whose visual system or copy isn't finished yet. Product UI takes
@@ -215,9 +216,9 @@ decision, not a research conclusion:
   [`TYPE_CRAFT.md`](./TYPE_CRAFT.md)) — before composing a page or setting a type
   ramp. The portable half: observed, never dialled — an uncalibrated axis is a
   number nobody can check.
-- **Visual review** ([`VISUAL_REVIEW.md`](./VISUAL_REVIEW.md)) — before a
-  screenshot is offered as evidence. It proves what it is OF, and the wrong frame
-  is the claim this file refuses.
+- **Visual review** ([`VISUAL_REVIEW.md`](./VISUAL_REVIEW.md)) — before accepting a
+  screenshot or rendered copy. Verify the frame, then inspect visible text
+  against project policy.
 - **Where the knowledge came from**
   ([`KNOWLEDGE_PROVENANCE.md`](./KNOWLEDGE_PROVENANCE.md)) — when a rule is
   challenged or copied.

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

@@ -7,6 +7,14 @@ file is the contract a visual claim clears before it is called a *visual-pass*
 — and the line past which "I could not capture it" is stated as **unverified**
 rather than dressed up as a reading.
 
+## Contents
+
+- The capture record
+- Fitness — what disqualifies a frame
+- Capture is tool-agnostic
+- Visual evidence is its own class — do not launder others into it
+- Rendered copy — the design/copywriting seam
+
 ## The capture record
 
 Every visual claim carries the record of what was actually captured. A
@@ -72,3 +80,36 @@ look like a phone, or a design comp of an app screen, is a mockup — calling it
 verified native interface claims a device evidence class it does not hold.
 Native readiness is claimed only from native device evidence, and its absence is
 `unverified`, never inferred from a web capture that resembles the platform.
+
+
+<a id="rendered-copy"></a>
+## Rendered copy — the design/copywriting seam
+
+During visual review, read what the user actually sees: hero eyebrows, headings,
+line-break fragments, captions and labels, including text split across inline
+markup. Compare each role with the **project policy** in the brand pack.
+Copy rules belong to **copywriting** (AT-07 covers terminal full stops in titles
+and labels); design catches mismatches between that policy and the rendered
+composition. It does not invent a second punctuation linter. A project can
+extend the default to hero supporting copy, but ordinary prose keeps its normal
+sentence punctuation. Respect a documented intentional exception.
+
+Keep a small review record: **selector**, role, **visible text**, **viewport**,
+**revision**, policy reference, finding and disposition. Inspect the supported
+narrow and wide layouts: a full sentence may become a misleading fragment when
+split for visual emphasis. A corrected headline needs both the source/generated-copy
+fix and a new capture. Where templates regenerate the text, fix their source too.
+
+| Review probe | Expected review action |
+|---|---|
+| `<h1>Your agents.<br>Your tools.</h1>` under a no-title-period policy | Flag both display fragments, including an inline-styled final word. Check the rendered narrow and wide versions after correcting the source. |
+| A hero paragraph ends in a period | Apply the project's rule for that role. Do not strip ordinary prose because a title rule exists. |
+| `Ready?`, `Dr. Ada`, `v1.2.3`, `https://example.org`, or `Loading…` | Preserve meaningful punctuation in questions, abbreviations, version numbers, URLs and ellipses. Do not use a global replacement. |
+| No runtime capture; the text extractor flattened all headings | Mark the visual claim **unverified**. Repair or report source-role coverage; inspect source provisionally and do not claim a rendered pass. |
+
+A linter's **exit 0** proves only the rules and sources it actually checked.
+Record its coverage and whether those sources preserve the roles above; a flat
+copy export, skipped source glob or token/contrast pass does not demonstrate
+that the visible headlines passed copy review. Route textual findings back
+through copywriting, compare the resulting composition, and record unresolved
+items explicitly. This is a review procedure, not evidence that a model followed it.