菜单
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.
用 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 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 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.
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 | fluent-validation-inline-messages |
| description | 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. |
WithErrorCode(ApiValidationErrorCodes.*) followed by WithMessage(ApiValidationErrorCodes.*).WithErrorCode(...) call — do not replace, just delete the line..WithMessage(ApiValidationErrorCodes.*) with a plain English string describing the rule.using Unified.Common.Validation; import if ApiValidationErrorCodes is no longer referenced..When(...) clauses and all other validation logic unchanged.| Rule | Message pattern |
|---|---|
NotEmpty / NotNull | "{PropertyName} is required." |
MaximumLength(n) | "{PropertyName} must not exceed {n} characters." |
Must(...) date format | "{PropertyName} must be in yyyy-MM-dd format." |
Must(...) cross-field | Describe the business rule, e.g. "ExpiryDate must be on or after EffectiveDate." |
Before:
using Unified.Common.Validation;
RuleFor(x => x.PositionTypeCode)
.NotEmpty()
.WithErrorCode(ApiValidationErrorCodes.Required)
.WithMessage(ApiValidationErrorCodes.Required)
.MaximumLength(50)
.WithErrorCode(ApiValidationErrorCodes.TooLong)
.WithMessage(ApiValidationErrorCodes.TooLong);
After:
RuleFor(x => x.PositionTypeCode)
.NotEmpty()
.WithMessage("PositionTypeCode is required.")
.MaximumLength(50)
.WithMessage("PositionTypeCode must not exceed 50 characters.");
WithErrorCode(...) lines removedWithMessage(ApiValidationErrorCodes.*) replaced with descriptive stringsusing Unified.Common.Validation; removed (if unused).When, .Must, rule ordering)