SolTechnology.Core

Review a SolTechnology.Core change against the Tale Code philosophy, ClaudeCodingGuide rules, and module conventions.

Imagine the change has shipped exactly as planned and broken production; write concrete failure stories, then sweep SolTechnology.Core module checklists for what the stories missed. Produces a Go / Go-with-mitigations / No-Go verdict. Runs as the 00 gate of a plan, always in a session that did not author the plan.

Evaluate a SolTechnology.Core design choice from supportive and skeptical perspectives. Records alternatives in the dated feature brief and informs current architecture after delivery.

Author a use case in any app built on the `SolTechnology.Core.CQRS` / `SolTechnology.Core.Tale` NuGet packages — a command, a query, a fire-and-forget event, or a Tale (chapters). Covers simple handlers, Tales hosted in `Commands`/`Queries`, domain-model Tales in `DomainServices`, and long-running interactive Tales in `Workflows`. Use whenever adding a new command/query/event, promoting a handler past the §3 size budget into a Tale, adding a chapter, publishing or handling an `IEvent`, wiring a handler into a `ModuleInstaller`, or adding `[LogScope]` logging. Encodes the layout and rules from `ClaudeCodingGuide.md` §0/§3/§4/§11 and the DreamTravel reference app. Routes tests to `test-writing`, review to `code-review`, behaviour-preserving cleanup to `refactor`.

Produce a Conventional Commits message for SolTechnology.Core, using module names as scopes and surfacing semver impact in the footer.

Resolve a NU1901–NU1904 CVE warning, an NU1605 downgrade, or a transitive vulnerability in SolTechnology.Core. Drives the parent-lookup → fix-at-source → override-only-as-last-resort flow from CLAUDE.md §6. Companion to `package-management` (which only handles "add a package").

Validate and fix documentation integrity in SolTechnology.Core — current architecture, dated feature records, module/doc parity, indexes, tables, Mermaid diagrams, links, and numbered lists.

Execute one temporary implementation step from a dated feature plan. Enforces review and premortem gates, updates feature and step statuses, records deviations, and closes delivery by synchronizing current architecture before collapsing the working folder.

Look up canonical NuGet package versions used in this repo before adding a PackageReference. Use when adding a new package to any .csproj, creating a new project, or checking which version of Microsoft.Extensions, Polly, FluentValidation, NUnit, FluentAssertions, NSubstitute, AutoFixture, Azure SDK, or other shared packages to use. Avoids drift and version-by-memory hallucination.

Plan and execute a behaviour-preserving refactor inside `src/SolTechnology.Core.*` or a sample app. Use when renaming inside one module, splitting a class above the size budget, extracting a primary constructor, removing a `#region`, replacing a Newtonsoft usage with `System.Text.Json`, or paying down any `ClaudeCodingGuide §15` anti-pattern. Routes to `implementation-planning` when scope grows past a single module or touches a public symbol.

Author or extend tests for a SolTechnology.Core module or sample app. Use when implementing behaviour that needs coverage, fixing a `Result.Failure` path without a negative test, or adding a regression test for a bug. Picks the right test project, framework (NUnit for all projects), assertion library, mocking style, and file layout. Never invents a new test project.

Interview the user one question at a time before planning or coding. Use when the request is vague, before invoking the implementation-planning agent, or when the user says "roast me" / "stress-test this". Maintains a running ledger of resolved / open / asking branches across turns.