Use when running tests, fixing failing tests, updating snapshots, syncing corpus data, validating before push, or working with Django matrix testing in django-language-server. Handles cargo, just, nox, insta, corpus, clippy, fmt, and lint commands.
20712d agoReviewMountCreate a free account to mount
Enforce Sentry React Native SDK test conventions for naming, structure, mocking, and fixtures with Jest. Use when writing tests, adding tests, modifying tests, reviewing test code, fixing failing tests, adding coverage, TDD, test-first / red-green, reproducing bugs with tests, regression tests, or test refactoring in `packages/core`.
1.8k2mo agoReviewMountCreate a free account to mount
Usability-test any web page or HTML prototype with AI agents acting as first-time users, then improve it in a measured loop. Tester agents drive the page through a local Playwright harness that shows them only the accessibility tree (or only screenshots, for vision testers); success is verified from page state, never from the tester's claim. Produces a baseline scorecard, stops for approval, then runs design review, fixes and a re-test into a before/after report. Optional extras are a role and task model with a weighted cost score, simulated users from a fast System One model to screen layout hypotheses, and session replays for a visual report. Use when the user says "usability-test this page", "run agent UX tests", "can a new user complete these tasks", "test this prototype with users", "simulate users on this design", or "test this UX hypothesis". For a critique without testing use design-review; for measured visual polish use ui-polish.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Orienta o planejamento, a escrita, a execução e a auditoria de testes automatizados (unitários, integração, contrato e E2E), de forma agnóstica a linguagem: padrão AAA, Test Data Builders, dublês, determinismo, esperas ativas, isolamento de estado e pirâmide de testes. Use sempre que o usuário pedir 'escreva testes', 'testes unitários, de integração ou E2E', 'aumente a cobertura', 'TDD', 'teste instável (flaky)', 'gere os testes a partir dos critérios de aceite' ou 'caracterize este código antes de refatorar', mesmo sem a palavra 'testing'. NÃO use para diagnosticar um bug em produção (isso é sk-debug), para revisar a qualidade de um diff (isso é sk-code-review) nem para configurar ferramentas específicas de uma stack (isso é a sk-tech-* correspondente).
This skill should be used when the user asks to 'write tests', 'add test coverage', 'test a component', 'test an API route', 'test a hook', 'set up Vitest', 'use React Testing Library', 'mock an API', or mentions 'component testing', 'integration tests', 'vitest', 'RTL', 'msw', 'testing library'. Provides JavaScript/TypeScript testing patterns using Vitest and React Testing Library for Next.js applications.
Visual testing of TUI and CLI output using VHS and Freeze. Use when making changes to TUI views, CLI output formatting, theme styling, layout, or any visual component. Must be used after any change to View() functions, lipgloss styles, footer, sidebar, metadata, output pane, wizard overlay, or CLI error formatting.
Activate this skill for unit tests, TDD, Playwright E2E tests, Jest/Vitest setups, test strategy design, or stabilizing flaky test suites. Use when writing reliable tests, mocking boundaries, or setting up automated regression verification.
Use when writing unit tests for a function or module, mocking external dependencies, practising TDD on new business logic, or enforcing a coverage target across a codebase in Python, TypeScript, or Go.
1906mo agoReviewMountCreate a free account to mount
Use when you need to write fast unit tests for Quarkus applications — including pure tests with @ExtendWith(MockitoExtension.class), @QuarkusTest with @InjectMock for full CDI mock replacement, @InjectSpy for partial CDI bean mocking, REST Assured for resource-focused tests, @ParameterizedTest with @CsvSource / @MethodSource, QuarkusTestProfile for test-specific configuration overrides, and naming conventions (*Test → Surefire, *IT → Failsafe). For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Quarkus project; Reduce slow @QuarkusTest usage with Mockito-first tests; Add @InjectSpy partial mocking or QuarkusTestProfile configuration in Quarkus tests; Convert repeated test methods to @ParameterizedTest with @CsvSource or @MethodSource; Write fast pure unit tests for Quarkus services. Part of Plinth Toolkit
4614mo agoReviewMountCreate a free account to mount
Write high-quality BDD pytest tests for the ArduPilot Methodic Configurator. Use when writing new unit tests, creating test fixtures, applying Given-When-Then pattern, testing tkinter frontends, or following the minimal-mocking strategy for backend and business logic.
17320mo agoReviewMountCreate a free account to mount
Set up and run SITL integration tests for backend_flightcontroller.py. Use when testing real MAVLink communication, downloading pre-built SITL binaries from firmware.ardupilot.org, running sitl-marked pytest tests, or debugging connection failures on TCP port 5760.
17320mo agoReviewMountCreate a free account to mount
Generate a standalone console application under artifacts/tmp from a managed test under src/tests so it can be run directly with corerun. USE FOR: "create a standalone repro for this runtime test", converting a CoreCLR test wrapper path such as JIT/.../TestName.cmd into a console app, or extracting a fully qualified xUnit test method from a merged test assembly, including when a CI scenario such as jitstress1 is specified. DO NOT USE FOR: adding a regression test to src/tests, library tests under src/libraries, NativeAOT-only tests, or tests whose behavior fundamentally requires a native, browser, mobile, multi-process, or external-service harness.
18k2y agoReviewMountCreate a free account to mount
Playwright automation, Chrome DevTools debugging, and browser interaction testing. Use for E2E/unit tests, capturing screenshots, inspecting network/console logs, or validating user flows in web applications.
2224d agoReviewMountCreate a free account to mount
Write and run tests for ESPHome components - YAML build tests (test.*.yaml, validate.*.yaml, common.yaml) under tests/components, shared bus packages and CI test grouping, C++ gtest unit tests, and host integration tests including the uart_mock fixture. Use when adding or changing files under tests/, or when a code change needs test coverage.
12k5d agoReviewMountCreate a free account to mount
Verifies tests catch the bug. Auto-detects test type (UI tests, device tests, unit tests) and dispatches to the appropriate runner. Supports two modes - verify failure only (test creation) or full verification (test + fix validation).
23k14d agoReviewMountCreate a free account to mount
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.