Testing
Unit tests, integration tests, test automation
bad-reference
by jankneumann
Cites a reference file that does not exist
teaching-with-repo-token
by jankneumann
Fixture where teaching prose cites a repo-specific path
good-skill
by jankneumann
A well-formed skill used as a positive fixture for content invariants
gen-eval
by jankneumann
Run generator-evaluator testing against live services
gen-eval-scenario
by jankneumann
Create gen-eval scenario YAML files interactively
nested-references
by jankneumann
Fixture citing a reference two levels deep
all-shaped
by jankneumann
Fixture whose every section is decidable by the pre-pass
mixed
by jankneumann
Fixture with four prose sections the pre-pass cannot decide
missing-tail-block
by jankneumann
User-invocable skill that omits the tail block
browser-testing-with-devtools
by jankneumann
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. This is an infrastructure skill loaded by other testing/debugging skills; it is not directly user-invocable. Trigger phrases (when called by another skill): "verify in the browser", "capture console errors", "screenshot the page", "profile Core Web Vitals", "inspect the DOM".
oversized
by jankneumann
Fixture with more than 500 lines
no-tail-block
by jankneumann
User-invocable fixture without the tail block
behavior-driven-testing
by agent-next
Systematic testing methodology for exhaustive branch coverage, edge case identification, and production bug prevention. Use when PR review reveals incomplete test coverage, when tests pass but users report bugs, when code changes break existing features, when verifying all branches and edge cases before merge, when analyzing "it works on my machine" issues, when planning test strategy for new features, or when debugging flaky tests and race conditions.
elite-tester
by truongnat
World-class testing standards focused on the Testing Pyramid, TDD, E2E excellence, and robust test data management. Use when writing unit tests, integration tests, or complex E2E automation for any platform.
go-test-standards
by iceleaf916
Golang 单元测试规范与最佳实践指南
testing-patterns
by vivekgana
pytest fixtures and integration testing patterns for Spark applications, including DataFrame assertions and mock data generation.
playwright-browser
by arlenagreer
Browser automation and E2E testing via local Playwright Docker container
ab-test-setup
by ncdevshiv
"Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness."
test-driven-development
by jankneumann
Drives development with tests — write a failing test before the code that makes it pass. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives ("the Prove-It Pattern"), or when you're about to modify existing functionality. Trigger phrases: "write a test first", "TDD", "red green refactor", "reproduce the bug with a test", "Prove-It Pattern".
bad-related
by jankneumann
Declares a related skill that does not exist
frontend-testing
by langgenius
Use when writing or changing Vitest or React Testing Library tests under web/ or packages/dify-ui/, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy. Do not use for frontend code-review-only requests, general testability discussion, Python tests, or Cucumber/Playwright E2E.
nestjs-expert
by Jeffallan
Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating TypeORM or Prisma, or working with .module.ts, .controller.ts, and .service.ts files. Invoke for guards, interceptors, pipes, validation, Swagger documentation, and unit/E2E testing in NestJS projects.
adversarial-ux-test
by NousResearch
Roleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.
dogfood
by NousResearch
"Exploratory QA of web apps: find bugs, evidence, reports."