Skills

Inspect, unpack, edit, sign, and repack Ren'Py save files. Use when working with Ren'Py .save archives, save metadata JSON, screenshot/extra_info/log/signatures entries, machine save-token keys, or when a user asks to modify or repair a Ren'Py savegame.

correct modelling of C# datastructures for maintainable code

Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies.

Guides activity tracing with generated ActivitySources, tags, parent activities, exception status handling, and registration. Use when adding or reviewing OpenTelemetry activity tracing in Bendex flows.

Microsoft code analysis CA warning meanings and examples

Routing guide for enabled compiler and analyzer warnings in this Bendex solution

Non-nullability C# compiler warning meanings and examples

.NET IDE code style warning meanings and examples

Modern C# style guidance for Bendex and MicroSea code changes, including primary constructors, expression-bodied members, var usage, target-typed new, lambdas, and pattern matching.

MSBuild warning meanings and examples

NuGet restore warning meanings and examples

How to fix enabled C# nullable reference type compiler warnings (CS8xxx)

Roslynator RCS analyzer warning meanings and examples

Explains LocalExIm LCX and LCXZ translation file formats, compression headers, XML structure, RESX export rules, and language fallback behavior. Use when reading, writing, converting, or validating translation files.

Guides unit test setup, naming, TestOf usage, Arrange/Act/Assert structure, ServiceLocator initialization, and Shouldy assertions. Use when adding, reviewing, or fixing unit tests.

Rules for manually editing WinForms *.Designer.cs files, resources, project nesting, InitializeComponent order, and designer-safe event wiring. Use when changing WinForms designer files or related resx/csproj metadata.

xUnit analyzer warning meanings and examples