メニュー
Write minimal xUnit tests for .NET/C# changes in the unified-scheduling API. Use when adding tests for endpoints, validators, services, or handlers in api/. Covers test project layout, naming conventions, fixture setup, and run commands.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Apply the unified-scheduling backend logging pattern for .NET API services. Use when adding or changing logging in api/ services, controllers, background startup services, exception handling, or tests that directly instantiate logged services. Covers ILogger constructor injection, Microsoft logging level guidance, structured message templates, sensitive data handling, and validation commands.
Add or update Calendar module functionality using the contribution-based frontend architecture and Calendar-owned backend event model. Use when modifying calendar views, calendar data contributions, create/detail actions, or Calendar Event/EventSeries backend behavior.
Refactor FluentValidation validators to use inline WithMessage strings instead of WithErrorCode + shared error-code constants. Use when asked to remove error codes, inline validation messages, or clean up validators that reference ApiValidationErrorCodes.
Refactor or create Vue 3 form modal components using a formData object, generated Zod schemas, and consistent save/error handling. Use when asked to clean up, refactor, or build a form modal in web/src/.
Add or update permission seed entries using module-owned PermissionSeedConfiguration contributions, then let PermissionSeeder aggregate across modules. Use when introducing a new permission or moving permissions between modules.
Write minimal Vitest + Vue Test Utils tests for the unified-scheduling web frontend. Use when adding tests for Vue components, composables, stores, or utilities in web/src/. Covers test layout, setup helpers, mocking patterns, and run commands.
| name | unit-tests-api |
| description | Write minimal xUnit tests for .NET/C# changes in the unified-scheduling API. Use when adding tests for endpoints, validators, services, or handlers in api/. Covers test project layout, naming conventions, fixture setup, and run commands. |
Applies to files under api/ and tests under api/Unified.Tests/.
api/
Unified.Tests/
Unified.Core/
Controllers/ ← controller-level tests
Services/ ← service/domain tests
Unified.Infrastructure/
Unified.UserManagement/
Unified.Tests.csproj
xunit.runner.json
api/Unified.Tests/ for an existing file that tests the same class or a sibling. Mirror its fixture style, helpers, and using statements exactly.MethodName_StateUnderTest_ExpectedBehavior
// e.g. GetShift_WhenShiftNotFound_ReturnsNotFound
# Run only the Unified.Tests project
dotnet test api/Unified.Tests/Unified.Tests.csproj
# Filter to a single class (xUnit v3 style)
dotnet test api/Unified.Tests/Unified.Tests.csproj -- --filter-class <FullyQualifiedClassName>
xUnit ([Fact], [Theory]) — do not introduce NUnit or MSTest.Moq only when an external boundary (HTTP client, clock) must be isolated.Arrange / Act / Assert comment style if present in nearby tests.