[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SCZ0QGE3X92P0D31JCZNT":3,"skill-same:01M72SCZ0QGE3X92P0D31JCZNT":57},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72SCZ0QGE3X92P0D31JCZNT","fsdocs-examples",null,"This skill should be used when the user asks to \"write documentation examples\", \"create literate scripts\", \"add fsx docs\", \"write a tutorial\", \"create a how-to guide\", \"add example scripts to docs\", \"write literate F# documentation\", or needs to create `.fsx` literate scripts in the `docs\u002F` directory that teach library usage through executable, narrative-driven examples.","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\u002Ffsdocs-examples\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: fsdocs-examples\ndescription: This skill should be used when the user asks to \"write documentation examples\", \"create literate scripts\", \"add fsx docs\", \"write a tutorial\", \"create a how-to guide\", \"add example scripts to docs\", \"write literate F# documentation\", or needs to create `.fsx` literate scripts in the `docs\u002F` directory that teach library usage through executable, narrative-driven examples.\nversion: 0.1.0\n---\n\n# Write Literate F# Documentation Scripts\n\nCreate `.fsx` literate scripts in `docs\u002F` that teach library usage through executable examples with interleaved narrative.\n\n**Key capabilities:**\n- Create literate `.fsx` files with proper FSharp.Formatting frontmatter\n- Interleave narrative documentation with executable F# code\n- Use directives to control output display (`include-output`, `include-it`, `include-value`)\n- Organize examples by feature and use-case with proper navigation ordering\n\n## Overview\n\nFSharp.Formatting processes `.fsx` files in `docs\u002F` as literate scripts. These combine Markdown narrative (in `(**  **)` doc comments) with executable F# code. When built with `--eval`, the code runs and its output can be captured and displayed in the generated pages.\n\nLiterate scripts are organized by feature or use-case, not by namespace or API surface. They answer \"How do I accomplish X?\" rather than \"What does function Y do?\".\n\n## Workflow\n\n### 1. Identify What to Demonstrate\n\nDetermine the topic: a feature, use-case, pattern, or integration. Each script should focus on one coherent topic. Ask:\n- What problem does this solve for the user?\n- What is the simplest working example?\n- What are the important variations or advanced uses?\n\n### 2. Plan the Narrative Arc\n\nStructure the script as a progressive tutorial:\n1. **Introduction** — what this example covers and why it matters\n2. **Setup** — assembly references, namespace opens, any prerequisite configuration\n3. **Basic usage** — simplest possible working example\n4. **Intermediate patterns** — common variations, composition, error handling\n5. **Advanced usage** — complex scenarios, performance considerations (optional)\n6. **Summary** — recap key points, link to related topics\n\n### 3. Create the .fsx File with Frontmatter\n\nPlace the file in `docs\u002F` with a descriptive name. The first lines must be an fsdocs frontmatter block:\n\n```fsharp\n(**\n---\ntitle: Working with Parsers\ncategory: Tutorials\ncategoryindex: 2\nindex: 3\ndescription: Learn how to build and compose parsers.\n---\n*)\n```\n\nFrontmatter fields:\n- `title` — page title (appears in navigation and browser tab)\n- `category` — navigation group name\n- `categoryindex` — sort order of the category in the sidebar (lower = higher)\n- `index` — sort order within the category (lower = higher)\n- `description` — brief summary for search and metadata\n\n### 4. Write Narrative with Interleaved Code\n\nAlternate between Markdown narrative in `(**  **)` blocks and F# code:\n\n```fsharp\n(**\n## Getting Started\n\nFirst, reference the library and open the namespace:\n*)\n\n#r \"..\u002Fsrc\u002FMyLib\u002Fbin\u002FRelease\u002Fnet8.0\u002FMyLib.dll\"\nopen MyLib.Parsers\n\n(**\nCreate a simple parser that matches a single character:\n*)\n\nlet charParser = Parser.char 'a'\nlet result = Parser.run charParser \"abc\"\n(*** include-it ***)\n```\n\nThe `(*** include-it ***)` directive inserts the FSI evaluation result of the preceding expression.\n\n### 5. Use Output Directives\n\nControl what appears in the rendered page:\n\n| Directive | Effect |\n|---|---|\n| `(*** include-output ***)` | Show `stdout` output from preceding code |\n| `(*** include-it ***)` | Show FSI evaluation result of preceding expression |\n| `(*** include-value: x ***)` | Show the value of a named binding |\n| `(*** include-fsi-output ***)` | Show raw FSI output including types |\n| `(*** hide ***)` | Hide the next code block from rendered output |\n| `(*** do-not-eval ***)` | Show code but skip evaluation |\n| `(*** define: name ***)` | Define a named snippet for later inclusion |\n| `(*** include: name ***)` | Include a previously defined snippet |\n| `(*** condition: prepare ***)` | Only include when building (not in output) |\n| `(*** condition: ipynb ***)` | Only include in notebook output |\n\nPlace output directives **immediately after** the code block they reference. The directive applies to the code block directly above it.\n\n### 6. Add Assembly References\n\nLiterate scripts run as FSI scripts. They need explicit assembly references:\n\n```fsharp\n(*** condition: prepare ***)\n#r \"..\u002Fsrc\u002FMyLib\u002Fbin\u002FRelease\u002Fnet8.0\u002FMyLib.dll\"\n(*** condition: fsx ***)\n#r \"nuget: MyLib\"\n```\n\nUse `condition: prepare` for local development paths and `condition: fsx` for NuGet references shown to the reader. This way the script evaluates with local DLLs but the rendered page shows the NuGet install instruction.\n\n### 7. Verify with Build\n\nBuild with `--eval` to execute the scripts and verify output:\n\n```\ndotnet fsdocs build --clean --eval\n```\n\nCheck that:\n- All scripts compile and evaluate without errors\n- Output directives show expected values\n- Navigation ordering is correct in the generated site\n\n## Writing Good Examples\n\n**Teach one concept per script.** A script about \"parsing\" should not also cover serialization. Create separate scripts for separate topics.\n\n**Build complexity gradually.** Start with the simplest example that works, then layer on complexity. Every code block should build on what came before.\n\n**Show realistic use cases.** Avoid toy examples that don't resemble real usage. If the library parses JSON, parse actual JSON structures, not `\"hello\"`.\n\n**Show expected output.** Use `include-it` or `include-value` after expressions so readers see results. Invisible code that \"just works\" is less helpful than seeing concrete values.\n\n**Handle errors explicitly.** Show what happens with invalid input. Document error cases with the same care as success cases.\n\n**Keep setup minimal.** Use `(*** hide ***)` for boilerplate setup that would distract from the main narrative. But always show assembly references and namespace opens — readers need to know these.\n\n**Cross-reference related pages.** End each script with links to related examples and API docs. This helps readers find the next thing they need.\n\n**Name files descriptively.** Use kebab-case names that describe the content: `working-with-parsers.fsx`, `error-handling.fsx`, `async-patterns.fsx`. Avoid generic names like `tutorial1.fsx`.\n\n## Anatomy of a Literate Script\n\nA complete literate script follows this structure:\n\n```fsharp\n(** Frontmatter block — title, category, index *)\n\n(** Assembly references — condition:prepare for local, condition:fsx for NuGet *)\n\n(** Opening narrative — what this page covers *)\n\n(* Namespace opens *)\n\n(** Section heading + explanation *)\n(* Code block *)\n(*** output directive ***)\n\n(** Next section + explanation *)\n(* Code block *)\n(*** output directive ***)\n\n(** Summary + cross-references *)\n```\n\nEach section alternates between explanation (doc comments) and demonstration (code + output). The narrative should flow naturally so a reader can follow from top to bottom without jumping around.\n\n## Navigation Ordering Conventions\n\nCategories and pages are ordered by their index values (lower numbers appear first):\n\n| `categoryindex` | Typical use |\n|---|---|\n| 1 | Overview \u002F Getting Started |\n| 2 | Tutorials |\n| 3 | How-To Guides |\n| 4 | Advanced Topics |\n| 5 | Reference |\n\nWithin each category, use `index` values with gaps (1, 3, 5, 7...) so new pages can be inserted without renumbering.\n\n## Best Practices\n\n**DO:**\n- ✅ Organize scripts by feature or use-case, not by API namespace\n- ✅ Start with the simplest working example and build up\n- ✅ Use `(*** include-it ***)` after expressions to show concrete results\n- ✅ Use `(*** hide ***)` for boilerplate that distracts from the narrative\n- ✅ Test with `--eval` to verify all examples actually work\n- ✅ Use `condition: prepare` \u002F `condition: fsx` for assembly reference switching\n\n**DON'T:**\n- ❌ Create one massive script covering everything — split by topic\n- ❌ Show code without showing its output — readers want to see results\n- ❌ Use toy examples that don't resemble real usage\n- ❌ Forget assembly references — `.fsx` files need explicit `#r` directives\n- ❌ Place output directives before the code block — they must follow it\n- ❌ Skip the `--eval` build — unevaluated scripts may contain errors\n\n## Additional Resources\n\n### Reference Files\n- **`references\u002Fliterate-directives.md`** — Complete directive reference with positioning rules, edge cases, evaluator behavior, and troubleshooting\n\n### Templates\n- **`templates\u002Fexample.fsx`** — Starter literate script template with frontmatter, assembly references, and section patterns\n\n## Implementation Workflow\n\n1. Determine the feature or use-case to document\n2. Plan the narrative arc: introduction, setup, basic, advanced, summary\n3. Create `.fsx` file in `docs\u002F` with proper frontmatter\n4. Write interleaved narrative and code sections\n5. Add output directives to show evaluation results\n6. Verify with `dotnet fsdocs build --clean --eval`\n\nFocus on creating examples that teach through working code, progressing from simple to complex.\n\n## Scope \u002F when to use\n\nUse this skill to **author literate `.fsx` scripts in `docs\u002F`** — executable,\nnarrative-driven tutorials and how-to guides built with `--eval`. For reference\ndocumentation generated from source, use [[fsdocs-api-doc]]; for architecture and\ndesign prose, use [[fsdocs-technical]]; to build and preview the scripts, use\n[[fsdocs-build]]; and if the project lacks a docs pipeline, run [[fsdocs-setup]]\nfirst. This skill is for use-case-oriented teaching content, not API reference.\n\n## Driven-library API\n\nThis skill drives the external **FSharp.Formatting** literate-scripting pipeline —\nthere is no FS.Skia.UI backing `.fsi` surface. The driven contract is the literate\ndirective set placed in `(*** … ***)` blocks — `include-output`, `include-it`,\n`include-value`, `include-fsi-output`, `hide`, `do-not-eval`, `define`\u002F`include`,\nand `condition:` (`prepare`\u002F`fsx`\u002F`ipynb`) — plus the `(** … *)` frontmatter\n(`title`, `category`, `categoryindex`, `index`, `description`) and `#r` assembly\nreferences. Scripts evaluate only under `dotnet fsdocs build --eval`.\n\n## Persistent-problem mandate\n\nLiterate directives, their positioning rules, and `condition:` semantics change\nacross FSharp.Formatting versions and fail quietly (output simply does not appear).\nConsult the **official online docs first** for the literate-scripting guide of the\npinned version before relying on a directive documented here, and always verify\nwith an `--eval` build rather than assuming the script rendered.\n\n## Related\n\n- [[fsdocs-setup]] — scaffold the `docs\u002F` directory these scripts live in\n- [[fsdocs-build]] — `--eval` build that executes and renders the scripts\n- [[fsdocs-api-doc]] — API reference that tutorials cross-link to\n- [[fsdocs-technical]] — design prose that complements example-driven docs\n\n## Sources\n\n- FSharp.Formatting literate-scripting guide: https:\u002F\u002Ffsprojects.github.io\u002FFSharp.Formatting\u002Fliterate.html\n- FSharp.Formatting documentation: https:\u002F\u002Ffsprojects.github.io\u002FFSharp.Formatting\u002F\n- FSharp.Formatting repository: https:\u002F\u002Fgithub.com\u002Ffsprojects\u002FFSharp.Formatting\n","# Write Literate F# Documentation Scripts\n\nCreate `.fsx` literate scripts in `docs\u002F` that teach library usage through executable examples with interleaved narrative.\n\n**Key capabilities:**\n- Create literate `.fsx` files with proper FSharp.Formatting frontmatter\n- Interleave narrative documentation with executable F# code\n- Use directives to control output display (`include-output`, `include-it`, `include-value`)\n- Organize examples by feature and use-case with proper navigation ordering\n\n## Overview\n\nFSharp.Formatting processes `.fsx` files in `docs\u002F` as literate scripts. These combine Markdown narrative (in `(**  **)` doc comments) with executable F# code. When built with `--eval`, the code runs and its output can be captured and displayed in the generated pages.\n\nLiterate scripts are organized by feature or use-case, not by namespace or API surface. They answer \"How do I accomplish X?\" rather than \"What does function Y do?\".\n\n## Workflow\n\n### 1. Identify What to Demonstrate\n\nDetermine the topic: a feature, use-case, pattern, or integration. Each script should focus on one coherent topic. Ask:\n- What problem does this solve for the user?\n- What is the simplest working example?\n- What are the important variations or advanced uses?\n\n### 2. Plan the Narrative Arc\n\nStructure the script as a progressive tutorial:\n1. **Introduction** — what this example covers and why it matters\n2. **Setup** — assembly references, namespace opens, any prerequisite configuration\n3. **Basic usage** — simplest possible working example\n4. **Intermediate patterns** — common variations, composition, error handling\n5. **Advanced usage** — complex scenarios, performance considerations (optional)\n6. **Summary** — recap key points, link to related topics\n\n### 3. Create the .fsx File with Frontmatter\n\nPlace the file in `docs\u002F` with a descriptive name. The first lines must be an fsdocs frontmatter block:\n\n```fsharp\n(**\n---\ntitle: Working with Parsers\ncategory: Tutorials\ncategoryindex: 2\nindex: 3\ndescription: Learn how to build and compose parsers.\n---\n*)\n```\n\nFrontmatter fields:\n- `title` — page title (appears in navigation and browser tab)\n- `category` — navigation group name\n- `categoryindex` — sort order of the category in the sidebar (lower = higher)\n- `index` — sort order within the category (lower = higher)\n- `description` — brief summary for search and metadata\n\n### 4. Write Narrative with Interleaved Code\n\nAlternate between Markdown narrative in `(**  **)` blocks and F# code:\n\n```fsharp\n(**\n## Getting Started\n\nFirst, reference the library and open the namespace:\n*)\n\n#r \"..\u002Fsrc\u002FMyLib\u002Fbin\u002FRelease\u002Fnet8.0\u002FMyLib.dll\"\nopen MyLib.Parsers\n\n(**\nCreate a simple parser that matches a single character:\n*)\n\nlet charParser = Parser.char 'a'\nlet result = Parser.run charParser \"abc\"\n(*** include-it ***)\n```\n\nThe `(*** include-it ***)` directive inserts the FSI evaluation result of the preceding expression.\n\n### 5. Use Output Directives\n\nControl what appears in the rendered page:\n\n| Directive | Effect |\n|---|---|\n| `(*** include-output ***)` | Show `stdout` output from preceding code |\n| `(*** include-it ***)` | Show FSI evaluation result of preceding expression |\n| `(*** include-value: x ***)` | Show the value of a named binding |\n| `(*** include-fsi-output ***)` | Show raw FSI output including types |\n| `(*** hide ***)` | Hide the next code block from rendered output |\n| `(*** do-not-eval ***)` | Show code but skip evaluation |\n| `(*** define: name ***)` | Define a named snippet for later inclusion |\n| `(*** include: name ***)` | Include a previously defined snippet |\n| `(*** condition: prepare ***)` | Only include when building (not in output) |\n| `(*** condition: ipynb ***)` | Only include in notebook output |\n\nPlace output directives **immediately after** the code block they reference. The directive applies to the code block directly above it.\n\n### 6. Add Assembly References\n\nLiterate scripts run as FSI scripts. They need explicit assembly references:\n\n```fsharp\n(*** condition: prepare ***)\n#r \"..\u002Fsrc\u002FMyLib\u002Fbin\u002FRelease\u002Fnet8.0\u002FMyLib.dll\"\n(*** condition: fsx ***)\n#r \"nuget: MyLib\"\n```\n\nUse `condition: prepare` for local development paths and `condition: fsx` for NuGet references shown to the reader. This way the script evaluates with local DLLs but the rendered page shows the NuGet install instruction.\n\n### 7. Verify with Build\n\nBuild with `--eval` to execute the scripts and verify output:\n\n```\ndotnet fsdocs build --clean --eval\n```\n\nCheck that:\n- All scripts compile and evaluate without errors\n- Output directives show expected values\n- Navigation ordering is correct in the generated site\n\n## Writing Good Examples\n\n**Teach one concept per script.** A script about \"parsing\" should not also cover serialization. Create separate scripts for separate topics.\n\n**Build complexity gradually.** Start with the simplest example that works, then layer on complexity. Every code block should build on what came before.\n\n**Show realistic use cases.** Avoid toy examples that don't resemble real usage. If the library parses JSON, parse actual JSON structures, not `\"hello\"`.\n\n**Show expected output.** Use `include-it` or `include-value` after expressions so readers see results. Invisible code that \"just works\" is less helpful than seeing concrete values.\n\n**Handle errors explicitly.** Show what happens with invalid input. Document error cases with the same care as success cases.\n\n**Keep setup minimal.** Use `(*** hide ***)` for boilerplate setup that would distract from the main narrative. But always show assembly references and namespace opens — readers need to know these.\n\n**Cross-reference related pages.** End each script with links to related examples and API docs. This helps readers find the next thing they need.\n\n**Name files descriptively.** Use kebab-case names that describe the content: `working-with-parsers.fsx`, `error-handling.fsx`, `async-patterns.fsx`. Avoid generic names like `tutorial1.fsx`.\n\n## Anatomy of a Literate Script\n\nA complete literate script follows this structure:\n\n```fsharp\n(** Frontmatter block — title, category, index *)\n\n(** Assembly references — condition:prepare for local, condition:fsx for NuGet *)\n\n(** Opening narrative — what this page covers *)\n\n(* Namespace opens *)\n\n(** Section heading + explanation *)\n(* Code block *)\n(*** output directive ***)\n\n(** Next section + explanation *)\n(* Code block *)\n(*** output directive ***)\n\n(** Summary + cross-references *)\n```\n\nEach section alternates between explanation (doc comments) and demonstration (code + output). The narrative should flow naturally so a reader can follow from top to bottom without jumping around.\n\n## Navigation Ordering Conventions\n\nCategories and pages are ordered by their index values (lower numbers appear first):\n\n| `categoryindex` | Typical use |\n|---|---|\n| 1 | Overview \u002F Getting Started |\n| 2 | Tutorials |\n| 3 | How-To Guides |\n| 4 | Advanced Topics |\n| 5 | Reference |\n\nWithin each category, use `index` values with gaps (1, 3, 5, 7...) so new pages can be inserted without renumbering.\n\n## Best Practices\n\n**DO:**\n- ✅ Organize scripts by feature or use-case, not by API namespace\n- ✅ Start with the simplest working example and build up\n- ✅ Use `(*** include-it ***)` after expressions to show concrete results\n- ✅ Use `(*** hide ***)` for boilerplate that distracts from the narrative\n- ✅ Test with `--eval` to verify all examples actually work\n- ✅ Use `condition: prepare` \u002F `condition: fsx` for assembly reference switching\n\n**DON'T:**\n- ❌ Create one massive script covering everything — split by topic\n- ❌ Show code without showing its output — readers want to see results\n- ❌ Use toy examples that don't resemble real usage\n- ❌ Forget assembly references — `.fsx` files need explicit `#r` directives\n- ❌ Place output directives before the code block — they must follow it\n- ❌ Skip the `--eval` build — unevaluated scripts may contain errors\n\n## Additional Resources\n\n### Reference Files\n- **`references\u002Fliterate-directives.md`** — Complete directive reference with positioning rules, edge cases, evaluator behavior, and troubleshooting\n\n### Templates\n- **`templates\u002Fexample.fsx`** — Starter literate script template with frontmatter, assembly references, and section patterns\n\n## Implementation Workflow\n\n1. Determine the feature or use-case to document\n2. Plan the narrative arc: introduction, setup, basic, advanced, summary\n3. Create `.fsx` file in `docs\u002F` with proper frontmatter\n4. Write interleaved narrative and code sections\n5. Add output directives to show evaluation results\n6. Verify with `dotnet fsdocs build --clean --eval`\n\nFocus on creating examples that teach through working code, progressing from simple to complex.\n\n## Scope \u002F when to use\n\nUse this skill to **author literate `.fsx` scripts in `docs\u002F`** — executable,\nnarrative-driven tutorials and how-to guides built with `--eval`. For reference\ndocumentation generated from source, use [[fsdocs-api-doc]]; for architecture and\ndesign prose, use [[fsdocs-technical]]; to build and preview the scripts, use\n[[fsdocs-build]]; and if the project lacks a docs pipeline, run [[fsdocs-setup]]\nfirst. This skill is for use-case-oriented teaching content, not API reference.\n\n## Driven-library API\n\nThis skill drives the external **FSharp.Formatting** literate-scripting pipeline —\nthere is no FS.Skia.UI backing `.fsi` surface. The driven contract is the literate\ndirective set placed in `(*** … ***)` blocks — `include-output`, `include-it`,\n`include-value`, `include-fsi-output`, `hide`, `do-not-eval`, `define`\u002F`include`,\nand `condition:` (`prepare`\u002F`fsx`\u002F`ipynb`) — plus the `(** … *)` frontmatter\n(`title`, `category`, `categoryindex`, `index`, `description`) and `#r` assembly\nreferences. Scripts evaluate only under `dotnet fsdocs build --eval`.\n\n## Persistent-problem mandate\n\nLiterate directives, their positioning rules, and `condition:` semantics change\nacross FSharp.Formatting versions and fail quietly (output simply does not appear).\nConsult the **official online docs first** for the literate-scripting guide of the\npinned version before relying on a directive documented here, and always verify\nwith an `--eval` build rather than assuming the script rendered.\n\n## Related\n\n- [[fsdocs-setup]] — scaffold the `docs\u002F` directory these scripts live in\n- [[fsdocs-build]] — `--eval` build that executes and renders the scripts\n- [[fsdocs-api-doc]] — API reference that tutorials cross-link to\n- [[fsdocs-technical]] — design prose that complements example-driven docs\n\n## Sources\n\n- FSharp.Formatting literate-scripting guide: https:\u002F\u002Ffsprojects.github.io\u002FFSharp.Formatting\u002Fliterate.html\n- FSharp.Formatting documentation: https:\u002F\u002Ffsprojects.github.io\u002FFSharp.Formatting\u002F\n- FSharp.Formatting repository: https:\u002F\u002Fgithub.com\u002Ffsprojects\u002FFSharp.Formatting\n",{"name":5,"version":23,"description":7},"0.1.0","main","f943406829a9218b2882e09eb88d4ddb539c5e72",".claude\u002Fskills\u002Ffsdocs-examples",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":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add EHotwagner\u002FFS-Skia-UI --skill fsdocs-examples",{"tool":37,"command":38},"bunx","bunx skills add EHotwagner\u002FFS-Skia-UI --skill fsdocs-examples",{"tool":40,"command":41},"pnpm","pnpm dlx skills add EHotwagner\u002FFS-Skia-UI --skill fsdocs-examples","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffsdocs-examples\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fliterate-directives.md","REFERENCE","参考文档",11738,"https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffsdocs-examples\u002Freferences\u002Fliterate-directives.md",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"templates\u002Fexample.fsx","OTHER","其他",1046,"https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffsdocs-examples\u002Ftemplates\u002Fexample.fsx",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]