[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72S8JA2E6QPWM05HMVJR8NF":3,"skill-same:01M72S8JA2E6QPWM05HMVJR8NF":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72S8JA2E6QPWM05HMVJR8NF","fs-skia-viewer-host",null,"Consumer-facing guide to hosting an interactive FS.Skia.UI app — the keyboard\u002Fpointer input surface, the preview-vs-tree render distinction, and the windowed-fullscreen blur caveat.","EHotwagner\u002FFS-Skia-UI","EHotwagner","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1645484?v=4","01M72S7CTBDPQDQHQJKKHY87K9","01M72S7CVFD0JN82RVX21NFEVC",2,"MIT","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffs-skia-viewer-host\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: fs-skia-viewer-host\ndescription: Consumer-facing guide to hosting an interactive FS.Skia.UI app — the keyboard\u002Fpointer input surface, the preview-vs-tree render distinction, and the windowed-fullscreen blur caveat.\n---\n\n# FS Skia Viewer Host Capability\n\n## Scope \u002F when to use\n\nUse this skill when authoring a **consumer** interactive host for an FS.Skia.UI app: wiring\nkeyboard and pointer input into an MVU loop, rendering a real nested control tree to a window,\nand capturing visible-window evidence. This is the host-usage companion to the package-owned\n`fs-skia-skiaviewer` skill (viewer host contracts) — it covers the **input surface** and the\n**which-renderer** decisions a product makes, not the internal viewer plumbing.\n\n## Public Contract (.fsi)\n\nTwo host front doors exist; pick by whether you need pointer routing:\n\n- **`FS.Skia.UI.SkiaViewer.Viewer.runApp` + `GeneratedAppHost`** — keyboard + tick only;\n  `View: 'model -> SceneNode`. Unchanged, durable (feature 084).\n- **`FS.Skia.UI.Controls.Elmish.ControlsElmish.runInteractiveApp` + `InteractiveAppHost`**\n  (feature 085) — adds a **pointer** seam and a **size-aware** view:\n\n```fsharp\nopen FS.Skia.UI.Scene\nopen FS.Skia.UI.Controls\nopen FS.Skia.UI.Controls.Elmish\nopen FS.Skia.UI.SkiaViewer\n\nlet host : InteractiveAppHost\u003CModel, Msg> =\n    { Init = fun () -> initModel, []\n      Update = fun msg model -> update msg model       \u002F\u002F pure: 'model -> 'model * ViewerEffect list\n      View = fun (size: Size) model -> view size model \u002F\u002F size-aware: returns Control\u003C'msg>\n      Theme = Theme.light\n      MapKey = fun key isDown -> mapKey key isDown      \u002F\u002F keyboard input surface\n      MapPointer = fun interaction -> mapPointer interaction  \u002F\u002F pointer input surface (Click\u002FDrag\u002FScroll…)\n      Tick = fun _ -> None\n      Diagnostics = Viewer.defaultDiagnostics }\n\nControlsElmish.runInteractiveApp\n    { Title = \"App\"\n      InitialSize = { Width = 1024; Height = 768 }\n      PresentMode = ViewerPresentMode.DirectToSwapchain   \u002F\u002F live default (feature 119)\n      FrameRateCap = None }                               \u002F\u002F None = 60 FPS; Some n caps the loop (feature 121)\n    host\n```\n\n### Input surface\n\n- **Keyboard** flows through `MapKey: ViewerKey -> bool -> 'msg option` (same as `GeneratedAppHost`).\n  Toolkit key names like `Number5`\u002F`Digit5`\u002F`Keypad5`\u002F`Key5`\u002F`KeyL` are normalized by\n  `ViewerKeyboard.normalize` to `Digit n` \u002F `Letter X` (feature 085); unknown names stay `Unknown raw`.\n- **Pointer** flows through `MapPointer: PointerInteraction -> 'msg option`. `runInteractiveApp`\n  hit-tests the rendered tree (`Control.renderTree` `Layout` × `EventBindings` by `ControlId`,\n  with the shipped 4px click\u002Fdrag fold via `Pointer.update`) and offers each `PointerInteraction`\n  (`Click`\u002F`PressedDown`\u002F`ReleasedUp`\u002F`DragBegin`\u002F`Scroll`\u002F…) to your `MapPointer`. Match on the\n  `ControlId` to route the bound product message.\n\n## Preview vs tree — `Control.render` is NOT `Control.renderTree`\n\nThis is the most common authoring mistake:\n\n- **`Control.render theme control`** is the Feature-080 **single-control PREVIEW**: it flattens\n  every descendant and stacks them at fixed y-offsets to show *one control's* faithful thumbnail.\n  Use it for catalog\u002Fthumbnail rendering — **not** for a live app screen.\n- **`Control.renderTree theme size control`** (feature 085) runs a **real recursive Yoga layout**\n  at the output `size` and paints nested containers AND their children at their computed bounds.\n  This is what an interactive host renders; `runInteractiveApp` uses it internally. Two\n  structurally different trees produce visibly different scenes.\n\n```fsharp\nlet live = Control.renderTree Theme.light { Width = 1024; Height = 768 } appTree  \u002F\u002F real layout\nlet thumb = Control.render Theme.light singleControl                              \u002F\u002F 080 preview\n```\n\n## Windowed-fullscreen blur caveat + workaround\n\nThe **no-flag default** is windowed fullscreen, which scales a fixed-resolution scene up to the\nmonitor work area and **blurs** it. Two fixes:\n\n1. Use the **size-aware `View: Size -> 'model -> Control\u003C'msg>`** so content is laid out to the\n   actual swapchain extent (sharp at any size) — the preferred path.\n2. Or pass exactly one flag — **`--window-startup normal`** — for a 1:1 normal window.\n\n> These fix **blur**, not the black-frame blink below. The size-aware view does **not** address\n> interleaved-black, and naively filling a large extent with a full grid of controls is an\n> `O(cells)` ANR trap — keep the cell\u002Frow count bounded (virtualize) when you size to the extent.\n\n## Interleaved-black-frame blink — Wayland `DirectToSwapchain` (feature 122)\n\n**Symptom (pre-122).** On a Wayland windowed-fullscreen session with the default\n`DirectToSwapchain` present, a **static** scene could **blink** — fully-black frames interleaved\nwith the painted frame — while offscreen\u002Fscreenshot evidence stayed correct. Root cause: the\nfeature-120 idle optimization skipped the buffer **swap** entirely on an unchanged scene, assuming\ndouble-buffering; a 3+ buffer compositor then rotated an **undrawn (black)** buffer into view.\n\n**Fix (feature 122, shipped).** The host now keeps every swapchain buffer populated: on an idle\nframe it **re-presents the cached last good frame** (a single image blit, no scene walk) for a\nbounded number of frames until all buffers are filled, then fully idles. Static content no longer\ninterleaves black, and the idle CPU win is preserved. No consumer action is required on the current\nframework.\n\n**On older framework versions** (or to force a normal window regardless), pass\n**`--window-startup normal`** — feature 122 also made that flag actually apply to the live\n**controls** window (`runInteractiveAppWithWindowBehavior`), where it was previously inert (it only\nfed the options report). The earlier \"size-aware view\" advice does **not** fix the blink.\n\n## Present mode: live vs evidence — do not reuse the evidence options (feature 121)\n\n`ViewerOptions.PresentMode` picks the present mechanism; choose it by launch context:\n\n| Launch context | `PresentMode` | Why |\n|----------------|---------------|-----|\n| Persistent interactive window | `DirectToSwapchain` | zero-readback live present (feature 119); unchanged frames skip paint (feature 120) |\n| Evidence \u002F screenshot capture | `OffscreenReadback` | small readback surface for deterministic pixel capture |\n\n**Do NOT reuse your evidence `viewerOptions` for the persistent interactive launch.** The\nevidence options set `OffscreenReadback` (640×480), which renders **off-screen** — a live window\nbuilt from them shows a **blank** frame. Give the interactive launch its own `DirectToSwapchain`\noptions (e.g. 1280×800). A generated scaffold that defaults the persistent launch to the evidence\n`viewerOptions` ships a blank window — the exact defect the ControlsShowcase4 feedback hit.\n\n## Loop pacing & the headless free-run environment limit (feature 121)\n\n`ViewerOptions.FrameRateCap : int option` bounds the live persistent loop:\n\n- `None` keeps the default **60 FPS** (the pre-121 behaviour).\n- `Some n` (n > 0) caps **both** the update and the present cadence at `n` FPS — the consumer\n  lever to keep the loop from free-running. `Some n` with `n \u003C= 0` is rejected at startup.\n\n**Desktop-session prerequisites for a responsive window**: a compositor with vsync. On such a\nhost the loop paces on present. On a **minimal\u002Fheadless host with no compositor\u002Fvsync** (e.g. a\nbare GTK session) the loop has nothing to block on and **free-runs toward the cap** — this is an\n**environment limitation, not a product defect**. Lower the `FrameRateCap` to bound CPU there; a\ntruly responsive interactive window still requires a real desktop session.\n\n## Already shipped — don't re-derive these (feature 121 reconciliation)\n\n- **In-app quit needs no new effect.** `update` returns `ViewerEffect list`; return\n  `[ ViewerEffect.CloseWindow ]` to request a graceful shutdown (it propagates to\n  `AppRequestedClose` + `Shutdown`). Wire a plain key to it via `MapKey` — no `kill` required.\n- **Unchanged frames already skip paint.** On `DirectToSwapchain`, a frame whose scene is\n  reference\u002Fstructurally unchanged at an unchanged size does no clear\u002Fscene-walk\u002Fdraw (feature\n  120). You do not need to add idle-skip yourself.\n\n## Keyboard warm-up: no dropped keystrokes at focus (feature 086)\n\nWhen a persistent window first gains focus there is a brief **warm-up window** before the\nrender pipeline signals ready (its first presented frame). Key events that fire in that gap\nused to be dropped. The persistent host now buffers them in a **bounded pre-ready FIFO** and\nflushes them **in capture order** the moment the pipeline is ready, so every keystroke issued\nin the first seconds after focus still reaches your `MapKey`.\n\n- The buffer is **bounded** (capacity 64). Past the cap it **drops the oldest** event and\n  emits a structured `Input`\u002F`Warning` diagnostic — explicit degradation, never silent loss\n  (Principle VII). In practice the cap is never reached: the first frame arrives within a few\n  frames of focus and the buffer drains.\n- After the pipeline is ready, dispatch is **direct** (no buffering), and any residual\n  buffered keys are drained in order before the live key.\n- You do not opt in — it is automatic on the persistent host input path. This only closes the\n  focus-time gap; there is no behavior change once the window is warm.\n\n## Persistent problems\n\nWhen a problem outlasts reasonable in-repo attempts, extensive external research is\n**mandatory** — consult **official online docs first** (the F#\u002F.NET docs and the driven\nlibrary's own documentation\u002FAPI reference), then community sources (forums, Reddit, Q&A\nsites, issue trackers and changelogs). Record the findings and resolving links in the\nfeature's `specs\u002F\u003Cfeature>\u002Ffeedback\u002F` folder and, for durable lessons, in this skill's\n**Sources** line. Offline, the mandate degrades to recording \"research blocked — \u003Cwhy>\"\nrather than hard-failing the phase.\n\n## Related\n\n- [[fs-skia-controls-host]] — the **maintainer-facing** counterpart: what `runInteractiveApp` does\n  internally each frame (the retained structure, per-identity animation clocks, visual-state stamping,\n  focus-first key routing). This skill is the consumer view; that one is the host-internals view.\n- [[fs-skia-skiaviewer]] — the package-owned viewer host contracts this builds on.\n- [[fs-skia-ui-widgets]] — building the `Control\u003C'msg>` tree the host renders.\n- [[fs-skia-elmish]] — the MVU wiring the interactive host follows.\n- [[fs-skia-keyboard-input]] — `ViewerKeyboard.normalize` and the key-name families.\n\n## Sources \u002F links\n\n- F#\u002F.NET docs: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Ffsharp\u002F\n- SkiaSharp (the driven Skia rendering library): https:\u002F\u002Fgithub.com\u002Fmono\u002FSkiaSharp\n","# FS Skia Viewer Host Capability\n\n## Scope \u002F when to use\n\nUse this skill when authoring a **consumer** interactive host for an FS.Skia.UI app: wiring\nkeyboard and pointer input into an MVU loop, rendering a real nested control tree to a window,\nand capturing visible-window evidence. This is the host-usage companion to the package-owned\n`fs-skia-skiaviewer` skill (viewer host contracts) — it covers the **input surface** and the\n**which-renderer** decisions a product makes, not the internal viewer plumbing.\n\n## Public Contract (.fsi)\n\nTwo host front doors exist; pick by whether you need pointer routing:\n\n- **`FS.Skia.UI.SkiaViewer.Viewer.runApp` + `GeneratedAppHost`** — keyboard + tick only;\n  `View: 'model -> SceneNode`. Unchanged, durable (feature 084).\n- **`FS.Skia.UI.Controls.Elmish.ControlsElmish.runInteractiveApp` + `InteractiveAppHost`**\n  (feature 085) — adds a **pointer** seam and a **size-aware** view:\n\n```fsharp\nopen FS.Skia.UI.Scene\nopen FS.Skia.UI.Controls\nopen FS.Skia.UI.Controls.Elmish\nopen FS.Skia.UI.SkiaViewer\n\nlet host : InteractiveAppHost\u003CModel, Msg> =\n    { Init = fun () -> initModel, []\n      Update = fun msg model -> update msg model       \u002F\u002F pure: 'model -> 'model * ViewerEffect list\n      View = fun (size: Size) model -> view size model \u002F\u002F size-aware: returns Control\u003C'msg>\n      Theme = Theme.light\n      MapKey = fun key isDown -> mapKey key isDown      \u002F\u002F keyboard input surface\n      MapPointer = fun interaction -> mapPointer interaction  \u002F\u002F pointer input surface (Click\u002FDrag\u002FScroll…)\n      Tick = fun _ -> None\n      Diagnostics = Viewer.defaultDiagnostics }\n\nControlsElmish.runInteractiveApp\n    { Title = \"App\"\n      InitialSize = { Width = 1024; Height = 768 }\n      PresentMode = ViewerPresentMode.DirectToSwapchain   \u002F\u002F live default (feature 119)\n      FrameRateCap = None }                               \u002F\u002F None = 60 FPS; Some n caps the loop (feature 121)\n    host\n```\n\n### Input surface\n\n- **Keyboard** flows through `MapKey: ViewerKey -> bool -> 'msg option` (same as `GeneratedAppHost`).\n  Toolkit key names like `Number5`\u002F`Digit5`\u002F`Keypad5`\u002F`Key5`\u002F`KeyL` are normalized by\n  `ViewerKeyboard.normalize` to `Digit n` \u002F `Letter X` (feature 085); unknown names stay `Unknown raw`.\n- **Pointer** flows through `MapPointer: PointerInteraction -> 'msg option`. `runInteractiveApp`\n  hit-tests the rendered tree (`Control.renderTree` `Layout` × `EventBindings` by `ControlId`,\n  with the shipped 4px click\u002Fdrag fold via `Pointer.update`) and offers each `PointerInteraction`\n  (`Click`\u002F`PressedDown`\u002F`ReleasedUp`\u002F`DragBegin`\u002F`Scroll`\u002F…) to your `MapPointer`. Match on the\n  `ControlId` to route the bound product message.\n\n## Preview vs tree — `Control.render` is NOT `Control.renderTree`\n\nThis is the most common authoring mistake:\n\n- **`Control.render theme control`** is the Feature-080 **single-control PREVIEW**: it flattens\n  every descendant and stacks them at fixed y-offsets to show *one control's* faithful thumbnail.\n  Use it for catalog\u002Fthumbnail rendering — **not** for a live app screen.\n- **`Control.renderTree theme size control`** (feature 085) runs a **real recursive Yoga layout**\n  at the output `size` and paints nested containers AND their children at their computed bounds.\n  This is what an interactive host renders; `runInteractiveApp` uses it internally. Two\n  structurally different trees produce visibly different scenes.\n\n```fsharp\nlet live = Control.renderTree Theme.light { Width = 1024; Height = 768 } appTree  \u002F\u002F real layout\nlet thumb = Control.render Theme.light singleControl                              \u002F\u002F 080 preview\n```\n\n## Windowed-fullscreen blur caveat + workaround\n\nThe **no-flag default** is windowed fullscreen, which scales a fixed-resolution scene up to the\nmonitor work area and **blurs** it. Two fixes:\n\n1. Use the **size-aware `View: Size -> 'model -> Control\u003C'msg>`** so content is laid out to the\n   actual swapchain extent (sharp at any size) — the preferred path.\n2. Or pass exactly one flag — **`--window-startup normal`** — for a 1:1 normal window.\n\n> These fix **blur**, not the black-frame blink below. The size-aware view does **not** address\n> interleaved-black, and naively filling a large extent with a full grid of controls is an\n> `O(cells)` ANR trap — keep the cell\u002Frow count bounded (virtualize) when you size to the extent.\n\n## Interleaved-black-frame blink — Wayland `DirectToSwapchain` (feature 122)\n\n**Symptom (pre-122).** On a Wayland windowed-fullscreen session with the default\n`DirectToSwapchain` present, a **static** scene could **blink** — fully-black frames interleaved\nwith the painted frame — while offscreen\u002Fscreenshot evidence stayed correct. Root cause: the\nfeature-120 idle optimization skipped the buffer **swap** entirely on an unchanged scene, assuming\ndouble-buffering; a 3+ buffer compositor then rotated an **undrawn (black)** buffer into view.\n\n**Fix (feature 122, shipped).** The host now keeps every swapchain buffer populated: on an idle\nframe it **re-presents the cached last good frame** (a single image blit, no scene walk) for a\nbounded number of frames until all buffers are filled, then fully idles. Static content no longer\ninterleaves black, and the idle CPU win is preserved. No consumer action is required on the current\nframework.\n\n**On older framework versions** (or to force a normal window regardless), pass\n**`--window-startup normal`** — feature 122 also made that flag actually apply to the live\n**controls** window (`runInteractiveAppWithWindowBehavior`), where it was previously inert (it only\nfed the options report). The earlier \"size-aware view\" advice does **not** fix the blink.\n\n## Present mode: live vs evidence — do not reuse the evidence options (feature 121)\n\n`ViewerOptions.PresentMode` picks the present mechanism; choose it by launch context:\n\n| Launch context | `PresentMode` | Why |\n|----------------|---------------|-----|\n| Persistent interactive window | `DirectToSwapchain` | zero-readback live present (feature 119); unchanged frames skip paint (feature 120) |\n| Evidence \u002F screenshot capture | `OffscreenReadback` | small readback surface for deterministic pixel capture |\n\n**Do NOT reuse your evidence `viewerOptions` for the persistent interactive launch.** The\nevidence options set `OffscreenReadback` (640×480), which renders **off-screen** — a live window\nbuilt from them shows a **blank** frame. Give the interactive launch its own `DirectToSwapchain`\noptions (e.g. 1280×800). A generated scaffold that defaults the persistent launch to the evidence\n`viewerOptions` ships a blank window — the exact defect the ControlsShowcase4 feedback hit.\n\n## Loop pacing & the headless free-run environment limit (feature 121)\n\n`ViewerOptions.FrameRateCap : int option` bounds the live persistent loop:\n\n- `None` keeps the default **60 FPS** (the pre-121 behaviour).\n- `Some n` (n > 0) caps **both** the update and the present cadence at `n` FPS — the consumer\n  lever to keep the loop from free-running. `Some n` with `n \u003C= 0` is rejected at startup.\n\n**Desktop-session prerequisites for a responsive window**: a compositor with vsync. On such a\nhost the loop paces on present. On a **minimal\u002Fheadless host with no compositor\u002Fvsync** (e.g. a\nbare GTK session) the loop has nothing to block on and **free-runs toward the cap** — this is an\n**environment limitation, not a product defect**. Lower the `FrameRateCap` to bound CPU there; a\ntruly responsive interactive window still requires a real desktop session.\n\n## Already shipped — don't re-derive these (feature 121 reconciliation)\n\n- **In-app quit needs no new effect.** `update` returns `ViewerEffect list`; return\n  `[ ViewerEffect.CloseWindow ]` to request a graceful shutdown (it propagates to\n  `AppRequestedClose` + `Shutdown`). Wire a plain key to it via `MapKey` — no `kill` required.\n- **Unchanged frames already skip paint.** On `DirectToSwapchain`, a frame whose scene is\n  reference\u002Fstructurally unchanged at an unchanged size does no clear\u002Fscene-walk\u002Fdraw (feature\n  120). You do not need to add idle-skip yourself.\n\n## Keyboard warm-up: no dropped keystrokes at focus (feature 086)\n\nWhen a persistent window first gains focus there is a brief **warm-up window** before the\nrender pipeline signals ready (its first presented frame). Key events that fire in that gap\nused to be dropped. The persistent host now buffers them in a **bounded pre-ready FIFO** and\nflushes them **in capture order** the moment the pipeline is ready, so every keystroke issued\nin the first seconds after focus still reaches your `MapKey`.\n\n- The buffer is **bounded** (capacity 64). Past the cap it **drops the oldest** event and\n  emits a structured `Input`\u002F`Warning` diagnostic — explicit degradation, never silent loss\n  (Principle VII). In practice the cap is never reached: the first frame arrives within a few\n  frames of focus and the buffer drains.\n- After the pipeline is ready, dispatch is **direct** (no buffering), and any residual\n  buffered keys are drained in order before the live key.\n- You do not opt in — it is automatic on the persistent host input path. This only closes the\n  focus-time gap; there is no behavior change once the window is warm.\n\n## Persistent problems\n\nWhen a problem outlasts reasonable in-repo attempts, extensive external research is\n**mandatory** — consult **official online docs first** (the F#\u002F.NET docs and the driven\nlibrary's own documentation\u002FAPI reference), then community sources (forums, Reddit, Q&A\nsites, issue trackers and changelogs). Record the findings and resolving links in the\nfeature's `specs\u002F\u003Cfeature>\u002Ffeedback\u002F` folder and, for durable lessons, in this skill's\n**Sources** line. Offline, the mandate degrades to recording \"research blocked — \u003Cwhy>\"\nrather than hard-failing the phase.\n\n## Related\n\n- [[fs-skia-controls-host]] — the **maintainer-facing** counterpart: what `runInteractiveApp` does\n  internally each frame (the retained structure, per-identity animation clocks, visual-state stamping,\n  focus-first key routing). This skill is the consumer view; that one is the host-internals view.\n- [[fs-skia-skiaviewer]] — the package-owned viewer host contracts this builds on.\n- [[fs-skia-ui-widgets]] — building the `Control\u003C'msg>` tree the host renders.\n- [[fs-skia-elmish]] — the MVU wiring the interactive host follows.\n- [[fs-skia-keyboard-input]] — `ViewerKeyboard.normalize` and the key-name families.\n\n## Sources \u002F links\n\n- F#\u002F.NET docs: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Ffsharp\u002F\n- SkiaSharp (the driven Skia rendering library): https:\u002F\u002Fgithub.com\u002Fmono\u002FSkiaSharp\n",{"name":5,"description":7},"main","f943406829a9218b2882e09eb88d4ddb539c5e72",".agents\u002Fskills\u002Ffs-skia-viewer-host",0,"https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI","https:\u002F\u002Fgithub.com\u002FEHotwagner","2026-06-16 16:16:52",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add EHotwagner\u002FFS-Skia-UI --skill fs-skia-viewer-host",{"tool":36,"command":37},"bunx","bunx skills add EHotwagner\u002FFS-Skia-UI --skill fs-skia-viewer-host",{"tool":39,"command":40},"pnpm","pnpm dlx skills add EHotwagner\u002FFS-Skia-UI --skill fs-skia-viewer-host","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffs-skia-viewer-host\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M72SGYR4T02T1HTS175E0V86","fs-skia-ui-widgets","Generated product guidance for Skia-rendered FS.Skia.UI Controls, rich text, chart controls, graph controls, DataGrid, and custom wrappers.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-ui-widgets\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M72SGVZJR1B117QK7TCC6E0J","fs-skia-testing","Assert generated-product expectations and evidence in a governed FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-testing\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M72SGTC5HZYEVVVZT4X51AZ3","fs-skia-skiaviewer","Wire a generated FS.Skia.UI product to the desktop viewer host.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-skiaviewer\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72SGS47RPYPC9JTC39CC6EF","fs-skia-scene","Build pure scene descriptions in a generated FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-scene\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72SGQF4G76C4NGSF69KZRRF","fs-skia-keyboard-input","Map keyboard input to product commands in a generated FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-keyboard-input\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72SGNJP3PMSS2VRP98G7Z42","fs-skia-elmish","Drive a generated FS.Skia.UI product through the pure Elmish adapter.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-elmish\u002FSKILL.md",[],[]]