メニュー
Guardrails for Vitest changes in opal-frontend-common-ui-lib. Use when editing Vitest config, Angular test setup, or VS Code Vitest Explorer support so the extension path works without regressing the normal Angular CLI Vitest flow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Automated review rules for opal-frontend-common-ui-lib PRs. Use when asked to review code, run @codex review, or provide PR feedback; apply severity levels and the required comment format.
Repository structure, build/test commands, coding style, and contribution rules for opal-frontend-common-ui-lib. Use when navigating the repo, running or debugging builds/lint/tests, or following style conventions.
| name | opal-vitest-guard |
| description | Guardrails for Vitest changes in opal-frontend-common-ui-lib. Use when editing Vitest config, Angular test setup, or VS Code Vitest Explorer support so the extension path works without regressing the normal Angular CLI Vitest flow. |
Use this skill when changing vitest*.ts, Angular test setup files, or .vscode Vitest settings in this repository.
vitest.explorer support isolated from the normal Angular CLI Vitest runner.vitest.vscode.config.ts for editor-only behavior.vitest.config.ts aligned with the Angular CLI runner and free of raw-Vitest-only workarounds.projects/opal-frontend-common/test-setup.ts lean.projects/opal-frontend-common/test-setup.vscode.ts or the VS Code config path, not in the main setup.BrowserTestingModule and platformBrowserTesting.@angular/platform-browser-dynamic/testing.node_modules tests are not collected accidentally.projects/opal-frontend-common/**/*.spec.ts and projects/opal-frontend-common/**/*.test.ts.@hmcts/opal-frontend-common/... need to work under raw Vitest, resolve them to source entry points rather than relying on stale built output.templateUrl and styleUrl or styleUrls.node_modules test trees.