[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVPJ1FDTCANDZEVMV2TVJW":3,"skill-same:01M7CVPJ1FDTCANDZEVMV2TVJW":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7CVPJ1FDTCANDZEVMV2TVJW","use-js-interop",null,"Add, review, or fix JavaScript interop in Blazor components. USE FOR: calling JavaScript from Blazor, calling .NET from JavaScript, collocated .razor.js modules, IJSRuntime, IJSObjectReference lifecycle, DotNetObjectReference, ElementReference, timing rules for when JS is available, IAsyncDisposable disposal of JS references, server-side JS interop safety. DO NOT USE FOR: general Blazor component authoring without JS interop needs (use author-component), forms (use collect-user-input).","deadmade\u002Fdead-agent-skills","deadmade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130925709?v=4","01M7CTQ65AGYR4J9K9TX0YR9V3","01M7CTQ66B4VMJFEDZP4EKKE6K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fuse-js-interop\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nlicense: MIT\nname: use-js-interop\ndescription: >\n  Add, review, or fix JavaScript interop in Blazor components.\n  USE FOR: calling JavaScript from Blazor, calling .NET from JavaScript,\n  collocated .razor.js modules, IJSRuntime, IJSObjectReference lifecycle,\n  DotNetObjectReference, ElementReference, timing rules for when JS is available,\n  IAsyncDisposable disposal of JS references, server-side JS interop safety.\n  DO NOT USE FOR: general Blazor component authoring without JS interop needs\n  (use author-component), forms (use collect-user-input).\n---\n\n# JS Interop in Blazor\n\n## 1. Collocated JS Modules\n\nAlways use collocated `.razor.js` files with `export` — never global `window.*` functions or `\u003Cscript>` tags.\n\n```javascript\n\u002F\u002F ChartPanel.razor.js — placed next to ChartPanel.razor\nexport function initialize(canvas, dotNetRef) { \u002F* ... *\u002F }\nexport function updateData(points) { \u002F* ... *\u002F }\nexport function dispose() { \u002F* ... *\u002F }\n```\n\nImport paths: same project = `\".\u002FComponents\u002FChartPanel.razor.js\"`, RCL = `\".\u002F_content\u002F{AssemblyName}\u002F...\"`.\n\n## 2. Lifecycle Timing\n\n**All JS interop must happen in `OnAfterRenderAsync` or event handlers** — never in `OnInitialized`, `OnParametersSet`, or constructors. JS is not available during server prerendering.\n\nUse a typed interop wrapper (see Section 4) — never call `InvokeAsync`\u002F`InvokeVoidAsync` with raw string literals:\n\n```csharp\nprivate ChartInterop? _chart;\n\nprotected override async Task OnAfterRenderAsync(bool firstRender)\n{\n    if (firstRender)\n    {\n        _chart = new ChartInterop(JS);\n        await _chart.InitializeAsync(_canvasRef);\n    }\n}\n```\n\n**Parameter changes**: set a flag in `OnParametersSet`, apply in `OnAfterRenderAsync`:\n\n```csharp\nprivate bool _dataChanged;\n\nprotected override void OnParametersSet() => _dataChanged = true;\n\nprotected override async Task OnAfterRenderAsync(bool firstRender)\n{\n    if (firstRender) { \u002F* init *\u002F }\n    else if (_dataChanged && _chart is not null)\n    {\n        _dataChanged = false;\n        await _chart.UpdateDataAsync(DataPoints);\n    }\n}\n```\n\n## 3. Batch Related Operations\n\nEach JS interop call crosses the .NET-to-JS boundary (and in Blazor Server, the SignalR circuit). Batching applies in **both directions** — .NET→JS and JS→.NET.\n\n### .NET → JS: merge consecutive calls\n\nIf the C# side makes two or more JS calls in a row, combine them into one JS function:\n\n```csharp\n\u002F\u002F ❌ Two round-trips — theme and locale are always applied together\nawait _module.InvokeVoidAsync(\"applyTheme\", theme);\nawait _module.InvokeVoidAsync(\"applyLocale\", locale);\n\n\u002F\u002F ❌ Result of one call feeds into another — both can stay in JS\nvar token = await _module.InvokeAsync\u003Cstring>(\"createAccessToken\");\nawait _module.InvokeVoidAsync(\"storeToken\", token);\n```\n\n```javascript\n\u002F\u002F ✅ One call applies both — no data dependency, no reason for two trips\nexport function applyPreferences(theme, locale) {\n    document.documentElement.dataset.theme = theme;\n    document.documentElement.lang = locale;\n}\n\n\u002F\u002F ✅ Chain stays in JS — the token never needs to cross the boundary\nexport function createAndStoreToken() {\n    const token = crypto.randomUUID();\n    sessionStorage.setItem('access-token', token);\n    return token;\n}\n```\n\n### JS → .NET: batch callbacks\n\nWhen JS needs to send multiple pieces of data back to .NET, send them in a single `invokeMethodAsync` call rather than making separate callbacks:\n\n```javascript\n\u002F\u002F ❌ Two .NET round-trips from JS\nawait dotNetRef.invokeMethodAsync(ON_VOLUME_CHANGED, volume);\nawait dotNetRef.invokeMethodAsync(ON_PLAYBACK_CHANGED, isPlaying);\n\n\u002F\u002F ✅ One callback with all data\nawait dotNetRef.invokeMethodAsync(ON_PLAYER_STATE_CHANGED, { volume, isPlaying });\n```\n\n**Rule**: if two interop calls always happen together from either side, merge them into one function.\n\n## 4. Typed Interop Wrapper\n\nEncapsulate interop for a feature in a plain class that owns the module lifecycle:\n\n```csharp\npublic sealed class ChartInterop : IAsyncDisposable\n{\n    internal const string ModulePath = \".\u002FComponents\u002FChartPanel.razor.js\";\n    internal const string InitMethod = \"initialize\";\n    internal const string UpdateMethod = \"updateData\";\n    internal const string DisposeMethod = \"dispose\";\n\n    private readonly IJSRuntime _js;\n    private IJSObjectReference? _module;\n\n    public ChartInterop(IJSRuntime js) => _js = js;\n\n    private async ValueTask\u003CIJSObjectReference> GetModuleAsync()\n        => _module ??= await _js.InvokeAsync\u003CIJSObjectReference>(\"import\", ModulePath);\n\n    public async ValueTask InitializeAsync(ElementReference canvas)\n    {\n        var module = await GetModuleAsync();\n        await module.InvokeVoidAsync(InitMethod, canvas);\n    }\n\n    public async ValueTask UpdateDataAsync(IReadOnlyList\u003CDataPoint> points)\n    {\n        var module = await GetModuleAsync();\n        await module.InvokeVoidAsync(UpdateMethod, points);\n    }\n\n    public async ValueTask DisposeAsync()\n    {\n        try\n        {\n            if (_module is not null)\n            {\n                await _module.InvokeVoidAsync(DisposeMethod);\n                await _module.DisposeAsync();\n            }\n        }\n        catch (JSDisconnectedException) { }\n    }\n}\n```\n\nThe component creates and uses the wrapper with no magic strings:\n\n```razor\n@inject IJSRuntime JS\n@implements IAsyncDisposable\n\n\u003Ccanvas @ref=\"_canvasRef\" width=\"600\" height=\"400\">\u003C\u002Fcanvas>\n\n@code {\n    private ElementReference _canvasRef;\n    private ChartInterop? _chart;\n\n    protected override async Task OnAfterRenderAsync(bool firstRender)\n    {\n        if (firstRender)\n        {\n            _chart = new ChartInterop(JS);\n            await _chart.InitializeAsync(_canvasRef);\n        }\n    }\n\n    async ValueTask IAsyncDisposable.DisposeAsync()\n    {\n        if (_chart is not null)\n            await _chart.DisposeAsync();\n    }\n}\n```\n\nPrefer a concrete class over interface + implementation for interop wrappers. For unit testing, substitute `IJSRuntime` directly (it is already an interface).\n\n## 5. DotNetObjectReference for JS-to-.NET Callbacks\n\n```csharp\n_dotNetRef = DotNetObjectReference.Create(this);\nawait _module.InvokeVoidAsync(\"initialize\", _dotNetRef);\n```\n\nOn the JS side, wrap the `dotNetRef` in a class. Use `async`\u002F`await` with `try\u002Fcatch` (not `.catch()`) to guard against circuit loss. Define .NET method name constants at the top:\n\n```javascript\nconst ON_CLIPBOARD_CHANGED = 'OnClipboardChanged';\n\nclass ClipboardMonitor {\n    #dotNetRef;\n    #abortController;\n\n    constructor(dotNetRef) {\n        this.#dotNetRef = dotNetRef;\n        this.#abortController = new AbortController();\n    }\n\n    start() {\n        document.addEventListener('copy', async () => {\n            try {\n                const text = await navigator.clipboard.readText();\n                await this.#dotNetRef.invokeMethodAsync(ON_CLIPBOARD_CHANGED, text);\n            } catch { \u002F* circuit disconnected or clipboard denied *\u002F }\n        }, { signal: this.#abortController.signal });\n    }\n\n    dispose() {\n        this.#abortController.abort();\n    }\n}\n\nlet monitor;\nexport function initialize(dotNetRef) {\n    monitor = new ClipboardMonitor(dotNetRef);\n    monitor.start();\n}\n\nexport function dispose() {\n    monitor?.dispose();\n}\n```\n\nRules:\n- `[JSInvokable]` methods **must be `public`** — private\u002Finternal silently fails at runtime\n- Wrap `StateHasChanged` in `InvokeAsync` inside `[JSInvokable]` callbacks:\n  ```csharp\n  [JSInvokable]\n  public async Task OnClipboardChanged(string text)\n  {\n      await InvokeAsync(() => { _lastClipboard = text; StateHasChanged(); });\n  }\n  ```\n- Always `try\u002Fcatch` around `invokeMethodAsync` in JS — circuit loss throws\n- Use `const` for .NET method name strings in JS — prevents typo bugs that silently fail\n- Dispose `DotNetObjectReference` in `DisposeAsync`\n\n## 6. Disposal and Server Safety\n\nAlways implement `IAsyncDisposable`. Call JS cleanup first, then dispose references. Catch `JSDisconnectedException` for Blazor Server circuit loss:\n\n```csharp\npublic async ValueTask DisposeAsync()\n{\n    try\n    {\n        if (_module is not null)\n        {\n            await _module.InvokeVoidAsync(\"dispose\");\n            await _module.DisposeAsync();\n        }\n    }\n    catch (JSDisconnectedException) { }\n\n    _dotNetRef?.Dispose();\n}\n```\n\nNever use sync `IDisposable` for JS interop cleanup — `InvokeVoidAsync` returns `ValueTask` and must be awaited.\n\n## 7. ElementReference\n\nPass DOM elements via `@ref`, not string IDs:\n\n```razor\n\u003Ccanvas @ref=\"_canvasRef\" width=\"600\" height=\"400\">\u003C\u002Fcanvas>\n```\n\n```csharp\nawait _chart.InitializeAsync(_canvasRef);\n```\n\n## Checklist\n\n- [ ] JS is in collocated `.razor.js` with `export` — no `window.*` globals\n- [ ] All interop in `OnAfterRenderAsync` or event handlers — never during prerender\n- [ ] `IAsyncDisposable` catches `JSDisconnectedException`\n- [ ] `DotNetObjectReference` disposed in `DisposeAsync`; JS side has `try\u002Fcatch` around `invokeMethodAsync`\n- [ ] `[JSInvokable]` methods are `public` and use `await InvokeAsync(StateHasChanged)`\n- [ ] `InvokeVoidAsync` used when no return value is needed\n- [ ] `ElementReference` instead of string IDs\n- [ ] Related operations batched into single interop calls (both .NET→JS and JS→.NET)\n\n## Common Mistakes Checklist\n\n| Mistake | Fix |\n|---------|-----|\n| Using JS for something achievable with CSS | Use CSS custom properties, `data-` attributes, pseudo-classes |\n| Many fine-grained interop calls | Batch into coarse functions — both .NET→JS and JS→.NET |\n| Component imports JS module directly | Encapsulate in a strongly typed interop class |\n| Magic strings for method names \u002F module paths | Define `internal const` fields in the interop class |\n| Interface + implementation for interop wrapper | Use a plain class; mock `IJSRuntime` for tests instead |\n| JS calls in `OnInitializedAsync` | Move to `OnAfterRenderAsync(firstRender)` |\n| `InvokeAsync\u003Cobject>` for void calls | Use `InvokeVoidAsync` |\n| `IDisposable` with fire-and-forget JS | Use `IAsyncDisposable` with `await` |\n| Global `window.*` JS functions | Use collocated `.razor.js` with `export` |\n| String element IDs passed to JS | Use `ElementReference` with `@ref` |\n| `[JSInvokable]` on private method | Must be `public` — silently fails otherwise |\n| `DotNetObjectReference` not disposed | Dispose in `DisposeAsync` — causes memory leak |\n| `StateHasChanged()` without `InvokeAsync` | Wrap in `await InvokeAsync(() => { StateHasChanged(); })` |\n| JS `invokeMethodAsync` without error handling | Wrap in `try\u002Fcatch` — circuit loss throws |\n| Bare `dotNetRef` in JS event handlers | Wrap in a class with `#dotNetRef` private field |\n| Magic strings in JS `invokeMethodAsync` calls | Use `const` at module top — typos silently fail at runtime |\n| JS calls in `OnParametersSetAsync` | Track changes, apply in `OnAfterRenderAsync` with guard |\n| No null check before calling module | Check `module is not null` before use |\n","# JS Interop in Blazor\n\n## 1. Collocated JS Modules\n\nAlways use collocated `.razor.js` files with `export` — never global `window.*` functions or `\u003Cscript>` tags.\n\n```javascript\n\u002F\u002F ChartPanel.razor.js — placed next to ChartPanel.razor\nexport function initialize(canvas, dotNetRef) { \u002F* ... *\u002F }\nexport function updateData(points) { \u002F* ... *\u002F }\nexport function dispose() { \u002F* ... *\u002F }\n```\n\nImport paths: same project = `\".\u002FComponents\u002FChartPanel.razor.js\"`, RCL = `\".\u002F_content\u002F{AssemblyName}\u002F...\"`.\n\n## 2. Lifecycle Timing\n\n**All JS interop must happen in `OnAfterRenderAsync` or event handlers** — never in `OnInitialized`, `OnParametersSet`, or constructors. JS is not available during server prerendering.\n\nUse a typed interop wrapper (see Section 4) — never call `InvokeAsync`\u002F`InvokeVoidAsync` with raw string literals:\n\n```csharp\nprivate ChartInterop? _chart;\n\nprotected override async Task OnAfterRenderAsync(bool firstRender)\n{\n    if (firstRender)\n    {\n        _chart = new ChartInterop(JS);\n        await _chart.InitializeAsync(_canvasRef);\n    }\n}\n```\n\n**Parameter changes**: set a flag in `OnParametersSet`, apply in `OnAfterRenderAsync`:\n\n```csharp\nprivate bool _dataChanged;\n\nprotected override void OnParametersSet() => _dataChanged = true;\n\nprotected override async Task OnAfterRenderAsync(bool firstRender)\n{\n    if (firstRender) { \u002F* init *\u002F }\n    else if (_dataChanged && _chart is not null)\n    {\n        _dataChanged = false;\n        await _chart.UpdateDataAsync(DataPoints);\n    }\n}\n```\n\n## 3. Batch Related Operations\n\nEach JS interop call crosses the .NET-to-JS boundary (and in Blazor Server, the SignalR circuit). Batching applies in **both directions** — .NET→JS and JS→.NET.\n\n### .NET → JS: merge consecutive calls\n\nIf the C# side makes two or more JS calls in a row, combine them into one JS function:\n\n```csharp\n\u002F\u002F ❌ Two round-trips — theme and locale are always applied together\nawait _module.InvokeVoidAsync(\"applyTheme\", theme);\nawait _module.InvokeVoidAsync(\"applyLocale\", locale);\n\n\u002F\u002F ❌ Result of one call feeds into another — both can stay in JS\nvar token = await _module.InvokeAsync\u003Cstring>(\"createAccessToken\");\nawait _module.InvokeVoidAsync(\"storeToken\", token);\n```\n\n```javascript\n\u002F\u002F ✅ One call applies both — no data dependency, no reason for two trips\nexport function applyPreferences(theme, locale) {\n    document.documentElement.dataset.theme = theme;\n    document.documentElement.lang = locale;\n}\n\n\u002F\u002F ✅ Chain stays in JS — the token never needs to cross the boundary\nexport function createAndStoreToken() {\n    const token = crypto.randomUUID();\n    sessionStorage.setItem('access-token', token);\n    return token;\n}\n```\n\n### JS → .NET: batch callbacks\n\nWhen JS needs to send multiple pieces of data back to .NET, send them in a single `invokeMethodAsync` call rather than making separate callbacks:\n\n```javascript\n\u002F\u002F ❌ Two .NET round-trips from JS\nawait dotNetRef.invokeMethodAsync(ON_VOLUME_CHANGED, volume);\nawait dotNetRef.invokeMethodAsync(ON_PLAYBACK_CHANGED, isPlaying);\n\n\u002F\u002F ✅ One callback with all data\nawait dotNetRef.invokeMethodAsync(ON_PLAYER_STATE_CHANGED, { volume, isPlaying });\n```\n\n**Rule**: if two interop calls always happen together from either side, merge them into one function.\n\n## 4. Typed Interop Wrapper\n\nEncapsulate interop for a feature in a plain class that owns the module lifecycle:\n\n```csharp\npublic sealed class ChartInterop : IAsyncDisposable\n{\n    internal const string ModulePath = \".\u002FComponents\u002FChartPanel.razor.js\";\n    internal const string InitMethod = \"initialize\";\n    internal const string UpdateMethod = \"updateData\";\n    internal const string DisposeMethod = \"dispose\";\n\n    private readonly IJSRuntime _js;\n    private IJSObjectReference? _module;\n\n    public ChartInterop(IJSRuntime js) => _js = js;\n\n    private async ValueTask\u003CIJSObjectReference> GetModuleAsync()\n        => _module ??= await _js.InvokeAsync\u003CIJSObjectReference>(\"import\", ModulePath);\n\n    public async ValueTask InitializeAsync(ElementReference canvas)\n    {\n        var module = await GetModuleAsync();\n        await module.InvokeVoidAsync(InitMethod, canvas);\n    }\n\n    public async ValueTask UpdateDataAsync(IReadOnlyList\u003CDataPoint> points)\n    {\n        var module = await GetModuleAsync();\n        await module.InvokeVoidAsync(UpdateMethod, points);\n    }\n\n    public async ValueTask DisposeAsync()\n    {\n        try\n        {\n            if (_module is not null)\n            {\n                await _module.InvokeVoidAsync(DisposeMethod);\n                await _module.DisposeAsync();\n            }\n        }\n        catch (JSDisconnectedException) { }\n    }\n}\n```\n\nThe component creates and uses the wrapper with no magic strings:\n\n```razor\n@inject IJSRuntime JS\n@implements IAsyncDisposable\n\n\u003Ccanvas @ref=\"_canvasRef\" width=\"600\" height=\"400\">\u003C\u002Fcanvas>\n\n@code {\n    private ElementReference _canvasRef;\n    private ChartInterop? _chart;\n\n    protected override async Task OnAfterRenderAsync(bool firstRender)\n    {\n        if (firstRender)\n        {\n            _chart = new ChartInterop(JS);\n            await _chart.InitializeAsync(_canvasRef);\n        }\n    }\n\n    async ValueTask IAsyncDisposable.DisposeAsync()\n    {\n        if (_chart is not null)\n            await _chart.DisposeAsync();\n    }\n}\n```\n\nPrefer a concrete class over interface + implementation for interop wrappers. For unit testing, substitute `IJSRuntime` directly (it is already an interface).\n\n## 5. DotNetObjectReference for JS-to-.NET Callbacks\n\n```csharp\n_dotNetRef = DotNetObjectReference.Create(this);\nawait _module.InvokeVoidAsync(\"initialize\", _dotNetRef);\n```\n\nOn the JS side, wrap the `dotNetRef` in a class. Use `async`\u002F`await` with `try\u002Fcatch` (not `.catch()`) to guard against circuit loss. Define .NET method name constants at the top:\n\n```javascript\nconst ON_CLIPBOARD_CHANGED = 'OnClipboardChanged';\n\nclass ClipboardMonitor {\n    #dotNetRef;\n    #abortController;\n\n    constructor(dotNetRef) {\n        this.#dotNetRef = dotNetRef;\n        this.#abortController = new AbortController();\n    }\n\n    start() {\n        document.addEventListener('copy', async () => {\n            try {\n                const text = await navigator.clipboard.readText();\n                await this.#dotNetRef.invokeMethodAsync(ON_CLIPBOARD_CHANGED, text);\n            } catch { \u002F* circuit disconnected or clipboard denied *\u002F }\n        }, { signal: this.#abortController.signal });\n    }\n\n    dispose() {\n        this.#abortController.abort();\n    }\n}\n\nlet monitor;\nexport function initialize(dotNetRef) {\n    monitor = new ClipboardMonitor(dotNetRef);\n    monitor.start();\n}\n\nexport function dispose() {\n    monitor?.dispose();\n}\n```\n\nRules:\n- `[JSInvokable]` methods **must be `public`** — private\u002Finternal silently fails at runtime\n- Wrap `StateHasChanged` in `InvokeAsync` inside `[JSInvokable]` callbacks:\n  ```csharp\n  [JSInvokable]\n  public async Task OnClipboardChanged(string text)\n  {\n      await InvokeAsync(() => { _lastClipboard = text; StateHasChanged(); });\n  }\n  ```\n- Always `try\u002Fcatch` around `invokeMethodAsync` in JS — circuit loss throws\n- Use `const` for .NET method name strings in JS — prevents typo bugs that silently fail\n- Dispose `DotNetObjectReference` in `DisposeAsync`\n\n## 6. Disposal and Server Safety\n\nAlways implement `IAsyncDisposable`. Call JS cleanup first, then dispose references. Catch `JSDisconnectedException` for Blazor Server circuit loss:\n\n```csharp\npublic async ValueTask DisposeAsync()\n{\n    try\n    {\n        if (_module is not null)\n        {\n            await _module.InvokeVoidAsync(\"dispose\");\n            await _module.DisposeAsync();\n        }\n    }\n    catch (JSDisconnectedException) { }\n\n    _dotNetRef?.Dispose();\n}\n```\n\nNever use sync `IDisposable` for JS interop cleanup — `InvokeVoidAsync` returns `ValueTask` and must be awaited.\n\n## 7. ElementReference\n\nPass DOM elements via `@ref`, not string IDs:\n\n```razor\n\u003Ccanvas @ref=\"_canvasRef\" width=\"600\" height=\"400\">\u003C\u002Fcanvas>\n```\n\n```csharp\nawait _chart.InitializeAsync(_canvasRef);\n```\n\n## Checklist\n\n- [ ] JS is in collocated `.razor.js` with `export` — no `window.*` globals\n- [ ] All interop in `OnAfterRenderAsync` or event handlers — never during prerender\n- [ ] `IAsyncDisposable` catches `JSDisconnectedException`\n- [ ] `DotNetObjectReference` disposed in `DisposeAsync`; JS side has `try\u002Fcatch` around `invokeMethodAsync`\n- [ ] `[JSInvokable]` methods are `public` and use `await InvokeAsync(StateHasChanged)`\n- [ ] `InvokeVoidAsync` used when no return value is needed\n- [ ] `ElementReference` instead of string IDs\n- [ ] Related operations batched into single interop calls (both .NET→JS and JS→.NET)\n\n## Common Mistakes Checklist\n\n| Mistake | Fix |\n|---------|-----|\n| Using JS for something achievable with CSS | Use CSS custom properties, `data-` attributes, pseudo-classes |\n| Many fine-grained interop calls | Batch into coarse functions — both .NET→JS and JS→.NET |\n| Component imports JS module directly | Encapsulate in a strongly typed interop class |\n| Magic strings for method names \u002F module paths | Define `internal const` fields in the interop class |\n| Interface + implementation for interop wrapper | Use a plain class; mock `IJSRuntime` for tests instead |\n| JS calls in `OnInitializedAsync` | Move to `OnAfterRenderAsync(firstRender)` |\n| `InvokeAsync\u003Cobject>` for void calls | Use `InvokeVoidAsync` |\n| `IDisposable` with fire-and-forget JS | Use `IAsyncDisposable` with `await` |\n| Global `window.*` JS functions | Use collocated `.razor.js` with `export` |\n| String element IDs passed to JS | Use `ElementReference` with `@ref` |\n| `[JSInvokable]` on private method | Must be `public` — silently fails otherwise |\n| `DotNetObjectReference` not disposed | Dispose in `DisposeAsync` — causes memory leak |\n| `StateHasChanged()` without `InvokeAsync` | Wrap in `await InvokeAsync(() => { StateHasChanged(); })` |\n| JS `invokeMethodAsync` without error handling | Wrap in `try\u002Fcatch` — circuit loss throws |\n| Bare `dotNetRef` in JS event handlers | Wrap in a class with `#dotNetRef` private field |\n| Magic strings in JS `invokeMethodAsync` calls | Use `const` at module top — typos silently fail at runtime |\n| JS calls in `OnParametersSetAsync` | Track changes, apply in `OnAfterRenderAsync` with guard |\n| No null check before calling module | Check `module is not null` before use |\n",{"name":5,"license":14,"description":7},"main","ccab8dffc0ecc173838f51e4c5f0d3b51a704f41","plugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fuse-js-interop","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills","https:\u002F\u002Fgithub.com\u002Fdeadmade","https:\u002F\u002Fdeadmade.github.io\u002F","Blood, an Ocean of blood","2026-11-14 02:03:31",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add deadmade\u002Fdead-agent-skills --skill use-js-interop",{"tool":37,"command":38},"bunx","bunx skills add deadmade\u002Fdead-agent-skills --skill use-js-interop",{"tool":40,"command":41},"pnpm","pnpm dlx skills add deadmade\u002Fdead-agent-skills --skill use-js-interop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fuse-js-interop\u002FSKILL.md",true,[],[46,53,62,70,77,84],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7CVRBFTXSTTQ7F5P6PJEFYA","rust-best-practices","Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Frust-skills\u002Fskills\u002Frust-best-practices\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7CVR0W7B8EGTNPSPA7FPC4Z","postgres-database-migration","Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases.\n\n**Trigger when user asks to:**\n- Test a schema migration before applying it to production\n- Add, remove, or rename columns safely on a live table\n- Change a column's data type without downtime\n- Add or drop indexes, constraints, or foreign keys on large tables\n- Understand which ALTER TABLE operations lock the table\n- Roll back a failed migration\n- Plan a zero-downtime migration strategy\n- Fork a database to test a migration safely\n\nCovers: lock-level reference for every common DDL operation, safe migration patterns, fork-based testing, zero-downtime column changes, index creation, constraint addition, backfill strategies, pre\u002Fpost-migration validation, and rollback planning.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-database-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-database-migration\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7CVQWK20ASAZN5VETZC8J99","postgres-best-practices","Best practices and guidelines for working with Postgres. Covers schema design, indexing strategies, query optimization, migrations, and common pitfalls. Use when writing SQL, designing database schemas, optimizing queries, or setting up a Postgres database.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-best-practices\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7CVQ5CY7AQHY7A2Y99RE6A7","writing-mstest-tests","ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7CVPWJZ63GB0810F0SCGZ1K","winforms-expert","Create, modify, debug, or review Windows Forms applications only when the request contains a concrete Windows Forms marker. USE FOR: WinForms, Windows Forms, System.Windows.Forms, WinForms Form or UserControl designer files (*.Designer.cs or *.Designer.vb), Visual Studio WinForms Designer, TableLayoutPanel, BindingSource, DataGridView, Control.InvokeAsync, component-tray ownership, or custom control serialization. DO NOT USE FOR: WPF or WPF XAML, including Window.InputBindings, KeyBinding, commands, or DataContext; .NET MAUI; Avalonia; or any request where none of the listed Windows Forms markers is present.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fwinforms-expert\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7CVPR0QFZ1HMJ6GZRBQAQ7W","vectorization","Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64\u002F128\u002F256\u002F512, or platform hardware intrinsics; reviewing existing SIMD code, including the generic Vector type, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fvectorization\u002FSKILL.md",[],[]]