[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XBFSV54N5KNMPK8K9MM3V":3,"skill-same:01M79XBFSV54N5KNMPK8K9MM3V":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M79XBFSV54N5KNMPK8K9MM3V","deniz-dotnet-general.dotnet-aot-compat",null,"Make .NET projects compatible with Native AOT and trimming by systematically resolving IL trim\u002FAOT analyzer warnings. USE FOR: making projects AOT-compatible, fixing trimming warnings, resolving IL warnings (IL2026, IL2070, IL2067, IL2072, IL3050), adding DynamicallyAccessedMembers annotations, enabling IsAotCompatible. DO NOT USE FOR: publishing native AOT binaries, optimizing binary size, replacing reflection-heavy libraries with alternatives. INVOKES: dotnet build, grep, project and source edits, and sub-agents where available.","Blind-Striker\u002Fagent-skills-and-plugins","Blind-Striker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1965259?v=4","01M79WFXTE5PH0C1VB7B54ANMN","Deniz İrgin","01M79WFXV5KZ5GST1K8G035DM5",1,"MIT","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.dotnet-aot-compat\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deniz-dotnet-general.dotnet-aot-compat\ndescription: >\n  Make .NET projects compatible with Native AOT and trimming by systematically\n  resolving IL trim\u002FAOT analyzer warnings. USE FOR: making projects\n  AOT-compatible, fixing trimming warnings, resolving IL warnings (IL2026,\n  IL2070, IL2067, IL2072, IL3050), adding DynamicallyAccessedMembers\n  annotations, enabling IsAotCompatible. DO NOT USE FOR: publishing native AOT\n  binaries, optimizing binary size, replacing reflection-heavy libraries with\n  alternatives. INVOKES: dotnet build, grep, project and source edits, and\n  sub-agents where available.\nmetadata:\n  opencode\u002Fautoinvoke: false\n---\n\n# dotnet-aot-compat\n\nMake .NET projects compatible with Native AOT and trimming by systematically resolving all IL trim\u002FAOT analyzer warnings.\n\n## When to Use This Skill\n\n- **\"Make this project AOT-compatible\"**\n- **\"Fix trimming warnings\"** or **\"fix IL warnings\"**\n- **\"Resolve IL2070 \u002F IL2067 \u002F IL2072 \u002F IL2026 \u002F IL3050 warnings\"**\n- **\"Add DynamicallyAccessedMembers annotations\"**\n- **\"Enable IsAotCompatible in my .csproj\"**\n- **\"My project has trim analyzer warnings after upgrading to net8.0\"**\n- **\"Annotate reflection code for the trimmer\"**\n\n## When Not to Use This Skill\n\nDo not use this skill when the project exclusively targets .NET Framework (net4x), which does not support the trim\u002FAOT analyzers.\n\n## Prerequisites\n\nAn existing .NET project targeting net8.0 or later (or multi-targeting with at least one net8.0+ TFM) and the corresponding .NET SDK installed.\n\n## Background: What AOT Compatibility Means\n\nNative AOT and the IL trimmer perform static analysis to determine what code is reachable. Reflection can break this analysis because the trimmer can't see what types\u002Fmembers are accessed at runtime. The `IsAotCompatible` property enables analyzers that flag these issues as build warnings (ILXXXX codes).\n\n## Critical Rules\n\n### ❌ Never suppress warnings incorrectly\n\n- **NEVER** use `#pragma warning disable` for IL warnings. It hides warnings from the Roslyn analyzer at build time, but the IL linker and AOT compiler still see the issue. The code will fail at trim\u002Fpublish time.\n- **NEVER** use `[UnconditionalSuppressMessage]`. It tells both the analyzer AND the linker to ignore the warning, meaning the trimmer cannot verify safety. Raising an error at build time is always preferable to hiding the issue and having it silently break at runtime.\n\n### 💡 Preferred approaches\n\n- **Prefer** `[DynamicallyAccessedMembers]` annotations to flow type information through the call chain.\n- **Prefer** refactoring to eliminate patterns that break annotation flow (e.g., boxing `Type` through `object[]`).\n- **Use** `[RequiresUnreferencedCode]` \u002F `[RequiresDynamicCode]` \u002F `[RequiresAssemblyFiles]` to mark methods as fundamentally incompatible with trimming, propagating the requirement to callers. This surfaces the issue clearly rather than hiding it — callers must explicitly acknowledge the incompatibility.\n\n### Annotation flow is key\n\nThe trimmer tracks `[DynamicallyAccessedMembers]` annotations through assignments, parameter passing, and return values. If this flow is broken (e.g., by boxing a `Type` into `object`, storing in an untyped collection, or casting through interfaces), the trimmer loses track and warns. The fix is to preserve the flow, not suppress the warning.\n\n## Step-by-Step Procedure\n\n> **Do not explore the codebase up-front.** The build warnings tell you exactly which files and lines need changes. Follow a tight loop: **build → pick a warning → open that file at that line → apply the fix recipe → rebuild**. Reading or analyzing source files beyond what a specific warning points you to is wasted effort and leads to timeouts. Let the compiler guide you.\n>\n> ❌ Do NOT run `find`, `ls`, or `grep` to understand the project structure before building. Do NOT read README, docs, or architecture files. Your first action should be Step 1 (enable AOT analysis), then build.\n\n### Step 1: Enable AOT analysis in the .csproj\n\nAdd `IsAotCompatible`. If the project doesn't exclusively target net8.0+, add a TFM condition (AOT analysis requires net8.0+):\n\n```xml\n\u003CPropertyGroup>\n  \u003CIsAotCompatible Condition=\"$([MSBuild]::IsTargetFrameworkCompatible('$(TargetFramework)', 'net8.0'))\">true\u003C\u002FIsAotCompatible>\n\u003C\u002FPropertyGroup>\n```\n\nThis automatically sets `EnableTrimAnalyzer=true` and `EnableAotAnalyzer=true` for compatible TFMs. For multi-targeting projects (e.g., `netstandard2.0;net8.0`), the condition ensures no `NETSDK1210` warnings on older TFMs.\n\nFor a trim-only request, set `IsTrimmable` instead and leave IL3xxx warnings out of scope.\n\n### Step 2: Build and collect warnings\n\n```bash\ndotnet build \u003Cproject.csproj> -f \u003Cnet8.0-or-later-tfm> --no-incremental 2>&1 | grep 'IL[0-9]\\{4\\}'\n```\n\nSort and deduplicate. Common warning codes:\n- **IL2070**: Reflection call on a `Type` parameter missing `[DynamicallyAccessedMembers]`\n- **IL2067**: Passing an unannotated `Type` to a method expecting `[DynamicallyAccessedMembers]`\n- **IL2072**: Return value or extracted value missing annotation (often from unboxing)\n- **IL2057**: `Type.GetType(string)` with a non-constant argument\n- **IL2026**: Calling a method marked `[RequiresUnreferencedCode]`\n- **IL2050**: P\u002Finvoke method with COM marshalling parameters\n- **IL2075**: Return value flows into reflection without annotation\n- **IL2091**: Generic argument missing `[DynamicallyAccessedMembers]` required by constraint\n- **IL3000**: `Assembly.Location` returns empty string in single-file\u002FAOT apps\n- **IL3050**: Calling a method marked `[RequiresDynamicCode]`\n\n### Step 3: Triage warnings by code (do NOT read every file)\n\nGroup the warnings from Step 2 by warning code and count them. **Do not open individual files yet.** Identify the top 1-2 patterns by count — these drive your fix strategy:\n\n| Pattern | Typical fix |\n|---------|-------------|\n| Many IL2026 + IL3050 from `JsonSerializer` | **Go to Strategy C immediately** — create a `JsonSerializerContext`, then batch-update all call sites |\n| IL2070\u002FIL2087 on `Type` parameters | Add `[DynamicallyAccessedMembers]` to the innermost method, then cascade outward |\n| IL2067 passing unannotated `Type` | Annotate the parameter at the source |\n\n**In most real projects, IL2026\u002FIL3050 from JsonSerializer dominate.** Start with Strategy C unless the warning breakdown clearly shows otherwise. After the batch JSON fix, handle remaining warnings with Strategies A–B. Only use Strategy D as a last resort.\n\n### Step 4: Fix warnings iteratively (innermost first)\n\nWork from the **innermost** reflection call outward. Each fix may cascade new warnings to callers.\n\n**Stay warning-driven.** For each warning, open only the file and line the compiler reported, identify the pattern, apply the matching fix recipe below, and move on. Do not scan the codebase for similar patterns or try to understand the full architecture — fix what the compiler tells you, rebuild, and let new warnings guide the next change. Fix a small batch of warnings (5-10), then rebuild immediately to check progress.\n\n**Use sub-agents when available.** If you can launch sub-agents (e.g., via a `task` tool), dispatch **multiple sub-agents in parallel** to edit different files simultaneously. Keep the main loop focused on building, parsing warnings, and dispatching — delegate actual file edits to sub-agents. For batch JSON updates, give each sub-agent 5-10 files to update in one prompt. **After 2 build-fix cycles, dispatch all remaining file edits to sub-agents in parallel — do not continue fixing files sequentially.** Example:\n\n> Update these files to use source-generated JSON: `src\u002FModels\u002FResource.Serialization.cs`, `src\u002FModels\u002FIdentity.Serialization.cs`, `src\u002FModels\u002FPlan.Serialization.cs`. In each file, replace `JsonSerializer.Serialize(writer, value)` with `JsonSerializer.Serialize(writer, value, MyProjectJsonContext.Default.TypeName)` and `JsonSerializer.Deserialize\u003CT>(ref reader)` with `JsonSerializer.Deserialize(ref reader, MyProjectJsonContext.Default.TypeName)`. Only edit the JsonSerializer call sites.\n\n#### Strategy A: Add `[DynamicallyAccessedMembers]` (preferred)\n\nWhen a method uses reflection on a `Type` parameter, annotate the parameter to tell the trimmer what members are needed:\n\n```csharp\nusing System.Diagnostics.CodeAnalysis;\n\n\u002F\u002F Before (warns IL2070):\nvoid Process(Type t) {\n    var method = t.GetMethod(\"Foo\");  \u002F\u002F trimmer can't verify\n}\n\n\u002F\u002F After (clean):\nvoid Process([DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.PublicMethods)] Type t) {\n    var method = t.GetMethod(\"Foo\");  \u002F\u002F trimmer preserves public methods\n}\n```\n\nWhen you annotate a parameter, **all callers** must now pass properly annotated types. This cascades outward — follow each caller and annotate or refactor as needed. **The caller's annotation must include at least the same member types as the callee's.** If the callee requires `PublicConstructors | NonPublicConstructors`, the caller must specify the same or a superset — using only `NonPublicConstructors` will produce IL2091.\n\n#### Strategy B: Refactor to preserve annotation flow\n\nWhen annotation flow is broken by boxing (storing `Type` in `object`, `object[]`, or untyped collections), **refactor** to pass the `Type` directly:\n\n```csharp\n\u002F\u002F BROKEN: Type boxed into object[], annotation lost\nvoid Process(object[] args) {\n    Type t = (Type)args[0];  \u002F\u002F IL2072: annotation lost through boxing\n    Evaluate(t, ...);\n}\n\n\u002F\u002F FIXED: Pass Type as a separate, annotated parameter\nvoid Process(\n    object[] args,\n    [DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.PublicMethods)] Type calleeType,\n    ...) {\n    Evaluate(calleeType, ...);  \u002F\u002F annotation flows cleanly\n}\n```\n\nCommon patterns that break flow and how to fix them:\n- **`object[]` parameter bags**: Extract the `Type` into a dedicated annotated parameter\n- **Dictionary\u002FList storage**: Use a typed field with annotation instead\n- **Interface indirection**: Add annotation to the interface method's parameter\n- **Property with boxing getter**: Annotate the property's return type\n\n#### Strategy C: Source-generated JSON serialization (batch fix)\n\nWhen most warnings are IL2026\u002FIL3050 from `JsonSerializer.Serialize`\u002F`Deserialize`, this is a single mechanical fix applied in bulk:\n\n1. **Collect affected types** — grep for all `JsonSerializer.Serialize` and `JsonSerializer.Deserialize` call sites. Extract the type being serialized (the `\u003CT>` in `Deserialize\u003CT>`, or the runtime type of the object in `Serialize`).\n\n2. **Create one `JsonSerializerContext`** with `[JsonSerializable]` for every type found. **Skip types from external packages** (e.g., `ResponseError` from `Azure.Core`) — they won't source-generate for types you don't own. Handle external types separately via Gotcha #1 below.\n\n```csharp\n[JsonSerializable(typeof(ManagedServiceIdentity))]\n[JsonSerializable(typeof(SystemData))]\n\u002F\u002F ... one attribute per type YOU OWN\n\u002F\u002F Do NOT add types from external packages (e.g., ResponseError)\ninternal partial class MyProjectJsonContext : JsonSerializerContext { }\n```\n\n3. **Batch-update all call sites** — do not read each file individually. Apply the pattern mechanically:\n   - `JsonSerializer.Serialize(obj)` → `JsonSerializer.Serialize(obj, MyProjectJsonContext.Default.TypeName)`\n   - `JsonSerializer.Deserialize\u003CT>(json)` → `JsonSerializer.Deserialize(json, MyProjectJsonContext.Default.TypeName)`\n\n   Find and update all call sites in one pass:\n   ```bash\n   # Find all files with JsonSerializer calls\n   grep -rl 'JsonSerializer\\.\\(Serialize\\|Deserialize\\)' src\u002F --include='*.cs'\n   ```\n   Then use sequential `edit` calls to apply the same transformation to every matching file. **Do not use `sed` for C# code** — generics like `Deserialize\u003CT>()` have angle brackets and nested parentheses that sed will mangle.\n\n4. **Build once** to verify. Remaining warnings will be non-serialization issues — handle those with Strategies A–B or D.\n\n#### Strategy D: `[RequiresUnreferencedCode]` (last resort)\n\nWhen a method fundamentally requires arbitrary reflection that cannot be statically described:\n\n```csharp\n[RequiresUnreferencedCode(\"Loads plugins by name using Assembly.Load\")]\npublic void LoadPlugin(string assemblyName) {\n    var asm = Assembly.Load(assemblyName);\n    \u002F\u002F ...\n}\n```\n\nThis propagates to callers — they must also be annotated with `[RequiresUnreferencedCode]`. Use sparingly; it marks the entire call chain as trim-incompatible.\n\n### Step 5: Rebuild and repeat\n\nAfter each small batch of fixes (5-10 warnings), rebuild with `--no-incremental` and check for new warnings. **Do not attempt to fix all warnings before rebuilding** — frequent rebuilds catch mistakes early and reveal cascading warnings. Fixes cascade — annotating an inner method may surface warnings in its callers. Repeat until `0 Warning(s)`.\n\n### Step 6: Validate all TFMs\n\nBuild all target frameworks to ensure:\n- **0 IL warnings** on net8.0+ TFMs (for a trim-only request: 0 IL2xxx warnings, IL3xxx out of scope)\n- **No NETSDK1210 warnings** (the `IsAotCompatible` condition handles this)\n- **Clean builds** on older TFMs (netstandard2.0, net472, etc.)\n\n```bash\ndotnet build \u003Cproject.csproj>  # builds all TFMs\n```\n\n### Optional: lock the remaining warnings with a temporary baseline\n\nUse a warning-approval baseline only as a migration aid, when a run stops short of 0 IL warnings — for\nexample, when the Stop Signals below leave warnings that need architectural refactoring — and the user\nwants the remaining set locked. A baseline neither fixes nor suppresses a warning: every baselined\nwarning still appears in the build, and the Critical Rules above still apply to every fix.\n\n1. Keep the analyzers from Step 1 enabled (`IsAotCompatible` implies `EnableTrimAnalyzer` and `EnableAotAnalyzer`; for a trim-only request, `IsTrimmable` implies `EnableTrimAnalyzer`). If the repository treats warnings as errors, list the baselined IL codes in `WarningsNotAsErrors` so they stay warnings; never add them to `NoWarn`, which removes them from the build the baseline compares against.\n2. Build, capture the `IL2xxx`\u002F`IL3xxx` diagnostics, scrub volatile parts (absolute paths, line numbers), normalize separators, and group by file.\n3. Store the result as an approved baseline (a checked-in text file).\n4. Add an approval test that compares the current warnings against the baseline on every build. A new warning fails the build: fix it with the strategies above. Only the user approves a new warning into the baseline, in the same PR; never extend the baseline to make a build pass.\n\nOnce the warning set is empty, delete the approval test and the checked-in warning file, and enforce\ntrimming directly through the project analyzers and publish validation. A permanent baseline can hide\nregressions behind an ever-growing list.\n\n## Stop Signals\n\n- **Do not analyze more than 2-3 representative files per warning pattern.** After identifying the fix for a pattern, apply it to all matching files without reading each one first.\n- **Start fixing after one build.** Do not do a second analysis pass — begin implementing fixes for the most common warning pattern immediately after Step 3 triage.\n- Stop after achieving **0 IL warnings** for net8.0+ TFMs (for a trim-only request, 0 IL2xxx warnings). Don't optimize or refactor already-clean annotations.\n- If a warning requires **architectural refactoring** beyond annotation flow fixes (e.g., replacing an entire serialization layer), document it and stop — don't rewrite large subsystems.\n- Limit to **3 build-fix iterations** per warning. If annotation flow doesn't resolve it after 3 attempts, escalate to `[RequiresUnreferencedCode]`.\n- Don't chase warnings in **third-party dependencies** you can't modify. Note them and move on.\n- If the user asked a scoped question (e.g., \"fix warnings in this file\"), don't expand to the entire project.\n\n## Polyfills for Older TFMs\n\nFor multi-targeting projects that include netstandard2.0 or net472, you need polyfills for `DynamicallyAccessedMembersAttribute` and related types. See [references\u002Fpolyfills.md](references\u002Fpolyfills.md).\n\n## Common Gotchas\n\n1. **External types without AOT-safe serialization**: When a type comes from a dependency you can't modify (e.g., `ResponseError` from `Azure.Core`) and it lacks a source-generated serializer, `Options.GetConverter\u003CT>()` is reflection-based and will produce IL warnings. First check if the type implements `IJsonModel\u003CT>` (common in Azure SDK) — if so, bypass `JsonSerializer` entirely:\n\n```csharp\n\u002F\u002F Before (IL2026 — JsonSerializer uses reflection):\nJsonSerializer.Serialize(writer, errorValue);\n\n\u002F\u002F After (AOT-safe — uses IJsonModel directly):\n((IJsonModel\u003CResponseError>)errorValue).Write(writer, ModelReaderWriterOptions.Json);\n\n\u002F\u002F For deserialization:\nvar error = ((IJsonModel\u003CResponseError>)new ResponseError()).Create(ref reader, ModelReaderWriterOptions.Json);\n```\n\nDo **not** add the external type to your `JsonSerializerContext` — it won't source-generate for types you don't own. If the type doesn't implement `IJsonModel\u003CT>`, write a custom `JsonConverter\u003CT>` with manual `Utf8JsonReader`\u002F`Utf8JsonWriter` logic and register it via `[JsonSourceGenerationOptions]` on your context.\n\n2. **Serialization libraries**: Most reflection-based serializers (e.g., `Newtonsoft.Json`, `XmlSerializer`) are not AOT-compatible. Migrate to a source-generation-based serializer such as `System.Text.Json` with a `JsonSerializerContext`. If migration is not feasible, mark the serialization call site with `[RequiresUnreferencedCode]`.\n\n3. **Shared projects \u002F projitems**: When source is shared between multiple projects via `\u003CImport>`, annotations added to shared code affect ALL consuming projects. Verify that all consumers still build cleanly.\n\n## References\n\n[Limitations](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fdeploying\u002Fnative-aot\u002F?tabs=windows%2Cnet8#limitations-of-native-aot-deployment)\n[Conceptual: Understanding trimming](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fdeploying\u002Ftrimming\u002Ftrimming-concepts)\n[How-to: trim compat](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fdeploying\u002Ftrimming\u002Ffixing-warnings)\n\n## Checklist\n\nFor a trim-only request, the first three items read: `\u003CIsTrimmable>` instead of `\u003CIsAotCompatible>`, built with the trim analyzer, and every IL2xxx warning fixed, with IL3xxx out of scope.\n\n- [ ] Added `\u003CIsAotCompatible>` with TFM condition to .csproj\n- [ ] Built with AOT analyzers enabled (net8.0+ TFM)\n- [ ] Fixed all IL warnings via annotations or refactoring (or, on the user's choice, locked the rest with the optional temporary baseline above)\n- [ ] No `#pragma warning disable` or `[UnconditionalSuppressMessage]` used for any IL warning\n- [ ] Polyfills present for older TFMs if needed\n- [ ] All target frameworks build with 0 warnings (with that baseline: 0 warnings outside it)\n- [ ] Verified shared\u002Flinked source doesn't break sibling projects\n","# dotnet-aot-compat\n\nMake .NET projects compatible with Native AOT and trimming by systematically resolving all IL trim\u002FAOT analyzer warnings.\n\n## When to Use This Skill\n\n- **\"Make this project AOT-compatible\"**\n- **\"Fix trimming warnings\"** or **\"fix IL warnings\"**\n- **\"Resolve IL2070 \u002F IL2067 \u002F IL2072 \u002F IL2026 \u002F IL3050 warnings\"**\n- **\"Add DynamicallyAccessedMembers annotations\"**\n- **\"Enable IsAotCompatible in my .csproj\"**\n- **\"My project has trim analyzer warnings after upgrading to net8.0\"**\n- **\"Annotate reflection code for the trimmer\"**\n\n## When Not to Use This Skill\n\nDo not use this skill when the project exclusively targets .NET Framework (net4x), which does not support the trim\u002FAOT analyzers.\n\n## Prerequisites\n\nAn existing .NET project targeting net8.0 or later (or multi-targeting with at least one net8.0+ TFM) and the corresponding .NET SDK installed.\n\n## Background: What AOT Compatibility Means\n\nNative AOT and the IL trimmer perform static analysis to determine what code is reachable. Reflection can break this analysis because the trimmer can't see what types\u002Fmembers are accessed at runtime. The `IsAotCompatible` property enables analyzers that flag these issues as build warnings (ILXXXX codes).\n\n## Critical Rules\n\n### ❌ Never suppress warnings incorrectly\n\n- **NEVER** use `#pragma warning disable` for IL warnings. It hides warnings from the Roslyn analyzer at build time, but the IL linker and AOT compiler still see the issue. The code will fail at trim\u002Fpublish time.\n- **NEVER** use `[UnconditionalSuppressMessage]`. It tells both the analyzer AND the linker to ignore the warning, meaning the trimmer cannot verify safety. Raising an error at build time is always preferable to hiding the issue and having it silently break at runtime.\n\n### 💡 Preferred approaches\n\n- **Prefer** `[DynamicallyAccessedMembers]` annotations to flow type information through the call chain.\n- **Prefer** refactoring to eliminate patterns that break annotation flow (e.g., boxing `Type` through `object[]`).\n- **Use** `[RequiresUnreferencedCode]` \u002F `[RequiresDynamicCode]` \u002F `[RequiresAssemblyFiles]` to mark methods as fundamentally incompatible with trimming, propagating the requirement to callers. This surfaces the issue clearly rather than hiding it — callers must explicitly acknowledge the incompatibility.\n\n### Annotation flow is key\n\nThe trimmer tracks `[DynamicallyAccessedMembers]` annotations through assignments, parameter passing, and return values. If this flow is broken (e.g., by boxing a `Type` into `object`, storing in an untyped collection, or casting through interfaces), the trimmer loses track and warns. The fix is to preserve the flow, not suppress the warning.\n\n## Step-by-Step Procedure\n\n> **Do not explore the codebase up-front.** The build warnings tell you exactly which files and lines need changes. Follow a tight loop: **build → pick a warning → open that file at that line → apply the fix recipe → rebuild**. Reading or analyzing source files beyond what a specific warning points you to is wasted effort and leads to timeouts. Let the compiler guide you.\n>\n> ❌ Do NOT run `find`, `ls`, or `grep` to understand the project structure before building. Do NOT read README, docs, or architecture files. Your first action should be Step 1 (enable AOT analysis), then build.\n\n### Step 1: Enable AOT analysis in the .csproj\n\nAdd `IsAotCompatible`. If the project doesn't exclusively target net8.0+, add a TFM condition (AOT analysis requires net8.0+):\n\n```xml\n\u003CPropertyGroup>\n  \u003CIsAotCompatible Condition=\"$([MSBuild]::IsTargetFrameworkCompatible('$(TargetFramework)', 'net8.0'))\">true\u003C\u002FIsAotCompatible>\n\u003C\u002FPropertyGroup>\n```\n\nThis automatically sets `EnableTrimAnalyzer=true` and `EnableAotAnalyzer=true` for compatible TFMs. For multi-targeting projects (e.g., `netstandard2.0;net8.0`), the condition ensures no `NETSDK1210` warnings on older TFMs.\n\nFor a trim-only request, set `IsTrimmable` instead and leave IL3xxx warnings out of scope.\n\n### Step 2: Build and collect warnings\n\n```bash\ndotnet build \u003Cproject.csproj> -f \u003Cnet8.0-or-later-tfm> --no-incremental 2>&1 | grep 'IL[0-9]\\{4\\}'\n```\n\nSort and deduplicate. Common warning codes:\n- **IL2070**: Reflection call on a `Type` parameter missing `[DynamicallyAccessedMembers]`\n- **IL2067**: Passing an unannotated `Type` to a method expecting `[DynamicallyAccessedMembers]`\n- **IL2072**: Return value or extracted value missing annotation (often from unboxing)\n- **IL2057**: `Type.GetType(string)` with a non-constant argument\n- **IL2026**: Calling a method marked `[RequiresUnreferencedCode]`\n- **IL2050**: P\u002Finvoke method with COM marshalling parameters\n- **IL2075**: Return value flows into reflection without annotation\n- **IL2091**: Generic argument missing `[DynamicallyAccessedMembers]` required by constraint\n- **IL3000**: `Assembly.Location` returns empty string in single-file\u002FAOT apps\n- **IL3050**: Calling a method marked `[RequiresDynamicCode]`\n\n### Step 3: Triage warnings by code (do NOT read every file)\n\nGroup the warnings from Step 2 by warning code and count them. **Do not open individual files yet.** Identify the top 1-2 patterns by count — these drive your fix strategy:\n\n| Pattern | Typical fix |\n|---------|-------------|\n| Many IL2026 + IL3050 from `JsonSerializer` | **Go to Strategy C immediately** — create a `JsonSerializerContext`, then batch-update all call sites |\n| IL2070\u002FIL2087 on `Type` parameters | Add `[DynamicallyAccessedMembers]` to the innermost method, then cascade outward |\n| IL2067 passing unannotated `Type` | Annotate the parameter at the source |\n\n**In most real projects, IL2026\u002FIL3050 from JsonSerializer dominate.** Start with Strategy C unless the warning breakdown clearly shows otherwise. After the batch JSON fix, handle remaining warnings with Strategies A–B. Only use Strategy D as a last resort.\n\n### Step 4: Fix warnings iteratively (innermost first)\n\nWork from the **innermost** reflection call outward. Each fix may cascade new warnings to callers.\n\n**Stay warning-driven.** For each warning, open only the file and line the compiler reported, identify the pattern, apply the matching fix recipe below, and move on. Do not scan the codebase for similar patterns or try to understand the full architecture — fix what the compiler tells you, rebuild, and let new warnings guide the next change. Fix a small batch of warnings (5-10), then rebuild immediately to check progress.\n\n**Use sub-agents when available.** If you can launch sub-agents (e.g., via a `task` tool), dispatch **multiple sub-agents in parallel** to edit different files simultaneously. Keep the main loop focused on building, parsing warnings, and dispatching — delegate actual file edits to sub-agents. For batch JSON updates, give each sub-agent 5-10 files to update in one prompt. **After 2 build-fix cycles, dispatch all remaining file edits to sub-agents in parallel — do not continue fixing files sequentially.** Example:\n\n> Update these files to use source-generated JSON: `src\u002FModels\u002FResource.Serialization.cs`, `src\u002FModels\u002FIdentity.Serialization.cs`, `src\u002FModels\u002FPlan.Serialization.cs`. In each file, replace `JsonSerializer.Serialize(writer, value)` with `JsonSerializer.Serialize(writer, value, MyProjectJsonContext.Default.TypeName)` and `JsonSerializer.Deserialize\u003CT>(ref reader)` with `JsonSerializer.Deserialize(ref reader, MyProjectJsonContext.Default.TypeName)`. Only edit the JsonSerializer call sites.\n\n#### Strategy A: Add `[DynamicallyAccessedMembers]` (preferred)\n\nWhen a method uses reflection on a `Type` parameter, annotate the parameter to tell the trimmer what members are needed:\n\n```csharp\nusing System.Diagnostics.CodeAnalysis;\n\n\u002F\u002F Before (warns IL2070):\nvoid Process(Type t) {\n    var method = t.GetMethod(\"Foo\");  \u002F\u002F trimmer can't verify\n}\n\n\u002F\u002F After (clean):\nvoid Process([DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.PublicMethods)] Type t) {\n    var method = t.GetMethod(\"Foo\");  \u002F\u002F trimmer preserves public methods\n}\n```\n\nWhen you annotate a parameter, **all callers** must now pass properly annotated types. This cascades outward — follow each caller and annotate or refactor as needed. **The caller's annotation must include at least the same member types as the callee's.** If the callee requires `PublicConstructors | NonPublicConstructors`, the caller must specify the same or a superset — using only `NonPublicConstructors` will produce IL2091.\n\n#### Strategy B: Refactor to preserve annotation flow\n\nWhen annotation flow is broken by boxing (storing `Type` in `object`, `object[]`, or untyped collections), **refactor** to pass the `Type` directly:\n\n```csharp\n\u002F\u002F BROKEN: Type boxed into object[], annotation lost\nvoid Process(object[] args) {\n    Type t = (Type)args[0];  \u002F\u002F IL2072: annotation lost through boxing\n    Evaluate(t, ...);\n}\n\n\u002F\u002F FIXED: Pass Type as a separate, annotated parameter\nvoid Process(\n    object[] args,\n    [DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.PublicMethods)] Type calleeType,\n    ...) {\n    Evaluate(calleeType, ...);  \u002F\u002F annotation flows cleanly\n}\n```\n\nCommon patterns that break flow and how to fix them:\n- **`object[]` parameter bags**: Extract the `Type` into a dedicated annotated parameter\n- **Dictionary\u002FList storage**: Use a typed field with annotation instead\n- **Interface indirection**: Add annotation to the interface method's parameter\n- **Property with boxing getter**: Annotate the property's return type\n\n#### Strategy C: Source-generated JSON serialization (batch fix)\n\nWhen most warnings are IL2026\u002FIL3050 from `JsonSerializer.Serialize`\u002F`Deserialize`, this is a single mechanical fix applied in bulk:\n\n1. **Collect affected types** — grep for all `JsonSerializer.Serialize` and `JsonSerializer.Deserialize` call sites. Extract the type being serialized (the `\u003CT>` in `Deserialize\u003CT>`, or the runtime type of the object in `Serialize`).\n\n2. **Create one `JsonSerializerContext`** with `[JsonSerializable]` for every type found. **Skip types from external packages** (e.g., `ResponseError` from `Azure.Core`) — they won't source-generate for types you don't own. Handle external types separately via Gotcha #1 below.\n\n```csharp\n[JsonSerializable(typeof(ManagedServiceIdentity))]\n[JsonSerializable(typeof(SystemData))]\n\u002F\u002F ... one attribute per type YOU OWN\n\u002F\u002F Do NOT add types from external packages (e.g., ResponseError)\ninternal partial class MyProjectJsonContext : JsonSerializerContext { }\n```\n\n3. **Batch-update all call sites** — do not read each file individually. Apply the pattern mechanically:\n   - `JsonSerializer.Serialize(obj)` → `JsonSerializer.Serialize(obj, MyProjectJsonContext.Default.TypeName)`\n   - `JsonSerializer.Deserialize\u003CT>(json)` → `JsonSerializer.Deserialize(json, MyProjectJsonContext.Default.TypeName)`\n\n   Find and update all call sites in one pass:\n   ```bash\n   # Find all files with JsonSerializer calls\n   grep -rl 'JsonSerializer\\.\\(Serialize\\|Deserialize\\)' src\u002F --include='*.cs'\n   ```\n   Then use sequential `edit` calls to apply the same transformation to every matching file. **Do not use `sed` for C# code** — generics like `Deserialize\u003CT>()` have angle brackets and nested parentheses that sed will mangle.\n\n4. **Build once** to verify. Remaining warnings will be non-serialization issues — handle those with Strategies A–B or D.\n\n#### Strategy D: `[RequiresUnreferencedCode]` (last resort)\n\nWhen a method fundamentally requires arbitrary reflection that cannot be statically described:\n\n```csharp\n[RequiresUnreferencedCode(\"Loads plugins by name using Assembly.Load\")]\npublic void LoadPlugin(string assemblyName) {\n    var asm = Assembly.Load(assemblyName);\n    \u002F\u002F ...\n}\n```\n\nThis propagates to callers — they must also be annotated with `[RequiresUnreferencedCode]`. Use sparingly; it marks the entire call chain as trim-incompatible.\n\n### Step 5: Rebuild and repeat\n\nAfter each small batch of fixes (5-10 warnings), rebuild with `--no-incremental` and check for new warnings. **Do not attempt to fix all warnings before rebuilding** — frequent rebuilds catch mistakes early and reveal cascading warnings. Fixes cascade — annotating an inner method may surface warnings in its callers. Repeat until `0 Warning(s)`.\n\n### Step 6: Validate all TFMs\n\nBuild all target frameworks to ensure:\n- **0 IL warnings** on net8.0+ TFMs (for a trim-only request: 0 IL2xxx warnings, IL3xxx out of scope)\n- **No NETSDK1210 warnings** (the `IsAotCompatible` condition handles this)\n- **Clean builds** on older TFMs (netstandard2.0, net472, etc.)\n\n```bash\ndotnet build \u003Cproject.csproj>  # builds all TFMs\n```\n\n### Optional: lock the remaining warnings with a temporary baseline\n\nUse a warning-approval baseline only as a migration aid, when a run stops short of 0 IL warnings — for\nexample, when the Stop Signals below leave warnings that need architectural refactoring — and the user\nwants the remaining set locked. A baseline neither fixes nor suppresses a warning: every baselined\nwarning still appears in the build, and the Critical Rules above still apply to every fix.\n\n1. Keep the analyzers from Step 1 enabled (`IsAotCompatible` implies `EnableTrimAnalyzer` and `EnableAotAnalyzer`; for a trim-only request, `IsTrimmable` implies `EnableTrimAnalyzer`). If the repository treats warnings as errors, list the baselined IL codes in `WarningsNotAsErrors` so they stay warnings; never add them to `NoWarn`, which removes them from the build the baseline compares against.\n2. Build, capture the `IL2xxx`\u002F`IL3xxx` diagnostics, scrub volatile parts (absolute paths, line numbers), normalize separators, and group by file.\n3. Store the result as an approved baseline (a checked-in text file).\n4. Add an approval test that compares the current warnings against the baseline on every build. A new warning fails the build: fix it with the strategies above. Only the user approves a new warning into the baseline, in the same PR; never extend the baseline to make a build pass.\n\nOnce the warning set is empty, delete the approval test and the checked-in warning file, and enforce\ntrimming directly through the project analyzers and publish validation. A permanent baseline can hide\nregressions behind an ever-growing list.\n\n## Stop Signals\n\n- **Do not analyze more than 2-3 representative files per warning pattern.** After identifying the fix for a pattern, apply it to all matching files without reading each one first.\n- **Start fixing after one build.** Do not do a second analysis pass — begin implementing fixes for the most common warning pattern immediately after Step 3 triage.\n- Stop after achieving **0 IL warnings** for net8.0+ TFMs (for a trim-only request, 0 IL2xxx warnings). Don't optimize or refactor already-clean annotations.\n- If a warning requires **architectural refactoring** beyond annotation flow fixes (e.g., replacing an entire serialization layer), document it and stop — don't rewrite large subsystems.\n- Limit to **3 build-fix iterations** per warning. If annotation flow doesn't resolve it after 3 attempts, escalate to `[RequiresUnreferencedCode]`.\n- Don't chase warnings in **third-party dependencies** you can't modify. Note them and move on.\n- If the user asked a scoped question (e.g., \"fix warnings in this file\"), don't expand to the entire project.\n\n## Polyfills for Older TFMs\n\nFor multi-targeting projects that include netstandard2.0 or net472, you need polyfills for `DynamicallyAccessedMembersAttribute` and related types. See [references\u002Fpolyfills.md](references\u002Fpolyfills.md).\n\n## Common Gotchas\n\n1. **External types without AOT-safe serialization**: When a type comes from a dependency you can't modify (e.g., `ResponseError` from `Azure.Core`) and it lacks a source-generated serializer, `Options.GetConverter\u003CT>()` is reflection-based and will produce IL warnings. First check if the type implements `IJsonModel\u003CT>` (common in Azure SDK) — if so, bypass `JsonSerializer` entirely:\n\n```csharp\n\u002F\u002F Before (IL2026 — JsonSerializer uses reflection):\nJsonSerializer.Serialize(writer, errorValue);\n\n\u002F\u002F After (AOT-safe — uses IJsonModel directly):\n((IJsonModel\u003CResponseError>)errorValue).Write(writer, ModelReaderWriterOptions.Json);\n\n\u002F\u002F For deserialization:\nvar error = ((IJsonModel\u003CResponseError>)new ResponseError()).Create(ref reader, ModelReaderWriterOptions.Json);\n```\n\nDo **not** add the external type to your `JsonSerializerContext` — it won't source-generate for types you don't own. If the type doesn't implement `IJsonModel\u003CT>`, write a custom `JsonConverter\u003CT>` with manual `Utf8JsonReader`\u002F`Utf8JsonWriter` logic and register it via `[JsonSourceGenerationOptions]` on your context.\n\n2. **Serialization libraries**: Most reflection-based serializers (e.g., `Newtonsoft.Json`, `XmlSerializer`) are not AOT-compatible. Migrate to a source-generation-based serializer such as `System.Text.Json` with a `JsonSerializerContext`. If migration is not feasible, mark the serialization call site with `[RequiresUnreferencedCode]`.\n\n3. **Shared projects \u002F projitems**: When source is shared between multiple projects via `\u003CImport>`, annotations added to shared code affect ALL consuming projects. Verify that all consumers still build cleanly.\n\n## References\n\n[Limitations](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fdeploying\u002Fnative-aot\u002F?tabs=windows%2Cnet8#limitations-of-native-aot-deployment)\n[Conceptual: Understanding trimming](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fdeploying\u002Ftrimming\u002Ftrimming-concepts)\n[How-to: trim compat](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fdeploying\u002Ftrimming\u002Ffixing-warnings)\n\n## Checklist\n\nFor a trim-only request, the first three items read: `\u003CIsTrimmable>` instead of `\u003CIsAotCompatible>`, built with the trim analyzer, and every IL2xxx warning fixed, with IL3xxx out of scope.\n\n- [ ] Added `\u003CIsAotCompatible>` with TFM condition to .csproj\n- [ ] Built with AOT analyzers enabled (net8.0+ TFM)\n- [ ] Fixed all IL warnings via annotations or refactoring (or, on the user's choice, locked the rest with the optional temporary baseline above)\n- [ ] No `#pragma warning disable` or `[UnconditionalSuppressMessage]` used for any IL warning\n- [ ] Polyfills present for older TFMs if needed\n- [ ] All target frameworks build with 0 warnings (with that baseline: 0 warnings outside it)\n- [ ] Verified shared\u002Flinked source doesn't break sibling projects\n",{"name":5,"metadata":24,"description":25},{"opencode\u002Fautoinvoke":20},"Make .NET projects compatible with Native AOT and trimming by systematically resolving IL trim\u002FAOT analyzer warnings. USE FOR: making projects AOT-compatible, fixing trimming warnings, resolving IL warnings (IL2026, IL2070, IL2067, IL2072, IL3050), adding DynamicallyAccessedMembers annotations, enabling IsAotCompatible. DO NOT USE FOR: publishing native AOT binaries, optimizing binary size, replacing reflection-heavy libraries with alternatives. INVOKES: dotnet build, grep, project and source edits, and sub-agents where available.\n","master","b30b1c1908dbc56a8184128f18803053d762ccb5","opencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.dotnet-aot-compat",0,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins","https:\u002F\u002Fgithub.com\u002FBlind-Striker","denizirgin.com","VP of Engineering - \r\n@armutcom @homeruntech @prontopro\r\n |  Speaker \r\n@CodeFiction\r\n, http:\u002F\u002Fcodefiction.tech | Developer, gamer, blogger, maiden iron fan","2026-11-13 00:23:18",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.dotnet-aot-compat",{"tool":41,"command":42},"bunx","bunx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.dotnet-aot-compat",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.dotnet-aot-compat","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.dotnet-aot-compat\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fpolyfills.md","REFERENCE","参考文档",1625,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.dotnet-aot-compat\u002Freferences\u002Fpolyfills.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79YGWBJ52PHMSTKJ3RJ3AWR","writing-tunit-tests","Write tests in TUnit — the attributes, the async assertion model, data-driven cases, lifecycle hooks, and the parallelism rules. USE FOR writing or fixing a test in a TUnit project, translating a test idea into TUnit syntax, or reviewing TUnit test code for API mistakes. DO NOT USE FOR deciding what to test, judging whether a test is any good, or running tests.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fwriting-tunit-tests\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79YGR3Y9RCRS6TD71D0KKP8","dotnet-walls","Walls for a .NET change in a repository without its own quality gates — pinned, ephemeral analyzer, format, clone and scanner commands for the verify step, their identity ratchet, and the build traps. Use during a walls preflight, or when a worker's verify step needs .NET quality gates.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fdotnet-walls\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79YGFNJBST7D803NQW3SBYM","csharp-15","Write, review and modernize C# 15 (.NET 11) code correctly. Covers every C# 15 feature - collection expression arguments (`[with(...), ...]`), union types (`union`, `[Union]`, `IUnion`, custom unions), closed class hierarchies (`closed`), extension indexers, labeled `break`\u002F`continue`, non-virtual static interface members on runtimes without default interface methods, and the preview memory-safety model (`unsafe(expr)`, `safe`, requires-unsafe members). Use when code targets net11.0 or LangVersion 15\u002Fpreview, when the user mentions any of these features, when replacing marker interfaces, OneOf-style results, `goto`\u002Fflag loop exits or capacity\u002Fcomparer boilerplate, or when the build reports CS8121, CS8509, CS8655, CS8510, CS0121\u002FCS0411 on a `with(...)` element, CS9370, CS9380 or CS9363.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fcsharp-15\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79YGAV031473HSX6FN87ENH","verified-waves","Run one task as verified multi-agent waves. Plans the fan-out, sends findings to fresh skeptics, keeps a ledger, and reports N of M done; small tasks stay solo.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fverified-waves\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79YG6QXNND4WRPP3GATSY8J","harness","The bundled dispatch harness, which runs a task file on worker models through OpenCode or Codex, fences their writes, escalates their asks to the operator, settles each result from git and its verify commands, and records every step in a ledger. Its commands, task file, modes and write fence, configuration, runs and their recovery, ledger and exit codes.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fharness\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79YG2P5S91SDTA5912XJ4FV","delegating-to-worker-models","Use when you hand off implementation, a plan, research a decision will rely on, or a review, and you brief the worker and check what comes back. A subagent that searches, reads in parallel, or keeps your context small is ordinary tool use. Covers what stays with you, the mechanism, assigning work by strength, the walls preflight, prompts without contradictions, the worker contract and model profiles, evidence from your own run, review, and the fix-up loop.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fdelegating-to-worker-models\u002FSKILL.md",[],[]]