testing
测试规范与最佳实践。Use when writing unit tests, integration tests, or component tests. Triggers on: creating test files, using Vitest, Testing Library, mocking, test organization questions.
Discover blockchain testing skills, compare source repositories and read the instructions for each workflow.
测试规范与最佳实践。Use when writing unit tests, integration tests, or component tests. Triggers on: creating test files, using Vitest, Testing Library, mocking, test organization questions.
Analyze Go test files (*_test.go) for quality issues, anti-patterns, and code smells. This is a Go-specific tool that checks for external dependencies, complexity, flaky patterns, and testing anti-patterns. Use...
This skill should be used when the user asks about "Go test conventions", "ADR-008", "test naming", "table-driven tests", "go testing patterns", "testify", "how to write go tests", or needs guidance on Go testi...
Testing strategy and test pyramid for EFT-Tracker. Guides when to write unit, integration, E2E, or smoke tests. Includes MSW patterns, Playwright best practices, and contract testing. Activates when user mentio...
Writes tests using Vitest and Testing Library. Use when creating unit tests, API tests, component tests, or mocking Firebase/external services. Includes test patterns, assertions, and coverage targets.
Navegação e teste conversacional de aplicações web usando Chrome DevTools. Permite testar sites através de comandos naturais em português, com suporte a contexto do Neo4j e integração automática com hooks de va...
Playwright E2E testing patterns with chrome-devtools MCP integration. Reference for integration tests, A11y validation, and visual regression.
Vitest + Storybook testing strategy with clear role separation. Reference for implementing unit tests and UI interaction tests.
Test-driven development. Use when asked to use TDD explicitly, or any other times when asked write a failing test before implementation, or similar.
Guide for using Assert class (webmozart/assert) for data validation and type enforcement. Use when adding validation to value objects or domain methods.
Guide for writing integration tests for API endpoints. Use when creating endpoint tests, testing validation, or asserting JSON responses.
Guide for writing frontend tests including unit tests with Vitest, component tests, and visual/E2E tests with Playwright MCP. Use when creating tests for hooks, components, or pages.
テストやリンターを実行してプロジェクトの状態を検証します。コード変更後や、動作確認を求められた際に使用します。
仕様書に基づき、テスト駆動開発(TDD)を用いて機能を実装します。
This skill should be used when the user asks about "tests", "unit tests", "EditMode tests", "PlayMode tests", "Test Runner", "test coverage", "NUnit", "Assert", "test fixtures", "writing tests", "running tests"...
Visual E2E testing workflow for frontend UI changes. Use after modifying Svelte components, layouts, or styles to verify the UI renders correctly.
Write comprehensive unit tests for Visual Layout Builder using Vitest. Use when creating tests for lib/ functions, schema validation, canvas utilities, or any business logic. Follows AAA pattern and project tes...
从需求文档(文字、图片、PDF、DOCX)生成结构化的功能测试用例。遵循 15 字段规范,输出 Excel 文件,支持正向/异常场景、边界值、安全性测试。
Testing patterns, strategies, and best practices for comprehensive test coverage.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Diagnose and fix CI/CD failures related to Lint errors and test failures. Use when: (1) User mentions CI/CD failures, lint errors, or test failures, (2) User asks to fix code quality issues or make tests pass,...
Guide for implementing features using Test-Driven Development (TDD) methodology. Use when: (1) User requests to implement a feature using TDD, (2) User asks to write tests first before implementation, (3) User...
Generate tests following project conventions. Use when writing unit tests, integration tests, creating test fixtures, or implementing test builders. Triggers on requests like "write tests for", "add test covera...
Write E2E tests using Playwright with Cucumber/Gherkin for this project. Use when creating tests, writing test cases, testing UI flows, API testing, or when user mentions e2e, playwright, cucumber, gherkin, bdd...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.