purview-dev

Use when designing or refining event-sourced aggregates, commands, events, invariants, source-generator hooks, or snapshot-queryable mirror properties.

Use when defining event-sourced aggregate validation at command time, hook time, save time, or for computed snapshot/query mirror properties.

Use when modeling scalar, complex, or contextual value objects with source-generated normalization, validation, Hydrate/Create semantics, or query-translation awareness.

Create and apply a prerelease bump using Changesets CLI, with the new changeset markdown summarizing the actual changes since the last shipped release.

Use .NET with TUnit-specific test conventions.

Git workflow and conventional commit guidance.

Lefthook Git hook integration.

Run, filter, and select TUnit tests through `dotnet test`. Use this whenever executing .NET tests in a project that depends on TUnit (built on Microsoft.Testing.Platform / MTP, not VSTest), when `dotnet test --filter` reports "Zero tests ran", or when tests must be narrowed by assembly, namespace, class, test name, [Category], or other custom properties. Covers the `--treenode-filter` path-based query syntax, its operators, the `--` separator rules across SDK versions, and common 0-tests troubleshooting.

Use when converting an Aspire AppHost (typically Program.cs/AppHost.cs) into Purview.Aspire.ResourceKit patterns: generate a HostKit, split resources into ResourceKits with BuildResource/ConfigureResource, map existing config into generated options (IsEnabled/Name), replace direct wiring with AddAspireResourceKit, and update tests/fixtures/configuration to use OptionsHelper and ResourceKit semantics.

Use when creating, moving, or splitting projects in a repository that uses Purview.DotNetProjectSdk, especially for src/tests placement, test suffix naming, namespace alignment, and automatic project-reference behavior.

Create and apply a prerelease bump using Changesets CLI, with the new changeset markdown summarizing the actual changes since the last shipped release.

Use when creating or refactoring .NET tests with TUnit conventions (AAA pattern, naming, async assertions, and CancellationToken usage).

Git workflow and conventional commit guidance.

Lefthook Git hook integration.

Use for quick TUnit --treenode-filter patterns.

Run, filter, and select TUnit tests through `dotnet test`. Use this whenever executing .NET tests in a project that depends on TUnit (built on Microsoft.Testing.Platform / MTP, not VSTest), when `dotnet test --filter` reports "Zero tests ran", or when tests must be narrowed by assembly, namespace, class, test name, [Category], or other custom properties. Covers the `--treenode-filter` path-based query syntax, its operators, the `--` separator rules across SDK versions, and common 0-tests troubleshooting.

Creates a pre-release for AspireC4. Use this skill when asked to create a pre-release, publish an early-access version, increment the pre-release counter, or run the pre-release process.

Creates a stable release for AspireC4. Use this skill when asked to create a release, publish a new version, bump to a stable version, or run the release process.

Use when working with `.c4`/`.likec4` files or LikeC4 CLI/config questions where exact DSL/CLI syntax is required, especially for strict command/snippet-first answers, validate/export flags, predicates `*`/`_`/`**`, deployment snippets, dynamic views, or relationship extension matching.