القائمة
Use when writing or configuring Vitest unit tests in TypeScript or TSX files. Covers mocking patterns, setup files, snapshots, coverage, and DOM testing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when committing to the repository, writing commit messages, naming branches, structuring commits, or managing git history.
Use when changing GitHub configuration, setting up branch protection rules, configuring CODEOWNERS, pull request templates, or GitHub repository settings.
Use when creating a new package, changing workspace configuration, setting up shared tooling, or making decisions about monorepo structure and package boundaries.
Use when configuring GitHub Actions workflows, writing CI/CD pipelines, setting up composite actions, or managing workflow secrets and environment variables.
Use when writing Angular TypeScript or HTML template files. Covers modern Angular patterns: standalone components, signals, inject(), control flow syntax, and lazy loading.
Use when writing front-end components that require ARIA attributes, accessible custom widgets, screen reader support, or dynamic content announcements.
| name | testing-vitest |
| description | Use when writing or configuring Vitest unit tests in TypeScript or TSX files. Covers mocking patterns, setup files, snapshots, coverage, and DOM testing. |
vi.fn() for function mocks, vi.spyOn() to monitor existing functions, vi.stubGlobal() for global mocksvi.mock() factory functions at the top level — the factory runs before imports are processedmockImplementation() or mockReturnValue() for dynamic control during testsvitest.config.tstoMatchInlineSnapshot()) for readable assertions visible in code reviewvitest.config.ts only when asked; focus on meaningful tests over percentagesvitest --watch during development for instant feedback; use -t to filter specific testsvitest --ui to navigate large test suites visually during developmentenvironment: 'jsdom' for frontend component tests; combine with testing-library for user interaction simulationdescribe blocks; follow Arrange-Act-Assert patternexpectTypeOf() for type-level assertions; ensure mocks preserve original type signatures