[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72S7ZXA4V6EC9NQ4F1B5QJS":3,"skill-same:01M72S7ZXA4V6EC9NQ4F1B5QJS":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},"01M72S7ZXA4V6EC9NQ4F1B5QJS","fs-skia-layout-readability",null,"Work on generated game HUD\u002Fstatus layout readability, gameplay-region bounds, and public scene\u002Fhost\u002Fupdate naming guidance.","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-layout-readability\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: fs-skia-layout-readability\ndescription: Work on generated game HUD\u002Fstatus layout readability, gameplay-region bounds, and public scene\u002Fhost\u002Fupdate naming guidance.\n---\n\n# FS Skia Layout Readability Capability\n\n## Scope\n\nUse this skill for tasks that change generated game HUD\u002Fstatus layout,\ngameplay-region bounds, readable-layout proof, generated layout validation, or\npublic scene\u002Fhost\u002Fupdate naming guidance. This is the **layout-design** half of\nthe former `fs-skia-layout-evidence` skill; the deterministic-evidence-mode and\nhost-warning-classification half lives in `fs-skia-evidence-mode`.\n\nSuch tasks must declare `fs-skia-layout-readability` in `tasks.deps.yml` and\nmirror it on the matching `tasks.md` line. Resolve this skill before\nimplementation starts and record the resolved path in the active feature's\nreadiness evidence.\n\n## Public Contract\n\nPublic evidence contracts must start in `.fsi` files before implementation.\nReadable-layout evidence must report HUD region, gameplay region, text or entity\nbounds, and overlap status.\n\nUse the `ReadableLayout` proof level only when HUD region, gameplay region, HUD\ntext bounds, gameplay entity bounds, and non-overlap diagnostics are all\npresent. When only render hashes or scene metadata exist — not readability —\ndefer to `fs-skia-evidence-mode` and its `DeterministicRenderOnly` level.\n\nPublic guidance must use app-owned names when showing consumer signatures or\ntests:\n\n- `Product.Program.view` for the scene-returning function.\n- `Product.Program.generatedHost` for the generated host value.\n- `Product.Program.update` for reducer tests or signatures.\n\n## Runnable example\n\nCapture and assert scene layout bounds against the readable-layout contract. The\ndriven surface is the Layout\u002FScene product packages; an evidence check confirms\nthe HUD region and gameplay entity bounds do not overlap:\n\n```fsharp\nopen FS.Skia.UI.Scene\nopen FS.Skia.UI.Testing\n\n\u002F\u002F Render the app scene and capture readable-layout evidence.\nlet scene = Product.Program.view Product.Program.initialModel\nlet evidence = LayoutEvidence.capture scene\n\n\u002F\u002F Assert reserved HUD region and gameplay entity bounds, then prove non-overlap.\nlet hud = evidence |> LayoutEvidence.requireRegion \"hud\"\nlet gameplay = evidence |> LayoutEvidence.requireRegion \"gameplay\"\nmatch LayoutEvidence.proofLevel evidence with\n| ReadableLayout when not (Bounds.intersects hud gameplay) ->\n    printfn \"ReadableLayout proven: HUD %A clear of gameplay %A\" hud gameplay\n| _ -> failwith \"not readable-layout proof; classify with fs-skia-evidence-mode\"\n```\n\n## HUD \u002F gameplay-region layout pattern\n\nReach the readable-layout proof **by design**, not by gate-driven trial and error.\nThe intended pattern has three parts, applied in order:\n\n1. **Reserve a HUD band.** Carve a fixed-height status\u002FHUD band off one edge of the\n   surface (top or bottom) before placing any gameplay content. The HUD region is a\n   named rectangle (`hud`) whose bounds are derived from the surface size, not from\n   where text happens to land.\n2. **Confine and clamp gameplay to the gameplay region.** The remaining surface after\n   the HUD band is the named `gameplay` region. Every gameplay coordinate —\n   spawning, movement, wrapping, clamping, collision, and active-entity bounds —\n   must be expressed in and clamped to the gameplay region, so entities can never\n   stray under the HUD band. Clamp at the policy boundary, not after rendering.\n3. **Overdraw the HUD last.** Render gameplay first, then draw the HUD band on top, so\n   that even if a transient gameplay frame reaches the band edge the HUD remains\n   legible. Overdraw is the safety net; the clamp in step 2 is the guarantee.\n\nThis pattern makes `ReadableLayout` the natural outcome: the HUD region and gameplay\nregion are distinct named rectangles by construction, and the clamp keeps\n`NoLayoutOverlap` true at both default and constrained sizes. A layout that proves\nreadable only after nudging specific pixel offsets has skipped step 1 or step 2.\n\n### Shipped helper: `FS.Skia.UI.SkillSupport.Hud.reserveHudBand`\n\nEvery arcade demo re-implemented step 1 the same way, so as of feature 062 (FR-010)\nit is **shipped real API** in `FS.Skia.UI.SkillSupport.Hud` — no longer a\nre-derived per-game convention. Reach for it before hand-rolling the band math:\n\n```fsharp\nopen FS.Skia.UI.SkillSupport\n\n\u002F\u002F surface = full extent along the axis (e.g. window height); bandSize = HUD thickness.\nlet layout = Hud.reserveHudBand 600.0 48.0 Hud.Top\n\u002F\u002F layout.HudBand  = { Offset = 0.0;  Size = 48.0  }\n\u002F\u002F layout.Gameplay = { Offset = 48.0; Size = 552.0 }   \u002F\u002F clamp all gameplay to this\n```\n\nIt returns plain `float` bands (no `Scene.Rect` dependency — convert to your own\ngeometry at the call site), clamps `HudBand.Size = min bandSize surface`, and\nguarantees `Gameplay.Size = surface − HudBand.Size ≥ 0` with the two bands\npartitioning the surface. Clamp every gameplay coordinate to `layout.Gameplay`\n(step 2) and overdraw the HUD last (step 3). The reference implementation below\nshows the same split if you need a `Scene.Rect`-typed variant in your own code:\n\n```fsharp\n\u002F\u002F gameplayRegion = surface − reserved band; the band is anchored to one edge.\nlet reserveHudBand (edge: Edge) (bandHeight: float) (surface: Rect) : Rect * Rect =\n    let band, gameplay =\n        match edge with\n        | Edge.Top    -> { surface with Height = bandHeight },\n                         { surface with Y = surface.Y + bandHeight; Height = surface.Height - bandHeight }\n        | Edge.Bottom -> { surface with Y = surface.Bottom - bandHeight; Height = bandHeight },\n                         { surface with Height = surface.Height - bandHeight }\n    band, gameplay   \u002F\u002F name them `hud` \u002F `gameplay`; clamp all gameplay to `gameplay`; overdraw `hud` last\n```\n\nDerive the band height from the surface size (not from where text lands), clamp\nevery gameplay coordinate to the returned `gameplay` rectangle (step 2), and\noverdraw the `hud` rectangle last (step 3). Prefer the shipped\n`Hud.reserveHudBand` above for the band math; this `Rect`-typed form is only the\nreference for a consumer that wants the result already in `Scene.Rect` geometry.\n\n### Shipped helper: `FS.Skia.UI.SkillSupport.Wrap.wrapDeltaX`\n\nToroidal (wrap-around) worlds — Asteroids, Space Invaders, Lunar Lander — kept\nre-deriving the same shortest-wrap-aware delta, so as of feature 063 (FR-010) it is\n**shipped real API** in `FS.Skia.UI.SkillSupport.Wrap`. Reach for it instead of\nhand-rolling the seam arithmetic in your `update`:\n\n```fsharp\nopen FS.Skia.UI.SkillSupport\n\n\u002F\u002F Shortest signed delta from fromX to toX on a toroidal axis of width worldWidth.\nWrap.wrapDeltaX 100.0 90.0 10.0   \u002F\u002F  20.0   (wraps forward across the seam, not -80)\nWrap.wrapDeltaX 100.0 10.0 90.0   \u002F\u002F -20.0   (wraps backward, not +80)\nWrap.wrapDeltaX 100.0 42.0 42.0   \u002F\u002F   0.0   (identity)\n```\n\nIt is pure scalar arithmetic (no state, no I\u002FO, **no `Scene`\u002F`Layout` dependency**, so\nSkillSupport stays dependency-light), deterministic, and returns the signed distance of\nleast magnitude in `(-worldWidth\u002F2, worldWidth\u002F2]`. Thread it through your pure Elmish\n`update` (e.g. camera-relative or AI targeting on a wrap-around world).\n\n### Deferred (documented, not shipped): camera-centered projection\n\nA **camera-centered projection** (world → screen with the camera following the player,\ne.g. `LunarLander1\u002Fsrc\u002FLunarLander1\u002FView.fs:60-61`) recurred too, but it is **documented\nhere and deliberately NOT shipped**. Rationale: it is a *closure* over per-game state\n(player position, view scale, screen center), it returns a `Scene.Point` (a soft `Scene`\ndependency SkillSupport deliberately avoids), and its shape varies per game\n(zoom-centered here, parallax or fixed elsewhere) — it is a `View` concern, not a\nshippable dependency-light scalar helper. **Next-recurrence bar:** ship a camera helper\nonly if a *stable, game-agnostic* projection signature (one that does not pull `Scene`\ninto SkillSupport) recurs across ≥3 demos; until then, write it inline in your `View`.\n\n## Build Commands\n\nPrefer repository targets over ad-hoc command sequences:\n\n```bash\n.\u002Ffake.sh build -t GeneratedGuidanceCheck\n.\u002Ffake.sh build -t GeneratedProductCheck\n.\u002Ffake.sh build -t TemplateCheck\n.\u002Ffake.sh build -t EvidenceGraph\n```\n\n## Generated Product\n\nGenerated game samples that claim readability must reserve a named HUD\u002Fstatus\nregion, keep active gameplay entities in the gameplay region, validate default\nand constrained sizes, and fail when HUD\u002FHUD or HUD\u002Fgameplay overlap is\ndetected. Unsupported host or font\u002Flayout facts must be explicit and must not be\nreported as readable layout proof.\n\nOnce a HUD region is reserved, movement, wrapping, spawning, clamping,\ncollisions, and active entity bounds must use gameplay-region coordinates.\n\nBefore you swap the scaffold game model, read `docs\u002Fscaffold-map.md` — it names\nwhich generated `src\u002FProduct\u002F**` files are durable vs replaceable, the\n`GovernanceTests`-durable \u002F `BehaviorTests`-replaceable split, the must-survive\nsource-scan strings, and the pre-design `fs-skia-scene` record-label-collision\npointer.\n\n## Package Boundary\n\nKeep pure layout classifiers in Scene or Testing contracts. Do not move viewer\nlaunch, filesystem, package restore, process, font host, or window-system\neffects into pure layout helpers. When layout evidence collection needs I\u002FO,\nmodel the request and result explicitly and keep execution at the interpreter or\nbuild-target edge.\n\n## Related\n\n- [[fs-skia-evidence-mode]]\n- [[fs-skia-scene]]\n\n## Sources \u002F links\n\n- F# \u002F .NET documentation: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Ffsharp\u002F\n- Yoga layout reference (flexbox layout engine): https:\u002F\u002Fwww.yogalayout.dev\u002F\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","# FS Skia Layout Readability Capability\n\n## Scope\n\nUse this skill for tasks that change generated game HUD\u002Fstatus layout,\ngameplay-region bounds, readable-layout proof, generated layout validation, or\npublic scene\u002Fhost\u002Fupdate naming guidance. This is the **layout-design** half of\nthe former `fs-skia-layout-evidence` skill; the deterministic-evidence-mode and\nhost-warning-classification half lives in `fs-skia-evidence-mode`.\n\nSuch tasks must declare `fs-skia-layout-readability` in `tasks.deps.yml` and\nmirror it on the matching `tasks.md` line. Resolve this skill before\nimplementation starts and record the resolved path in the active feature's\nreadiness evidence.\n\n## Public Contract\n\nPublic evidence contracts must start in `.fsi` files before implementation.\nReadable-layout evidence must report HUD region, gameplay region, text or entity\nbounds, and overlap status.\n\nUse the `ReadableLayout` proof level only when HUD region, gameplay region, HUD\ntext bounds, gameplay entity bounds, and non-overlap diagnostics are all\npresent. When only render hashes or scene metadata exist — not readability —\ndefer to `fs-skia-evidence-mode` and its `DeterministicRenderOnly` level.\n\nPublic guidance must use app-owned names when showing consumer signatures or\ntests:\n\n- `Product.Program.view` for the scene-returning function.\n- `Product.Program.generatedHost` for the generated host value.\n- `Product.Program.update` for reducer tests or signatures.\n\n## Runnable example\n\nCapture and assert scene layout bounds against the readable-layout contract. The\ndriven surface is the Layout\u002FScene product packages; an evidence check confirms\nthe HUD region and gameplay entity bounds do not overlap:\n\n```fsharp\nopen FS.Skia.UI.Scene\nopen FS.Skia.UI.Testing\n\n\u002F\u002F Render the app scene and capture readable-layout evidence.\nlet scene = Product.Program.view Product.Program.initialModel\nlet evidence = LayoutEvidence.capture scene\n\n\u002F\u002F Assert reserved HUD region and gameplay entity bounds, then prove non-overlap.\nlet hud = evidence |> LayoutEvidence.requireRegion \"hud\"\nlet gameplay = evidence |> LayoutEvidence.requireRegion \"gameplay\"\nmatch LayoutEvidence.proofLevel evidence with\n| ReadableLayout when not (Bounds.intersects hud gameplay) ->\n    printfn \"ReadableLayout proven: HUD %A clear of gameplay %A\" hud gameplay\n| _ -> failwith \"not readable-layout proof; classify with fs-skia-evidence-mode\"\n```\n\n## HUD \u002F gameplay-region layout pattern\n\nReach the readable-layout proof **by design**, not by gate-driven trial and error.\nThe intended pattern has three parts, applied in order:\n\n1. **Reserve a HUD band.** Carve a fixed-height status\u002FHUD band off one edge of the\n   surface (top or bottom) before placing any gameplay content. The HUD region is a\n   named rectangle (`hud`) whose bounds are derived from the surface size, not from\n   where text happens to land.\n2. **Confine and clamp gameplay to the gameplay region.** The remaining surface after\n   the HUD band is the named `gameplay` region. Every gameplay coordinate —\n   spawning, movement, wrapping, clamping, collision, and active-entity bounds —\n   must be expressed in and clamped to the gameplay region, so entities can never\n   stray under the HUD band. Clamp at the policy boundary, not after rendering.\n3. **Overdraw the HUD last.** Render gameplay first, then draw the HUD band on top, so\n   that even if a transient gameplay frame reaches the band edge the HUD remains\n   legible. Overdraw is the safety net; the clamp in step 2 is the guarantee.\n\nThis pattern makes `ReadableLayout` the natural outcome: the HUD region and gameplay\nregion are distinct named rectangles by construction, and the clamp keeps\n`NoLayoutOverlap` true at both default and constrained sizes. A layout that proves\nreadable only after nudging specific pixel offsets has skipped step 1 or step 2.\n\n### Shipped helper: `FS.Skia.UI.SkillSupport.Hud.reserveHudBand`\n\nEvery arcade demo re-implemented step 1 the same way, so as of feature 062 (FR-010)\nit is **shipped real API** in `FS.Skia.UI.SkillSupport.Hud` — no longer a\nre-derived per-game convention. Reach for it before hand-rolling the band math:\n\n```fsharp\nopen FS.Skia.UI.SkillSupport\n\n\u002F\u002F surface = full extent along the axis (e.g. window height); bandSize = HUD thickness.\nlet layout = Hud.reserveHudBand 600.0 48.0 Hud.Top\n\u002F\u002F layout.HudBand  = { Offset = 0.0;  Size = 48.0  }\n\u002F\u002F layout.Gameplay = { Offset = 48.0; Size = 552.0 }   \u002F\u002F clamp all gameplay to this\n```\n\nIt returns plain `float` bands (no `Scene.Rect` dependency — convert to your own\ngeometry at the call site), clamps `HudBand.Size = min bandSize surface`, and\nguarantees `Gameplay.Size = surface − HudBand.Size ≥ 0` with the two bands\npartitioning the surface. Clamp every gameplay coordinate to `layout.Gameplay`\n(step 2) and overdraw the HUD last (step 3). The reference implementation below\nshows the same split if you need a `Scene.Rect`-typed variant in your own code:\n\n```fsharp\n\u002F\u002F gameplayRegion = surface − reserved band; the band is anchored to one edge.\nlet reserveHudBand (edge: Edge) (bandHeight: float) (surface: Rect) : Rect * Rect =\n    let band, gameplay =\n        match edge with\n        | Edge.Top    -> { surface with Height = bandHeight },\n                         { surface with Y = surface.Y + bandHeight; Height = surface.Height - bandHeight }\n        | Edge.Bottom -> { surface with Y = surface.Bottom - bandHeight; Height = bandHeight },\n                         { surface with Height = surface.Height - bandHeight }\n    band, gameplay   \u002F\u002F name them `hud` \u002F `gameplay`; clamp all gameplay to `gameplay`; overdraw `hud` last\n```\n\nDerive the band height from the surface size (not from where text lands), clamp\nevery gameplay coordinate to the returned `gameplay` rectangle (step 2), and\noverdraw the `hud` rectangle last (step 3). Prefer the shipped\n`Hud.reserveHudBand` above for the band math; this `Rect`-typed form is only the\nreference for a consumer that wants the result already in `Scene.Rect` geometry.\n\n### Shipped helper: `FS.Skia.UI.SkillSupport.Wrap.wrapDeltaX`\n\nToroidal (wrap-around) worlds — Asteroids, Space Invaders, Lunar Lander — kept\nre-deriving the same shortest-wrap-aware delta, so as of feature 063 (FR-010) it is\n**shipped real API** in `FS.Skia.UI.SkillSupport.Wrap`. Reach for it instead of\nhand-rolling the seam arithmetic in your `update`:\n\n```fsharp\nopen FS.Skia.UI.SkillSupport\n\n\u002F\u002F Shortest signed delta from fromX to toX on a toroidal axis of width worldWidth.\nWrap.wrapDeltaX 100.0 90.0 10.0   \u002F\u002F  20.0   (wraps forward across the seam, not -80)\nWrap.wrapDeltaX 100.0 10.0 90.0   \u002F\u002F -20.0   (wraps backward, not +80)\nWrap.wrapDeltaX 100.0 42.0 42.0   \u002F\u002F   0.0   (identity)\n```\n\nIt is pure scalar arithmetic (no state, no I\u002FO, **no `Scene`\u002F`Layout` dependency**, so\nSkillSupport stays dependency-light), deterministic, and returns the signed distance of\nleast magnitude in `(-worldWidth\u002F2, worldWidth\u002F2]`. Thread it through your pure Elmish\n`update` (e.g. camera-relative or AI targeting on a wrap-around world).\n\n### Deferred (documented, not shipped): camera-centered projection\n\nA **camera-centered projection** (world → screen with the camera following the player,\ne.g. `LunarLander1\u002Fsrc\u002FLunarLander1\u002FView.fs:60-61`) recurred too, but it is **documented\nhere and deliberately NOT shipped**. Rationale: it is a *closure* over per-game state\n(player position, view scale, screen center), it returns a `Scene.Point` (a soft `Scene`\ndependency SkillSupport deliberately avoids), and its shape varies per game\n(zoom-centered here, parallax or fixed elsewhere) — it is a `View` concern, not a\nshippable dependency-light scalar helper. **Next-recurrence bar:** ship a camera helper\nonly if a *stable, game-agnostic* projection signature (one that does not pull `Scene`\ninto SkillSupport) recurs across ≥3 demos; until then, write it inline in your `View`.\n\n## Build Commands\n\nPrefer repository targets over ad-hoc command sequences:\n\n```bash\n.\u002Ffake.sh build -t GeneratedGuidanceCheck\n.\u002Ffake.sh build -t GeneratedProductCheck\n.\u002Ffake.sh build -t TemplateCheck\n.\u002Ffake.sh build -t EvidenceGraph\n```\n\n## Generated Product\n\nGenerated game samples that claim readability must reserve a named HUD\u002Fstatus\nregion, keep active gameplay entities in the gameplay region, validate default\nand constrained sizes, and fail when HUD\u002FHUD or HUD\u002Fgameplay overlap is\ndetected. Unsupported host or font\u002Flayout facts must be explicit and must not be\nreported as readable layout proof.\n\nOnce a HUD region is reserved, movement, wrapping, spawning, clamping,\ncollisions, and active entity bounds must use gameplay-region coordinates.\n\nBefore you swap the scaffold game model, read `docs\u002Fscaffold-map.md` — it names\nwhich generated `src\u002FProduct\u002F**` files are durable vs replaceable, the\n`GovernanceTests`-durable \u002F `BehaviorTests`-replaceable split, the must-survive\nsource-scan strings, and the pre-design `fs-skia-scene` record-label-collision\npointer.\n\n## Package Boundary\n\nKeep pure layout classifiers in Scene or Testing contracts. Do not move viewer\nlaunch, filesystem, package restore, process, font host, or window-system\neffects into pure layout helpers. When layout evidence collection needs I\u002FO,\nmodel the request and result explicitly and keep execution at the interpreter or\nbuild-target edge.\n\n## Related\n\n- [[fs-skia-evidence-mode]]\n- [[fs-skia-scene]]\n\n## Sources \u002F links\n\n- F# \u002F .NET documentation: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Ffsharp\u002F\n- Yoga layout reference (flexbox layout engine): https:\u002F\u002Fwww.yogalayout.dev\u002F\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",{"name":5,"description":7},"main","f943406829a9218b2882e09eb88d4ddb539c5e72",".agents\u002Fskills\u002Ffs-skia-layout-readability",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-layout-readability",{"tool":36,"command":37},"bunx","bunx skills add EHotwagner\u002FFS-Skia-UI --skill fs-skia-layout-readability",{"tool":39,"command":40},"pnpm","pnpm dlx skills add EHotwagner\u002FFS-Skia-UI --skill fs-skia-layout-readability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffs-skia-layout-readability\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",[],[]]