Proves

Proves unitàries, d’integració i automatitzades

Skills: 25–48 de 6650
jankneumann

bad-reference

jankneumann

Cites a reference file that does not exist

Proves 4 fa 5 mesos
jankneumann

teaching-with-repo-token

jankneumann

Fixture where teaching prose cites a repo-specific path

Proves 4 fa 1 mes
jankneumann

good-skill

jankneumann

A well-formed skill used as a positive fixture for content invariants

Proves 4 fa 5 mesos
jankneumann

gen-eval

jankneumann

Run generator-evaluator testing against live services

Proves 4 fa 4 mesos
jankneumann

gen-eval-scenario

jankneumann

Create gen-eval scenario YAML files interactively

Proves 4 fa 4 mesos
jankneumann

nested-references

jankneumann

Fixture citing a reference two levels deep

Proves 4 fa 1 mes
jankneumann

all-shaped

jankneumann

Fixture whose every section is decidable by the pre-pass

Proves 4 fa 1 mes
jankneumann

mixed

jankneumann

Fixture with four prose sections the pre-pass cannot decide

Proves 4 fa 1 mes
jankneumann

missing-tail-block

jankneumann

User-invocable skill that omits the tail block

Proves 4 fa 5 mesos
jankneumann

browser-testing-with-devtools

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".

Proves 4 fa 5 mesos
jankneumann

oversized

jankneumann

Fixture with more than 500 lines

Proves 4 fa 1 mes
jankneumann

no-tail-block

jankneumann

User-invocable fixture without the tail block

Proves 4 fa 1 mes
agent-next

behavior-driven-testing

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.

Proves 11 fa 8 mesos
truongnat

elite-tester

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.

Proves 7 fa 8 mesos
iceleaf916

go-test-standards

iceleaf916

Golang 单元测试规范与最佳实践指南

Proves 5 fa 9 mesos
vivekgana

testing-patterns

vivekgana

pytest fixtures and integration testing patterns for Spark applications, including DataFrame assertions and mock data generation.

Proves 4 fa 9 mesos
arlenagreer

playwright-browser

arlenagreer

Browser automation and E2E testing via local Playwright Docker container

Proves 4 fa 11 mesos
ncdevshiv

ab-test-setup

ncdevshiv

"Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness."

Proves 1 fa 8 mesos
jankneumann

test-driven-development

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".

Proves 4 fa 5 mesos
jankneumann

bad-related

jankneumann

Declares a related skill that does not exist

Proves 4 fa 5 mesos
langgenius

frontend-testing

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.

Proves 159,4 k fa 2 mesos
Jeffallan

nestjs-expert

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.

Desenvolupament d’API 12 k fa 5 mesos
NousResearch

adversarial-ux-test

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.

Disseny 256,7 k fa 5 mesos
NousResearch

dogfood

NousResearch

"Exploratory QA of web apps: find bugs, evidence, reports."

Proves 256,7 k fa 5 mesos