[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SC0NPJWD1JAR3GZCWT9C0":3,"skill-same:01M72SC0NPJWD1JAR3GZCWT9C0":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},"01M72SC0NPJWD1JAR3GZCWT9C0","fs-skia-evidence-mode",null,"Deterministic render-only evidence mode, visual-proof honesty, and benign\u002Fblocking host-warning classification.","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.claude\u002Fskills\u002Ffs-skia-evidence-mode\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: fs-skia-evidence-mode\ndescription: Deterministic render-only evidence mode, visual-proof honesty, and benign\u002Fblocking host-warning classification.\n---\n\n# FS Skia Evidence Mode Capability\n\n## Scope\n\nUse this skill for tasks that change deterministic render-only evidence, visual\nevidence honesty, fallback classification, or readiness host-warning\nclassification. This is the **evidence-discipline** half of the former\n`fs-skia-layout-evidence` skill; the generated-HUD\u002Flayout-readability half lives\nin `fs-skia-layout-readability`.\n\nSuch tasks must declare `fs-skia-evidence-mode` in `tasks.deps.yml` and mirror it\non the matching `tasks.md` line. Resolve this skill before implementation starts\nand record the resolved path in the active feature's readiness evidence.\n\n## Public Contract\n\nPublic evidence contracts must start in `.fsi` files before implementation. Keep\ndeterministic render metadata separate from readable layout proof. Use explicit\nproof levels:\n\n- `DeterministicRenderOnly` for hashes, scene metadata, or render readback that\n  does not prove readability.\n- `UnsupportedLayoutInspection` when host, font, or public API facts cannot be\n  produced. Unsupported facts must be actionable and must not be converted into\n  readability proof.\n\nReadable-layout proof itself (the `ReadableLayout` level) belongs to\n`fs-skia-layout-readability`; this skill governs what is **not** readable proof.\n\n## Runnable example\n\nClassify render evidence honestly: a render hash is deterministic-render-only and\nmust never be reported as readable layout.\n\n```fsharp\nopen FS.Skia.UI.Scene\nopen FS.Skia.UI.Testing\n\nlet scene = Product.Program.view Product.Program.initialModel\nlet evidence = LayoutEvidence.capture scene\n\nmatch LayoutEvidence.proofLevel evidence with\n| DeterministicRenderOnly -> printfn \"render hash only; not readable-layout proof\"\n| UnsupportedLayoutInspection -> failwith \"unsupported layout inspection: facts not actionable\"\n| _ -> () \u002F\u002F readable layout is proven and classified by fs-skia-layout-readability\n```\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 EvidenceGraph\n.\u002Ffake.sh build -t EvidenceAudit\n```\n\n## Evidence\n\nReadiness evidence for this capability belongs under the active feature's\n`readiness\u002F` directory and must state whether it proves deterministic rendering\nonly or unsupported layout inspection.\n\nWarning classification evidence must preserve real `LaunchFailure`,\n`RenderingFailure`, `LayoutFailure`, and `PackageFailure` diagnostics even when\nknown benign environment warnings are present.\n\nVisual evidence honesty requires screenshot proof, rasterized scene proof,\nlayout readability proof, fallback classification, and unsupported proof to be\nseparate. Accepted visual proof names a decodable image, image dimensions,\nnon-trivial content, renderer mode, fallback classification, and\nunsupported reason.\n\u003C!-- BEGIN GENERATED: gov\u002Fvisual-proof-phrases -->\nExact visual proof rejection phrases for scans: metadata-only reports do not satisfy visual proof; 1x1 fallback images do not satisfy visual proof; layout-only bounds claims do not satisfy visual proof.\n\u003C!-- END GENERATED: gov\u002Fvisual-proof-phrases -->\n\nAsteroids feedback findings must be classified by owner (framework runtime,\ngenerated template workflow, documentation discoverability, consumer authoring),\nand host feedback must distinguish persistent-window blocking, display\u002Fsession\navailability, auto-close smoke needs, benign warning, blocking warning, deferred\nwarning, and name-collision guidance.\n\u003C!-- BEGIN GENERATED: gov\u002Fowner-phrases -->\nExact owner phrases for scans: framework runtime; generated template workflow; documentation discoverability; consumer authoring; persistent-window blocking; display\u002Fsession availability; auto-close smoke; benign warning; blocking warning; deferred warning; name-collision guidance.\n\u003C!-- END GENERATED: gov\u002Fowner-phrases -->\n\n## Evidence token parsing reads `key=value` lines, NOT tables (feature 085, FR-015)\n\nThe readiness validators (window-visibility, readiness-contract, generated-validation, the\naudit-status region) read machine-readable tokens **only from `key=value` lines** — e.g.\n`window-visible=observed:true`, `exact-package-match=true`, `verdict=...`. A markdown **table**\nthat carries the same token names in cells (`| window-visible | observed:true |`) does **not**\nsatisfy the validators — the token must appear as a bare `key=value` line. Put the authoritative\ntokens as `key=value` lines (tables are fine as *human-readable supplements alongside* them, never\nas the sole carrier). The exact required-token list per evidence class is single-sourced in\n`docs\u002Fevidence-formats.md` (generated from `FS.Skia.UI.Build.Evidence.EvidenceFormatSchema`; read\nit before authoring, and regenerate via `.\u002Ffake.sh build -t RefreshSurfaceBaselines` — never hand-edit).\n\n## `--evidence-run` deterministic-summary discipline (documented, not a shipped helper)\n\nGenerated games expose an `--evidence-run` command that drives the **pure** model\nthrough a fixed, per-frame **held-input script** and prints a deterministic summary.\nThe reusable value is the **discipline**, not a shared function — follow it whenever you\nadd or change an `--evidence-run` summary:\n\n- Drive only the **pure** model\u002Fupdate with a fixed seed and a deterministic per-frame\n  held-input script (no wall-clock, no RNG outside the seeded generator, no host I\u002FO).\n- Format every float with `InvariantCulture` and a fixed precision (e.g. `F3`) so the\n  summary is byte-identical across machines and locales.\n- Emit a `determinism=byte-identical` marker plus the stable core fields\n  `status` \u002F `command` \u002F `seed` \u002F `frame-count` \u002F `score`, then the game-specific fields.\n\nCanonical examples: `LunarLander1` `EvidenceCommands.fs:603-672` emits physics state\n(`final-position` \u002F `final-velocity` \u002F `final-rotation` \u002F `final-fuel`, `F3`);\n`AsteroidsDemo3` `EvidenceCommands.fs:670-685` emits entity counts\n(`wave` \u002F `lives` \u002F `asteroid-count` \u002F `bullet-count`) and availability probes.\n\n**Why this is documented, not shipped (FR-009 deferral).** A four-game comparison\n(LunarLander, Asteroids, Breakout, SpaceInvaders) shows the **field set varies\nmaterially per game**; the only stable core is\n`status`\u002F`command`\u002F`seed`\u002F`frame-count`\u002F`score`\u002F`determinism` — too thin to justify a\nshipped record that every consumer then appends 5–10 game-specific fields to. The\n*discipline* recurs; the *summary shape* does not. **Next-recurrence bar:** ship a\nreusable summary type only if a stable cross-game field set (beyond that thin core)\nemerges; until then, write the summary inline and follow the discipline above.\n\n## Responds-vs-renders runtime proof (feature 090, FR-006\u002FFR-007)\n\nAn **interactive-UI story** — one whose acceptance involves driving a live host with\npointer\u002Fkeyboard — is not done until it produces a **responds-proof**: a captured\n**input→visible-change** on the running host, where the rendered output **before** a real\ndispatched interaction differs from the output **after** it. This is a **distinct evidence\nclass**. It is **not** satisfied by a render-only screenshot of a single frame, nor by an\noffscreen route probe (`runInteractivePointerOnce`) that exercises only the model layer. An\napp that **renders but does not respond** yields identical before\u002Fafter frames and an\n`Inert` verdict — it **cannot** pass this proof, so an inert \"green-everything-but-dead-window\"\nbuild can no longer ship as done.\n\nCapture the artifact pair plus the verdict under the feature's\n`readiness\u002Fresponds-proof\u002F\u003Ccase>\u002F` (a `before` and an `after` frame, plus a\n`responds-proof.txt` carrying a bare `verdict=Responsive` token). No live Vulkan window is\nrequired — the before\u002Fafter frames are honest render-only captures\n(`ControlsElmish.captureRespondsProof` reuses the production `Control.renderTree` path). This\nproof **extends**, not replaces, the production-render-path screenshot rule: renders-vs-responds\nis the gate that distinguishes \"it draws\" from \"it reacts.\"\n\n## Package Boundary\n\nKeep pure evidence classifiers in Scene or Testing contracts. Do not move viewer\nlaunch, filesystem, package restore, process, font host, or window-system\neffects into pure validation helpers. When host warning classification or\nevidence collection needs I\u002FO, model the request and result explicitly and keep\nexecution at the interpreter or build-target edge.\n\n## Related\n\n- [[fs-skia-layout-readability]]\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- SkiaSharp API reference: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fapi\u002Fskiasharp\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 Evidence Mode Capability\n\n## Scope\n\nUse this skill for tasks that change deterministic render-only evidence, visual\nevidence honesty, fallback classification, or readiness host-warning\nclassification. This is the **evidence-discipline** half of the former\n`fs-skia-layout-evidence` skill; the generated-HUD\u002Flayout-readability half lives\nin `fs-skia-layout-readability`.\n\nSuch tasks must declare `fs-skia-evidence-mode` in `tasks.deps.yml` and mirror it\non the matching `tasks.md` line. Resolve this skill before implementation starts\nand record the resolved path in the active feature's readiness evidence.\n\n## Public Contract\n\nPublic evidence contracts must start in `.fsi` files before implementation. Keep\ndeterministic render metadata separate from readable layout proof. Use explicit\nproof levels:\n\n- `DeterministicRenderOnly` for hashes, scene metadata, or render readback that\n  does not prove readability.\n- `UnsupportedLayoutInspection` when host, font, or public API facts cannot be\n  produced. Unsupported facts must be actionable and must not be converted into\n  readability proof.\n\nReadable-layout proof itself (the `ReadableLayout` level) belongs to\n`fs-skia-layout-readability`; this skill governs what is **not** readable proof.\n\n## Runnable example\n\nClassify render evidence honestly: a render hash is deterministic-render-only and\nmust never be reported as readable layout.\n\n```fsharp\nopen FS.Skia.UI.Scene\nopen FS.Skia.UI.Testing\n\nlet scene = Product.Program.view Product.Program.initialModel\nlet evidence = LayoutEvidence.capture scene\n\nmatch LayoutEvidence.proofLevel evidence with\n| DeterministicRenderOnly -> printfn \"render hash only; not readable-layout proof\"\n| UnsupportedLayoutInspection -> failwith \"unsupported layout inspection: facts not actionable\"\n| _ -> () \u002F\u002F readable layout is proven and classified by fs-skia-layout-readability\n```\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 EvidenceGraph\n.\u002Ffake.sh build -t EvidenceAudit\n```\n\n## Evidence\n\nReadiness evidence for this capability belongs under the active feature's\n`readiness\u002F` directory and must state whether it proves deterministic rendering\nonly or unsupported layout inspection.\n\nWarning classification evidence must preserve real `LaunchFailure`,\n`RenderingFailure`, `LayoutFailure`, and `PackageFailure` diagnostics even when\nknown benign environment warnings are present.\n\nVisual evidence honesty requires screenshot proof, rasterized scene proof,\nlayout readability proof, fallback classification, and unsupported proof to be\nseparate. Accepted visual proof names a decodable image, image dimensions,\nnon-trivial content, renderer mode, fallback classification, and\nunsupported reason.\n\u003C!-- BEGIN GENERATED: gov\u002Fvisual-proof-phrases -->\nExact visual proof rejection phrases for scans: metadata-only reports do not satisfy visual proof; 1x1 fallback images do not satisfy visual proof; layout-only bounds claims do not satisfy visual proof.\n\u003C!-- END GENERATED: gov\u002Fvisual-proof-phrases -->\n\nAsteroids feedback findings must be classified by owner (framework runtime,\ngenerated template workflow, documentation discoverability, consumer authoring),\nand host feedback must distinguish persistent-window blocking, display\u002Fsession\navailability, auto-close smoke needs, benign warning, blocking warning, deferred\nwarning, and name-collision guidance.\n\u003C!-- BEGIN GENERATED: gov\u002Fowner-phrases -->\nExact owner phrases for scans: framework runtime; generated template workflow; documentation discoverability; consumer authoring; persistent-window blocking; display\u002Fsession availability; auto-close smoke; benign warning; blocking warning; deferred warning; name-collision guidance.\n\u003C!-- END GENERATED: gov\u002Fowner-phrases -->\n\n## Evidence token parsing reads `key=value` lines, NOT tables (feature 085, FR-015)\n\nThe readiness validators (window-visibility, readiness-contract, generated-validation, the\naudit-status region) read machine-readable tokens **only from `key=value` lines** — e.g.\n`window-visible=observed:true`, `exact-package-match=true`, `verdict=...`. A markdown **table**\nthat carries the same token names in cells (`| window-visible | observed:true |`) does **not**\nsatisfy the validators — the token must appear as a bare `key=value` line. Put the authoritative\ntokens as `key=value` lines (tables are fine as *human-readable supplements alongside* them, never\nas the sole carrier). The exact required-token list per evidence class is single-sourced in\n`docs\u002Fevidence-formats.md` (generated from `FS.Skia.UI.Build.Evidence.EvidenceFormatSchema`; read\nit before authoring, and regenerate via `.\u002Ffake.sh build -t RefreshSurfaceBaselines` — never hand-edit).\n\n## `--evidence-run` deterministic-summary discipline (documented, not a shipped helper)\n\nGenerated games expose an `--evidence-run` command that drives the **pure** model\nthrough a fixed, per-frame **held-input script** and prints a deterministic summary.\nThe reusable value is the **discipline**, not a shared function — follow it whenever you\nadd or change an `--evidence-run` summary:\n\n- Drive only the **pure** model\u002Fupdate with a fixed seed and a deterministic per-frame\n  held-input script (no wall-clock, no RNG outside the seeded generator, no host I\u002FO).\n- Format every float with `InvariantCulture` and a fixed precision (e.g. `F3`) so the\n  summary is byte-identical across machines and locales.\n- Emit a `determinism=byte-identical` marker plus the stable core fields\n  `status` \u002F `command` \u002F `seed` \u002F `frame-count` \u002F `score`, then the game-specific fields.\n\nCanonical examples: `LunarLander1` `EvidenceCommands.fs:603-672` emits physics state\n(`final-position` \u002F `final-velocity` \u002F `final-rotation` \u002F `final-fuel`, `F3`);\n`AsteroidsDemo3` `EvidenceCommands.fs:670-685` emits entity counts\n(`wave` \u002F `lives` \u002F `asteroid-count` \u002F `bullet-count`) and availability probes.\n\n**Why this is documented, not shipped (FR-009 deferral).** A four-game comparison\n(LunarLander, Asteroids, Breakout, SpaceInvaders) shows the **field set varies\nmaterially per game**; the only stable core is\n`status`\u002F`command`\u002F`seed`\u002F`frame-count`\u002F`score`\u002F`determinism` — too thin to justify a\nshipped record that every consumer then appends 5–10 game-specific fields to. The\n*discipline* recurs; the *summary shape* does not. **Next-recurrence bar:** ship a\nreusable summary type only if a stable cross-game field set (beyond that thin core)\nemerges; until then, write the summary inline and follow the discipline above.\n\n## Responds-vs-renders runtime proof (feature 090, FR-006\u002FFR-007)\n\nAn **interactive-UI story** — one whose acceptance involves driving a live host with\npointer\u002Fkeyboard — is not done until it produces a **responds-proof**: a captured\n**input→visible-change** on the running host, where the rendered output **before** a real\ndispatched interaction differs from the output **after** it. This is a **distinct evidence\nclass**. It is **not** satisfied by a render-only screenshot of a single frame, nor by an\noffscreen route probe (`runInteractivePointerOnce`) that exercises only the model layer. An\napp that **renders but does not respond** yields identical before\u002Fafter frames and an\n`Inert` verdict — it **cannot** pass this proof, so an inert \"green-everything-but-dead-window\"\nbuild can no longer ship as done.\n\nCapture the artifact pair plus the verdict under the feature's\n`readiness\u002Fresponds-proof\u002F\u003Ccase>\u002F` (a `before` and an `after` frame, plus a\n`responds-proof.txt` carrying a bare `verdict=Responsive` token). No live Vulkan window is\nrequired — the before\u002Fafter frames are honest render-only captures\n(`ControlsElmish.captureRespondsProof` reuses the production `Control.renderTree` path). This\nproof **extends**, not replaces, the production-render-path screenshot rule: renders-vs-responds\nis the gate that distinguishes \"it draws\" from \"it reacts.\"\n\n## Package Boundary\n\nKeep pure evidence classifiers in Scene or Testing contracts. Do not move viewer\nlaunch, filesystem, package restore, process, font host, or window-system\neffects into pure validation helpers. When host warning classification or\nevidence collection needs I\u002FO, model the request and result explicitly and keep\nexecution at the interpreter or build-target edge.\n\n## Related\n\n- [[fs-skia-layout-readability]]\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- SkiaSharp API reference: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fapi\u002Fskiasharp\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",".claude\u002Fskills\u002Ffs-skia-evidence-mode",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-evidence-mode",{"tool":36,"command":37},"bunx","bunx skills add EHotwagner\u002FFS-Skia-UI --skill fs-skia-evidence-mode",{"tool":39,"command":40},"pnpm","pnpm dlx skills add EHotwagner\u002FFS-Skia-UI --skill fs-skia-evidence-mode","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffs-skia-evidence-mode\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",[],[]]