VPDPersonal

Build the Roslyn analyzer submodule and deploy the resulting DLL into the Unity package

Build Roslyn source generators and deploy the resulting DLL into the Unity package

Verify and update Aspid.FastTools README files against the actual codebase — namespaces, public API, CreateAssetMenu paths — keeping EN/RU and root/Documentation copies in sync

Add an xUnit snapshot-style test for ChildStateGenerator or ControllersGroupGenerator output. Use when adding a new emit branch, fixing generated code, or verifying that an attribute combination produces the expected partial class. Tests live in Aspid.Core.HSM.Generators.Tests/ and use Microsoft.CodeAnalysis.CSharp.SourceGenerators.Testing.XUnit (already referenced).

Rebuild the Roslyn source generator. The compiled DLL is automatically delivered into the Unity package via Directory.Build.targets (CopyGeneratorToUnityPackage). Use when generator code under Aspid.Core.HSM.Generators/ has changed and Unity needs the updated DLL.

Conventions for writing XML documentation comments (`///`) in the Aspid.MVVM C# framework — `<summary>`, `<param>`, `<typeparam>`, `<returns>`, `<remarks>`, `<exception>`, `<inheritdoc/>`, hook methods, binder `<example>` includes, and class hierarchy-style summaries. Use this skill whenever writing, editing, or reviewing XML doc comments on classes, interfaces, methods, properties, events, binders, or attributes anywhere in the Aspid.MVVM repo, or when the user asks how to document something in this project, to add XML docs to a file, to write a summary for a binder, to format a `<param>` or `<returns>` block, or to fix inconsistent/missing documentation. Also triggers on phrases like "document this", "add XML docs", "write a summary for", "fix the docs on", "document the binder", or when editing `.cs` files that already contain `///` blocks.