storybook-guidelines
Comprehensive Storybook story creation guidelines. Covers story structure, naming conventions, and visual testing patterns. Reference this skill when creating Storybook stories for components with conditional r...
发现 testing security testing 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Comprehensive Storybook story creation guidelines. Covers story structure, naming conventions, and visual testing patterns. Reference this skill when creating Storybook stories for components with conditional r...
Comprehensive testing guidelines for Vitest and React Testing Library. Covers quality standards, AAA pattern, naming conventions, branch coverage, and best practices. Reference this skill when creating or updat...
PolicyEngine testing patterns - YAML test structure, naming conventions, period handling, and quality standards
Testing patterns for PolicyEngine data generation pipelines (policyengine-us-data, policyengine-uk-data)
Playwright 기반 브라우저 자동화 및 E2E 테스트 스킬. 스크린샷, 웹 스크래핑, 폼 자동화 지원. "브라우저", "스크린샷", "E2E 테스트", "웹 스크래핑" 요청 시 활성화됩니다.
Testing capabilities including running pytest, listing tests, and generating coverage reports.
Go repository testing with SQLC integration following hexagonal architecture. Use when writing integration tests for repository layer, testing database operations, and validating domain model persistence. Focus...
Run behavior tests, run browser tests, execute .test.txt files, run e2e tests with ATR, natural language browser testing, AI browser tests, behavior-driven browser testing, or run browser-based behavior tests u...
Use when testing UI changes, verifying builds work, or validating extension behavior on PoE trade website or Storybook
Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks
Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
Complete guide to testing Ruby on Rails applications with RSpec. Use when: (1) Writing unit tests, integration tests, system tests, (2) Setting up test factories, (3) Creating shared examples, (4) Mocking exter...
Unit, widget, integration, and golden test patterns with mocking strategies
Complete guide to testing Ruby on Rails applications with RSpec. Use this skill when writing unit tests, integration tests, system tests, or when setting up test infrastructure including factories, shared examp...
Expert XCTest decisions for iOS/tvOS: test type selection trade-offs, mock vs stub vs spy judgment calls, async testing pitfalls, and coverage threshold calibration. Use when designing test strategy, debugging...
Production-grade testing strategies for robust, maintainable systems. Covers unit/integration/E2E testing, contract testing, accessibility, mutation testing, and CI/CD patterns. Supports Python (pytest) and Typ...
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement
Use when asked to evaluate PR test coverage or explicitly asked to run the pr-test-analyzer subagent.
Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions
Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks
Comprehensive pytest skill for async Python testing with proper mocking, fixtures, and patterns from production-ready test suites. Use when writing or improving async tests for Python applications, especially F...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。