@xtframe/skills 0.19.1 → 0.19.2

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xtframe/skills",
3
- "version": "0.19.1",
3
+ "version": "0.19.2",
4
4
  "description": "Search for XTFrame agent skills and install them, with the XTFrame converter, into every coding agent on this machine (Claude Code, Codex, Gemini CLI, Copilot, Cursor, OpenCode, ...).",
5
5
  "type": "module",
6
6
  "bin": {
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xtframe",
3
- "version": "0.19.1",
3
+ "version": "0.19.2",
4
4
  "description": "XTFrame game UI skills: make a UI from a board (xtui) and change a UI open in the XTFrame editor (xtui-editor).",
5
5
  "author": {
6
6
  "name": "XTFrame"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xtframe",
3
- "version": "0.19.1",
3
+ "version": "0.19.2",
4
4
  "description": "XTFrame game UI skills: make a UI from a board (xtui) and change a UI open in the XTFrame editor (xtui-editor).",
5
5
  "skills": "./skills/",
6
6
  "interface": {
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "name": "xtframe",
3
- "version": "0.19.1",
3
+ "version": "0.19.2",
4
4
  "description": "XTFrame game UI skills: make a UI from a board (xtui) and change a UI open in the XTFrame editor (xtui-editor)."
5
5
  }
@@ -275,23 +275,27 @@ DOM only exists in the browser, so they are dropped), and `<sc-for>` / `<sc-if>`
275
275
  `grayscale()`, `hue-rotate()`, `invert()`, `sepia()`, `opacity()` and `drop-shadow()`.
276
276
  The colour functions merge into one adjustment applied in a fixed order (brightness, contrast,
277
277
  saturate/grayscale, hue-rotate, invert, sepia, opacity), not in the order written; each may appear
278
- only once. Every other filter function is dropped. They are not CSS's colour matrices
279
- (18 §18.3, kept by 18 §18.13): `brightness()` is **additive** in XTFrame and `hue-rotate()` is a
280
- YIQ hue rotation, so the import reports a `brightness()`/`hue-rotate()` that changes anything as
281
- `degraded` (`brightness(0.4) is multiplicative in CSS but additive here (becomes -0.60)` ...: a
282
- CSS dimming brightness turns the element much darker; dim with a black overlay of opacity
283
- `1 - factor` instead, or lower the element's opacity over a dark backdrop), and an out-of-range
284
- `brightness`/`contrast`/`saturate` is clamped with a finding (24 §24.15.4, T-566a/b records).
285
- Check such an element in a screenshot.
286
- - **`brightness()` is the most damaging trap of a web source.** CSS `brightness(0.4)` multiplies
287
- the colour by 0.4; here it adds -0.6, so a dark background goes black (a converted project lost
288
- seven backgrounds this way) and `brightness(0)` makes a silhouette. To **dim**, never use
289
- `brightness()` below 1: put a black element over the image with `opacity` = 1 - the value
290
- (`brightness(0.4)` -> a black overlay at `opacity: 0.6`), or make the element itself
291
- semi-transparent over a dark backdrop. `brightness(1.6)` washes it to white: for a flash use a
292
- small value (about 1.25) or a glow. `brightness()` and `drop-shadow()` in one `filter` work and
293
- may be keyed together (a silhouette revealed with a rim light): every key lists both, in the
294
- same order; the rim light does not darken with the brightness.
278
+ only once. Every other filter function is dropped. XTFrame's own `brightness` is additive and
279
+ `hue-rotate()` is a YIQ hue rotation (18 §18.3), so a `hue-rotate()` that changes anything is
280
+ reported as `degraded`, and an out-of-range `contrast`/`saturate` is clamped with a finding
281
+ (24 §24.15.4, T-566a/b records).
282
+ - **`filter: brightness()` is converted to look the same as on the web** (18 §18.13 amendment,
283
+ T-824). The import composes the `brightness()` and `contrast()` of one `filter` in the order
284
+ written and writes them as a `contrast` + `brightness` pair: `brightness(0.4)` becomes
285
+ `color-adjust(contrast(-0.6) brightness(-0.75))`, which is CSS's `0.4 * colour`. Between
286
+ `brightness(1/3)` and `brightness(2)` the result matches the web with no finding (the editor's
287
+ panel then shows those two numbers, not the one you wrote). Outside that range:
288
+ `brightness(0)` is black, exact; below 1/3 white stays exact but dark tones turn black sooner than
289
+ on the web (`degraded: below 1/3 the dark tones turn black sooner ...`) -- for a strong dim put
290
+ a black element over it with `opacity` = 1 - the value instead (`brightness(0.2)` -> a black
291
+ overlay at `opacity: 0.8`); above 2 it is clamped to `brightness(2)` with a finding. A `filter`
292
+ that also holds `invert()`, `sepia()` or `opacity()` keeps the old additive conversion
293
+ (`brightness(0.4)` adds -0.6, so a dark background goes black) and says so as `degraded` --
294
+ keep `brightness()` out of such a `filter`. `backdrop-filter: brightness()` is still additive
295
+ with the same finding (`backdrop-blur` has no contrast): do not dim a backdrop with it.
296
+ `brightness()` and `drop-shadow()` in one `filter` work and may be keyed together (a silhouette
297
+ revealed with a rim light): every key lists both, in the same order; the rim light does not
298
+ darken with the brightness. Check such an element in a screenshot.
295
299
  - `clip-path` with `inset()`, `circle()`, `ellipse()` or `polygon()` is supported **statically**
296
300
  (a diagonal split screen: two layers with `polygon(0 0, 58% 0, 42% 100%, 0 100%)` and its
297
301
  complement). It **cannot be animated**: a `clip-path` in a keyframe or a transition is dropped
@@ -461,7 +465,8 @@ transition: <prop|all> <duration> [<easing>] [<delay>]
461
465
  - Naming a `@keyframes` that does not exist is a compile error, not a warning.
462
466
  - Accepted and drawn right (each tried in a converted project): `filter: grayscale(0)` to
463
467
  `grayscale(1)` keyed (a freeze frame going grey); `brightness()` and `drop-shadow()` keyed
464
- together in one `filter`; a looping `@keyframes` animation on the child of an element a timeline
468
+ together in one `filter` (each key's `brightness()` is converted on its own: the keys match the
469
+ web, the frames between them are slightly darker, since the pair is not linear in the factor); a looping `@keyframes` animation on the child of an element a timeline
465
470
  moves; `steps()` with large step counts; a whole-shot `filter: blur(18px)` to `blur(0px)` on a
466
471
  sliding container (a whip pan). Procedural motion of every kind: `references/from-procedural.md`.
467
472
 
@@ -474,7 +479,10 @@ works even when the `<defs>` comes after the shape or sits inside a `<g>`. No `<
474
479
  Gradients must be defined inside the same `<svg>` that uses them; `fx`/`fy` (focal point),
475
480
  `spreadMethod="reflect|repeat"`, and a radial gradient stretched into an ellipse (a non-uniform
476
481
  or skewed `gradientTransform`, or `objectBoundingBox` on a non-square shape) are not supported:
477
- the centre, pad and a circle are used, with a warning. Or upload a PNG. An inline `<svg>` is imported as
482
+ the centre, pad and a circle are used, with a warning. Linear gradients follow any
483
+ `gradientTransform` (skew, non-uniform scale) and a diagonal `objectBoundingBox` gradient on a
484
+ non-square shape as browsers draw them, and `objectBoundingBox` x `gradientTransform` is applied in
485
+ SVG's order for both kinds (T-829, T-830). Or upload a PNG. An inline `<svg>` is imported as
478
486
  an editable vector layer (T-224); `data-xt-vector="file"` asks for a `shared/img/` file instead.
479
487
  Inside `<svg>` tag and attribute names keep their case (`linearGradient`, `viewBox`,
480
488
  `gradientUnits`), and intent tags work on the `<svg>` and on its shapes: a `data-xt-timeline` on
@@ -390,7 +390,9 @@ names below -- e.g. `effect.color-adjust.saturation`, not `saturate`. With the s
390
390
  in the chain use its index, `effect.<i>.<name>`. Every effect also has `enabled`; `color` is its
391
391
  colour; a drop shadow's `offset` keys `offsetX` / `offsetY` as one value (`"<x>px <y>px"`).
392
392
  `brightness` is **additive** (0 = unchanged, -1 = black), unlike CSS `brightness()`, which
393
- multiplies.
393
+ multiplies. The board import writes a `filter: brightness(x)` as the equivalent pair
394
+ `contrast` x - 1 with `brightness` 0.5 - 0.5/x (T-824), so an imported element keys both; to dim
395
+ a layer by hand, lower `contrast` and `brightness` together the same way, or its `opacity`.
394
396
 
395
397
  | Function | Track names (in order) | `color` |
396
398
  |---|---|---|
@@ -35,6 +35,8 @@ and animated.
35
35
  supported, each with a warning: `fx`/`fy` (the centre is used), `spreadMethod="reflect"` /
36
36
  `"repeat"` (pad is used), and elliptical radial gradients -- a `gradientTransform` with
37
37
  non-uniform scale or skew, or `objectBoundingBox` on a non-square shape, draws a circle.
38
+ Linear gradients have none of these limits: skew, non-uniform scale and a diagonal
39
+ `objectBoundingBox` gradient on a non-square shape draw as in a browser (T-829, T-830).
38
40
  6. **Prefer declarative motion to hand-computed keyframes.** Use `path-trim` for strokes that
39
41
  draw on, `transform` / `opacity` on shapes, and `d` keyframes only for real morphs. A morph
40
42
  needs the same number of vertices in every keyframe.
@@ -263,7 +263,7 @@ still happen:
263
263
  | `backdrop-filter` without `blur()`, or with a function other than `blur/saturate/brightness` | dropped + warning |
264
264
  | `vw/vh/rem/em/calc()` | that declaration dropped + warning |
265
265
  | `outline*` | kept (T-325); `dashed`/`dotted`/... become `solid` + warning |
266
- | a `filter()` other than `blur`/`drop-shadow`/`brightness` | dropped + warning |
266
+ | a `filter` function other than `blur`/`drop-shadow` and the colour functions (`references/dialect.md`) | dropped + warning |
267
267
  | `<sc-for>` / `<sc-if>` / `renderVals()` | expanded **once** from `data-props` defaults; script output never appears |
268
268
  | `<dc-import>` / `x-import` components | dropped + warning |
269
269
  | a tag outside the allow list (`table`, `tr`, `td`, ...) | becomes `<div>` + warning (low fidelity) |
@@ -145,8 +145,10 @@ in the `expand` margin outside the box it is below 0 or above 1. `i.boxSize` is
145
145
  in CSS px (no dpr). Effects that stick to the content (a light beam, a glow, scan lines lined up
146
146
  with it) use `local`. A `vec2` parameter is a plain pair of numbers: compare it with `uv` or with
147
147
  `local`, whichever the shader means. `i.texelSize` / `i.layerSize` describe the window in device
148
- pixels. `local` and `boxSize` are 0 on a vector or scene layer (no border box) and on a host whose
149
- shader wrapper predates them. The software renderer never runs a shader -- it applies the
148
+ pixels. On a vector or scene layer (a shape or group inside an `<svg>`) the box is the layer's own
149
+ geometry box in its local space, without the stroke (a group: the union of its shapes; the same box
150
+ an `objectBoundingBox` gradient uses), so the stroke falls outside 0..1. `local` and `boxSize` are 0
151
+ on a layer with no geometry and on a host whose shader wrapper predates them. The software renderer never runs a shader -- it applies the
150
152
  `fallback:` -- so look at a shader with `xtframe-view --headless --renderer wgpu`, not the default
151
153
  software render.
152
154