[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D04R01MM2GS9FAJ15B1CKQ":3,"skill-same:01M7D04R01MM2GS9FAJ15B1CKQ":44},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7D04R01MM2GS9FAJ15B1CKQ","csharp-scripts",null,"Run file-based C# apps with the .NET CLI when the user explicitly wants C#\u002F.NET code without creating a project. Use for C# language\u002FAPI experiments, one-file C# apps, small multi-file C# apps composed with `#:include`\u002F`#:exclude`, or C# file-based apps linked with `#:ref`. Do not use for language-agnostic throwaway scripts, generic computations, Python\u002FPowerShell-style automation, full projects, or existing app integration.","itsmejay18\u002FAI-Skills-for-My-Development-Stack","itsmejay18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167779943?v=4","01M7CZRFC6DDZA5V2CX8WDSZED","Jay Jemino Ababon ","01M7CZRFCVRNW1SFHSQXEJ3CQN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F02-CSharp-WPF-Desktop-Development\u002Fcsharp-scripts\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: csharp-scripts\ndescription: \"Run file-based C# apps with the .NET CLI when the user explicitly wants C#\u002F.NET code without creating a project. Use for C# language\u002FAPI experiments, one-file C# apps, small multi-file C# apps composed with `#:include`\u002F`#:exclude`, or C# file-based apps linked with `#:ref`. Do not use for language-agnostic throwaway scripts, generic computations, Python\u002FPowerShell-style automation, full projects, or existing app integration.\"\nlicense: MIT\n---\n\n# File-Based C# Apps\n\n## When to Use\n\n- Testing a C# concept, API, or language feature with a quick file-based app\n- Prototyping logic before integrating it into a larger project\n- Building a small utility from one entry-point file and a few helper `.cs` files\n\n## When Not to Use\n\n- The user asks for a language-agnostic quick script, throwaway computation, or shell\u002FPython\u002FPowerShell-style automation\n- The user needs a full project, solution integration, or project references in an existing app\n- The user is working inside an existing .NET solution and wants to add code there\n- The app is large enough that project structure, build customization, tests, or publish configuration should live in a `.csproj`\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| C# code or intent | Yes | The code to run, or a description of what the file-based app should do |\n\n## Workflow\n\n### Step 1: Check the .NET SDK version\n\nRun `dotnet --version` to verify the SDK is installed and note the full version, including the feature band. File-based apps require .NET 10 or later. `#:include`, `#:exclude`, and transitive directive processing require SDK 10.0.300 or later; SDK 10.0.100\u002F10.0.200 builds can run single-file apps but do not support those multi-file directives. If the version is below 10, follow the [fallback for older SDKs](#fallback-for-net-9-and-earlier) instead.\n\n### Step 2: Write the app file\n\nCreate an entry-point `.cs` file using top-level statements. Place it outside any existing project directory to avoid conflicts with `.csproj` files.\n\n```csharp\n#!\u002Fusr\u002Fbin\u002Fenv dotnet\n\u002F\u002F hello.cs\nConsole.WriteLine(\"Hello from a file-based app!\");\n\nvar numbers = new[] { 1, 2, 3, 4, 5 };\nConsole.WriteLine($\"Sum: {numbers.Sum()}\");\n```\n\nGuidelines:\n\n- Use top-level statements (no `Main` method, class, or namespace boilerplate)\n- Place `using` directives at the top of the file (after the `#!` line and any `#:` directives if present)\n- Place type declarations (classes, records, enums) after all top-level statements\n\n### Step 3: Run the app\n\n```bash\ndotnet hello.cs\n```\n\nBuilds and runs the file automatically. Cached so subsequent runs are fast. Pass arguments after `--`:\n\n```bash\ndotnet hello.cs -- arg1 arg2 \"multi word arg\"\n```\n\n### Step 4: Add directives (if needed)\n\nPlace directives at the top of the file (immediately after an optional shebang line), before any `using` directives or other C# code. All directives start with `#:`.\n\n#### `#:package` — NuGet package references\n\nSpecify a version unless the app intentionally uses central package management. Use `@*` when the latest available package is acceptable (or `@*-*` for pre-release):\n\n```csharp\n#:package Humanizer@2.14.1\n\nusing Humanizer;\n\nConsole.WriteLine(\"hello world\".Titleize());\n```\n\n#### `#:property` — MSBuild properties\n\nSet any MSBuild property inline. Syntax: `#:property PropertyName=Value`\n\n```csharp\n#:property AllowUnsafeBlocks=true\n#:property PublishAot=false\n#:property NoWarn=CS0162\n```\n\nMSBuild expressions and property functions are supported:\n\n```csharp\n#:property LogLevel=$([MSBuild]::ValueOrDefault('$(LOG_LEVEL)', 'Information'))\n```\n\nCommon properties:\n\n| Property | Purpose |\n|----------|---------|\n| `AllowUnsafeBlocks=true` | Enable `unsafe` code |\n| `PublishAot=false` | Disable native AOT (enabled by default) |\n| `NoWarn=CS0162;CS0219` | Suppress specific warnings |\n| `LangVersion=preview` | Enable preview language features |\n| `InvariantGlobalization=false` | Enable culture-specific globalization |\n\n#### `#:project` — Project references\n\nReference another project by relative path:\n\n```csharp\n#:project ..\u002FMyLibrary\u002FMyLibrary.csproj\n```\n\n#### `#:ref` — File-based app references\n\nReference another `.cs` file as a separate file-based app project when it should compile into a separate assembly instead of being included in the same compilation. Use `#:include` for ordinary helper files that should share the same assembly as the entry point; use `#:ref` when you want project-reference-like boundaries.\n\n```csharp\n#:property ExperimentalFileBasedProgramEnableRefDirective=true\n#:ref ..\u002FShared\u002FFormatter.cs\n\nConsole.WriteLine(Formatter.Title(\"hello world\"));\n```\n\nGuidelines:\n\n- The referenced file is compiled as its own virtual project and added as a project reference.\n- If the referenced file is a library without top-level statements, put `#:property OutputType=Library` in that referenced file.\n- Members that must be consumed by the referencing app should be public; internal members are not visible across the assembly boundary.\n- `#:ref` is transitive: a referenced file can contain its own `#:ref` and other `#:` directives.\n- Relative paths are resolved relative to the file containing the directive.\n- Some SDK builds require `#:property ExperimentalFileBasedProgramEnableRefDirective=true`; remove that property if the SDK accepts `#:ref` without it.\n\n#### `#:sdk` — SDK selection\n\nOverride the default SDK (`Microsoft.NET.Sdk`):\n\n```csharp\n#:sdk Microsoft.NET.Sdk.Web\n```\n\n#### `#:include` and `#:exclude` — Multi-file apps\n\nIn .NET SDK 10.0.300 and later, file-based apps can include additional files in the same virtual project. Check the full `dotnet --version` output before using these directives; a 10.0.100 or 10.0.200 SDK is still .NET 10 but does not support them. Use `#:include` for helper source files and supported assets, and `#:exclude` to remove files from an include pattern or default item set.\n\n```csharp\n#!\u002Fusr\u002Fbin\u002Fenv dotnet\n#:include Helpers.cs\n#:include Models\u002F*.cs\n#:exclude Models\u002FGenerated\u002F*.cs\n\nConsole.WriteLine(Formatter.Title(\"hello world\"));\n```\n\nGuidelines:\n\n- Treat the file passed to `dotnet` as the entry point; put top-level statements there.\n- Put declarations such as classes, records, and enums in included `.cs` files.\n- Prefer explicit globs such as `Helpers.cs` or `Models\u002F*.cs` over broad recursive globs.\n- Paths are resolved relative to the file containing the directive.\n- Include directives from non-entry-point C# files are processed too, so a helper file can declare its own `#:package`, `#:property`, `#:sdk`, `#:project`, `#:ref`, `#:include`, or `#:exclude` directives.\n- Avoid duplicate directives across included files unless the directive kind explicitly supports duplicates; duplicate `#:package`, `#:property`, `#:sdk`, `#:include`, and `#:exclude` entries can fail.\n- When an app uses `#:include`, add a shebang (`#!\u002Fusr\u002Fbin\u002Fenv dotnet`) to the entry-point file on Unix-like systems to make the entry point clear to tools. Use `LF` line endings and no BOM for shebang files.\n\nExample layout:\n\n```text\nscratch\u002F\n    hello.cs\n    Helpers.cs\n    Models\u002F\n        Person.cs\n```\n\n```csharp\n#!\u002Fusr\u002Fbin\u002Fenv dotnet\n\u002F\u002F hello.cs\n#:include Helpers.cs\n#:include Models\u002F*.cs\n\nvar person = new Person(\"Ada\");\nConsole.WriteLine(Formatter.Title(person.Name));\n```\n\n```csharp\n\u002F\u002F Helpers.cs\nstatic class Formatter\n{\n    public static string Title(string value) => value.ToUpperInvariant();\n}\n```\n\n```csharp\n\u002F\u002F Models\u002FPerson.cs\nrecord Person(string Name);\n```\n\n### Step 5: Clean up\n\nRemove the app files when the user is done. To clear cached build artifacts:\n\n```bash\ndotnet clean hello.cs\n```\n\n## Unix shebang support\n\nOn Unix platforms, make a `.cs` file directly executable:\n\n1. Add a shebang as the first line of the file:\n\n    ```csharp\n    #!\u002Fusr\u002Fbin\u002Fenv dotnet\n    Console.WriteLine(\"I'm executable!\");\n    ```\n\n2. Set execute permissions:\n\n    ```bash\n    chmod +x hello.cs\n    ```\n\n3. Run directly:\n\n    ```bash\n    .\u002Fhello.cs\n    ```\n\nUse `LF` line endings (not `CRLF`) when adding a shebang. This directive is ignored on Windows.\n\n## Source-generated JSON\n\nFile-based apps enable native AOT by default. Reflection-based APIs like `JsonSerializer.Serialize\u003CT>(value)` fail at runtime under AOT. Use source-generated serialization instead:\n\n```csharp\nusing System.Text.Json;\nusing System.Text.Json.Serialization;\n\nvar person = new Person(\"Alice\", 30);\nvar json = JsonSerializer.Serialize(person, AppJsonContext.Default.Person);\nConsole.WriteLine(json);\n\nvar deserialized = JsonSerializer.Deserialize(json, AppJsonContext.Default.Person);\nConsole.WriteLine($\"Name: {deserialized!.Name}, Age: {deserialized.Age}\");\n\nrecord Person(string Name, int Age);\n\n[JsonSerializable(typeof(Person))]\npartial class AppJsonContext : JsonSerializerContext;\n```\n\n## Converting to a project\n\nWhen a file-based app outgrows this workflow, convert it to a full project:\n\n```bash\ndotnet project convert hello.cs\n```\n\n## Fallback for .NET 9 and earlier\n\nIf the .NET SDK version is below 10, file-based apps are not available. Use a temporary console project instead:\n\n```bash\nmkdir -p \u002Ftmp\u002Fcsharp-file-based-app && cd \u002Ftmp\u002Fcsharp-file-based-app\ndotnet new console -o . --force\n```\n\nReplace the generated `Program.cs` with the app content and run with `dotnet run`. Add NuGet packages with `dotnet add package \u003Cname>`. Remove the directory when done.\n\n## Validation\n\n- [ ] `dotnet --version` reports 10.0 or later (or fallback path is used)\n- [ ] If the app uses `#:include`, `#:exclude`, or transitive directives from included files, `dotnet --version` reports SDK 10.0.300 or later\n- [ ] The app compiles without errors (can be checked explicitly with `dotnet build \u003Cfile>.cs`)\n- [ ] `dotnet \u003Cfile>.cs` produces the expected output\n- [ ] Multi-file apps include every required helper file and exclude unintended matches\n- [ ] App files and cached artifacts are cleaned up after the session\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| `.cs` file is inside a directory with a `.csproj` | Move the app outside the project directory, or use `dotnet run --file file.cs` |\n| `#:package` without a version | Specify a version: `#:package PackageName@1.2.3` or `@*` for latest |\n| `#:property` with wrong syntax | Use `PropertyName=Value` with no spaces around `=` and no quotes: `#:property AllowUnsafeBlocks=true` |\n| Directives placed after C# code | All `#:` directives must appear immediately after an optional shebang line (if present) and before any `using` directives or other C# statements |\n| Helper file is not compiled | Add `#:include Helper.cs` or an appropriate glob to the entry-point file |\n| Shared file needs an assembly boundary | Use `#:ref Shared.cs` instead of `#:include Shared.cs`, and set `#:property OutputType=Library` in the referenced file if it has no entry point |\n| Broad include pulls in unrelated files | Prefer narrow include patterns and use `#:exclude` for generated, backup, or experimental files |\n| Duplicate directives in included files | Keep package, property, SDK, include, and exclude directives unique across the entry point and included C# files |\n| Reflection-based JSON serialization fails | Use source-generated JSON with `JsonSerializerContext` (see [Source-generated JSON](#source-generated-json)) |\n| Unexpected build behavior or version errors | File-based apps inherit `global.json`, `Directory.Build.props`, `Directory.Build.targets`, and `nuget.config` from parent directories. Move the app to an isolated directory if the inherited settings conflict |\n\n## More info\n\nSee https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fsdk\u002Ffile-based-apps for a full reference on file-based apps.\n","# File-Based C# Apps\n\n## When to Use\n\n- Testing a C# concept, API, or language feature with a quick file-based app\n- Prototyping logic before integrating it into a larger project\n- Building a small utility from one entry-point file and a few helper `.cs` files\n\n## When Not to Use\n\n- The user asks for a language-agnostic quick script, throwaway computation, or shell\u002FPython\u002FPowerShell-style automation\n- The user needs a full project, solution integration, or project references in an existing app\n- The user is working inside an existing .NET solution and wants to add code there\n- The app is large enough that project structure, build customization, tests, or publish configuration should live in a `.csproj`\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| C# code or intent | Yes | The code to run, or a description of what the file-based app should do |\n\n## Workflow\n\n### Step 1: Check the .NET SDK version\n\nRun `dotnet --version` to verify the SDK is installed and note the full version, including the feature band. File-based apps require .NET 10 or later. `#:include`, `#:exclude`, and transitive directive processing require SDK 10.0.300 or later; SDK 10.0.100\u002F10.0.200 builds can run single-file apps but do not support those multi-file directives. If the version is below 10, follow the [fallback for older SDKs](#fallback-for-net-9-and-earlier) instead.\n\n### Step 2: Write the app file\n\nCreate an entry-point `.cs` file using top-level statements. Place it outside any existing project directory to avoid conflicts with `.csproj` files.\n\n```csharp\n#!\u002Fusr\u002Fbin\u002Fenv dotnet\n\u002F\u002F hello.cs\nConsole.WriteLine(\"Hello from a file-based app!\");\n\nvar numbers = new[] { 1, 2, 3, 4, 5 };\nConsole.WriteLine($\"Sum: {numbers.Sum()}\");\n```\n\nGuidelines:\n\n- Use top-level statements (no `Main` method, class, or namespace boilerplate)\n- Place `using` directives at the top of the file (after the `#!` line and any `#:` directives if present)\n- Place type declarations (classes, records, enums) after all top-level statements\n\n### Step 3: Run the app\n\n```bash\ndotnet hello.cs\n```\n\nBuilds and runs the file automatically. Cached so subsequent runs are fast. Pass arguments after `--`:\n\n```bash\ndotnet hello.cs -- arg1 arg2 \"multi word arg\"\n```\n\n### Step 4: Add directives (if needed)\n\nPlace directives at the top of the file (immediately after an optional shebang line), before any `using` directives or other C# code. All directives start with `#:`.\n\n#### `#:package` — NuGet package references\n\nSpecify a version unless the app intentionally uses central package management. Use `@*` when the latest available package is acceptable (or `@*-*` for pre-release):\n\n```csharp\n#:package Humanizer@2.14.1\n\nusing Humanizer;\n\nConsole.WriteLine(\"hello world\".Titleize());\n```\n\n#### `#:property` — MSBuild properties\n\nSet any MSBuild property inline. Syntax: `#:property PropertyName=Value`\n\n```csharp\n#:property AllowUnsafeBlocks=true\n#:property PublishAot=false\n#:property NoWarn=CS0162\n```\n\nMSBuild expressions and property functions are supported:\n\n```csharp\n#:property LogLevel=$([MSBuild]::ValueOrDefault('$(LOG_LEVEL)', 'Information'))\n```\n\nCommon properties:\n\n| Property | Purpose |\n|----------|---------|\n| `AllowUnsafeBlocks=true` | Enable `unsafe` code |\n| `PublishAot=false` | Disable native AOT (enabled by default) |\n| `NoWarn=CS0162;CS0219` | Suppress specific warnings |\n| `LangVersion=preview` | Enable preview language features |\n| `InvariantGlobalization=false` | Enable culture-specific globalization |\n\n#### `#:project` — Project references\n\nReference another project by relative path:\n\n```csharp\n#:project ..\u002FMyLibrary\u002FMyLibrary.csproj\n```\n\n#### `#:ref` — File-based app references\n\nReference another `.cs` file as a separate file-based app project when it should compile into a separate assembly instead of being included in the same compilation. Use `#:include` for ordinary helper files that should share the same assembly as the entry point; use `#:ref` when you want project-reference-like boundaries.\n\n```csharp\n#:property ExperimentalFileBasedProgramEnableRefDirective=true\n#:ref ..\u002FShared\u002FFormatter.cs\n\nConsole.WriteLine(Formatter.Title(\"hello world\"));\n```\n\nGuidelines:\n\n- The referenced file is compiled as its own virtual project and added as a project reference.\n- If the referenced file is a library without top-level statements, put `#:property OutputType=Library` in that referenced file.\n- Members that must be consumed by the referencing app should be public; internal members are not visible across the assembly boundary.\n- `#:ref` is transitive: a referenced file can contain its own `#:ref` and other `#:` directives.\n- Relative paths are resolved relative to the file containing the directive.\n- Some SDK builds require `#:property ExperimentalFileBasedProgramEnableRefDirective=true`; remove that property if the SDK accepts `#:ref` without it.\n\n#### `#:sdk` — SDK selection\n\nOverride the default SDK (`Microsoft.NET.Sdk`):\n\n```csharp\n#:sdk Microsoft.NET.Sdk.Web\n```\n\n#### `#:include` and `#:exclude` — Multi-file apps\n\nIn .NET SDK 10.0.300 and later, file-based apps can include additional files in the same virtual project. Check the full `dotnet --version` output before using these directives; a 10.0.100 or 10.0.200 SDK is still .NET 10 but does not support them. Use `#:include` for helper source files and supported assets, and `#:exclude` to remove files from an include pattern or default item set.\n\n```csharp\n#!\u002Fusr\u002Fbin\u002Fenv dotnet\n#:include Helpers.cs\n#:include Models\u002F*.cs\n#:exclude Models\u002FGenerated\u002F*.cs\n\nConsole.WriteLine(Formatter.Title(\"hello world\"));\n```\n\nGuidelines:\n\n- Treat the file passed to `dotnet` as the entry point; put top-level statements there.\n- Put declarations such as classes, records, and enums in included `.cs` files.\n- Prefer explicit globs such as `Helpers.cs` or `Models\u002F*.cs` over broad recursive globs.\n- Paths are resolved relative to the file containing the directive.\n- Include directives from non-entry-point C# files are processed too, so a helper file can declare its own `#:package`, `#:property`, `#:sdk`, `#:project`, `#:ref`, `#:include`, or `#:exclude` directives.\n- Avoid duplicate directives across included files unless the directive kind explicitly supports duplicates; duplicate `#:package`, `#:property`, `#:sdk`, `#:include`, and `#:exclude` entries can fail.\n- When an app uses `#:include`, add a shebang (`#!\u002Fusr\u002Fbin\u002Fenv dotnet`) to the entry-point file on Unix-like systems to make the entry point clear to tools. Use `LF` line endings and no BOM for shebang files.\n\nExample layout:\n\n```text\nscratch\u002F\n    hello.cs\n    Helpers.cs\n    Models\u002F\n        Person.cs\n```\n\n```csharp\n#!\u002Fusr\u002Fbin\u002Fenv dotnet\n\u002F\u002F hello.cs\n#:include Helpers.cs\n#:include Models\u002F*.cs\n\nvar person = new Person(\"Ada\");\nConsole.WriteLine(Formatter.Title(person.Name));\n```\n\n```csharp\n\u002F\u002F Helpers.cs\nstatic class Formatter\n{\n    public static string Title(string value) => value.ToUpperInvariant();\n}\n```\n\n```csharp\n\u002F\u002F Models\u002FPerson.cs\nrecord Person(string Name);\n```\n\n### Step 5: Clean up\n\nRemove the app files when the user is done. To clear cached build artifacts:\n\n```bash\ndotnet clean hello.cs\n```\n\n## Unix shebang support\n\nOn Unix platforms, make a `.cs` file directly executable:\n\n1. Add a shebang as the first line of the file:\n\n    ```csharp\n    #!\u002Fusr\u002Fbin\u002Fenv dotnet\n    Console.WriteLine(\"I'm executable!\");\n    ```\n\n2. Set execute permissions:\n\n    ```bash\n    chmod +x hello.cs\n    ```\n\n3. Run directly:\n\n    ```bash\n    .\u002Fhello.cs\n    ```\n\nUse `LF` line endings (not `CRLF`) when adding a shebang. This directive is ignored on Windows.\n\n## Source-generated JSON\n\nFile-based apps enable native AOT by default. Reflection-based APIs like `JsonSerializer.Serialize\u003CT>(value)` fail at runtime under AOT. Use source-generated serialization instead:\n\n```csharp\nusing System.Text.Json;\nusing System.Text.Json.Serialization;\n\nvar person = new Person(\"Alice\", 30);\nvar json = JsonSerializer.Serialize(person, AppJsonContext.Default.Person);\nConsole.WriteLine(json);\n\nvar deserialized = JsonSerializer.Deserialize(json, AppJsonContext.Default.Person);\nConsole.WriteLine($\"Name: {deserialized!.Name}, Age: {deserialized.Age}\");\n\nrecord Person(string Name, int Age);\n\n[JsonSerializable(typeof(Person))]\npartial class AppJsonContext : JsonSerializerContext;\n```\n\n## Converting to a project\n\nWhen a file-based app outgrows this workflow, convert it to a full project:\n\n```bash\ndotnet project convert hello.cs\n```\n\n## Fallback for .NET 9 and earlier\n\nIf the .NET SDK version is below 10, file-based apps are not available. Use a temporary console project instead:\n\n```bash\nmkdir -p \u002Ftmp\u002Fcsharp-file-based-app && cd \u002Ftmp\u002Fcsharp-file-based-app\ndotnet new console -o . --force\n```\n\nReplace the generated `Program.cs` with the app content and run with `dotnet run`. Add NuGet packages with `dotnet add package \u003Cname>`. Remove the directory when done.\n\n## Validation\n\n- [ ] `dotnet --version` reports 10.0 or later (or fallback path is used)\n- [ ] If the app uses `#:include`, `#:exclude`, or transitive directives from included files, `dotnet --version` reports SDK 10.0.300 or later\n- [ ] The app compiles without errors (can be checked explicitly with `dotnet build \u003Cfile>.cs`)\n- [ ] `dotnet \u003Cfile>.cs` produces the expected output\n- [ ] Multi-file apps include every required helper file and exclude unintended matches\n- [ ] App files and cached artifacts are cleaned up after the session\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| `.cs` file is inside a directory with a `.csproj` | Move the app outside the project directory, or use `dotnet run --file file.cs` |\n| `#:package` without a version | Specify a version: `#:package PackageName@1.2.3` or `@*` for latest |\n| `#:property` with wrong syntax | Use `PropertyName=Value` with no spaces around `=` and no quotes: `#:property AllowUnsafeBlocks=true` |\n| Directives placed after C# code | All `#:` directives must appear immediately after an optional shebang line (if present) and before any `using` directives or other C# statements |\n| Helper file is not compiled | Add `#:include Helper.cs` or an appropriate glob to the entry-point file |\n| Shared file needs an assembly boundary | Use `#:ref Shared.cs` instead of `#:include Shared.cs`, and set `#:property OutputType=Library` in the referenced file if it has no entry point |\n| Broad include pulls in unrelated files | Prefer narrow include patterns and use `#:exclude` for generated, backup, or experimental files |\n| Duplicate directives in included files | Keep package, property, SDK, include, and exclude directives unique across the entry point and included C# files |\n| Reflection-based JSON serialization fails | Use source-generated JSON with `JsonSerializerContext` (see [Source-generated JSON](#source-generated-json)) |\n| Unexpected build behavior or version errors | File-based apps inherit `global.json`, `Directory.Build.props`, `Directory.Build.targets`, and `nuget.config` from parent directories. Move the app to an isolated directory if the inherited settings conflict |\n\n## More info\n\nSee https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fsdk\u002Ffile-based-apps for a full reference on file-based apps.\n",{"name":5,"license":15,"description":7},"main","30954af1dcd1a74b63f05deb2e2c41e5ecae4a82","02-CSharp-WPF-Desktop-Development\u002Fcsharp-scripts","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack","https:\u002F\u002Fgithub.com\u002Fitsmejay18","2026-09-18 16:06:36",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill csharp-scripts",{"tool":36,"command":37},"bunx","bunx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill csharp-scripts",{"tool":39,"command":40},"pnpm","pnpm dlx skills add itsmejay18\u002FAI-Skills-for-My-Development-Stack --skill csharp-scripts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F02-CSharp-WPF-Desktop-Development\u002Fcsharp-scripts\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7D2RKBHPZ3E1RNN5DWHT550","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 Vector\u003CT>, 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\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fvectorization\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D2RDJ7RN3QK8GJR0QTER1D","resolve-project-references","Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fresolve-project-references\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D2R1H2GTNZYHG9YRX3JDQW","optimizing-ef-core-queries","Optimize and improve the performance of slow Entity Framework Core (EF Core) queries: make them generate less SQL, make fewer database round-trips, and return results faster. Use whenever an EF Core or DbContext query or data-access path is slow or should be made faster — whether or not EF Core owns the database schema. For EF Core, not Dapper or raw ADO.NET.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Foptimizing-ef-core-queries\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7D2QREG04W1YT0NEBHEW5C9","microbenchmarking","Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks. Also activate when microbenchmarking .NET code would be useful and BenchmarkDotNet is the likely tool. Consider activating when answering a .NET performance question requires measurement and BenchmarkDotNet may be needed. Covers microbenchmark design, BDN configuration and project setup, how to run BDN microbenchmarks efficiently and effectively, and using BDN for side-by-side performance comparisons. Do NOT use for profiling\u002Ftracing .NET code (dotnet-trace, PerfView), production telemetry, or load\u002Fstress testing (Crank, k6).","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fmicrobenchmarking\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D2QGE175XWPZVACVH2868Z","incremental-build","Guide for optimizing MSBuild incremental builds. USE FOR: builds slower than expected on subsequent runs, 'nothing changed but it rebuilds anyway', diagnosing why targets re-execute unnecessarily, fixing broken no-op builds. Covers 8 common causes: missing Inputs\u002FOutputs on custom targets, volatile properties in output paths (timestamps\u002FGUIDs), file writes outside tracked Outputs, missing FileWrites registration, glob changes, Visual Studio Fast Up-to-Date Check (FUTDC) issues. Key diagnostic: look for 'Building target completely' vs 'Skipping target' in binlog. DO NOT USE FOR: first-time build slowness (use build-perf-baseline), parallelism issues (use build-parallelism), evaluation-phase slowness (use eval-performance), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Fincremental-build\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D2Q1DQTC6K49R73WQTTPSB","eval-performance","Guide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I\u002FO ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with \u002Fpp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002Fitsmejay18\u002FAI-Skills-for-My-Development-Stack\u002Fblob\u002Fmain\u002F20-Performance-Optimization\u002Feval-performance\u002FSKILL.md",[],[]]