web-testing
MRCalderon3D/everything-game-dev-code/skills/web/web-testing/SKILL.md
Test browser games with fast unit tests for pure logic, headless smoke tests, and a deliberate browser matrix.
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
MRCalderon3D/everything-game-dev-code/skills/web/web-testing/SKILL.md
Test browser games with fast unit tests for pure logic, headless smoke tests, and a deliberate browser matrix.
TangleML/tangle-ui/.claude/skills/e2e-testing/SKILL.md
Playwright E2E testing best practices for this project. Use when writing, modifying, or reviewing E2E tests.
Often used witheverything-claude-codeeverything-claude-code-conventionsbun-runtime
rommapp/argosy-launcher/.claude/skills/ui-ux-testing/SKILL.md
Drive the running app on an Android emulator and visually verify UI/UX by capturing screenshots and reading them back. Use to confirm a screen renders, navigate a flow (e.g. first-run/quickstart), check dual-modality input, or catch visual regressions. Knows the technical limits of emulator testing and when the device is still the final authority.
github/awesome-copilot/skills/webapp-testing/SKILL.md
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
196 projects use a version of this
Often used withacademy-guideskill-shareintelligent-routing
mturac/everything-openai-codex/.agents/skills/e2e-testing/SKILL.md
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
Often used witheverything-claude-codeeverything-claude-code-conventionsbun-runtime
karmab/kcli/skills/kcli-testing/SKILL.md
Guides testing and code quality for kcli. Use when writing tests, running linting, or validating changes before committing.
petrkindlmann/qa-skills/skills/payment-testing/SKILL.md
Test payment and checkout flows end to end against PSP sandboxes — Stripe first, with the general pattern for Adyen/Braintree/PayPal. Covers Stripe test-mode card numbers and their decline codes, the 3DS/SCA challenge flow and its nested-iframe handling in Playwright, test clocks for subscription/billing-cycle simulation, webhook testing (stripe listen/trigger, signature verification, idempotency), failed/retried payments and refunds, and never using real cards. Use when: "test Stripe checkout," "payment test," "3DS test," "test webhook signature," "test subscription renewal," "test clock," "refund test," "decline card test," "checkout E2E." Not for: General API contract testing of non-payment endpoints — api-testing. PCI-DSS/regulatory compliance audit — compliance-testing. Related: api-testing, playwright-automation, compliance-testing, test-data-management, qa-project-context.
UI5/openui5/.claude/skills/run-test/SKILL.md
Run QUnit and OPA tests for OpenUI5 modules via headless Chrome. This is the ONLY way to run tests — never use karma, npm test, or browser MCP tools. Use whenever tests need execution: run tests, run unit tests, check tests pass, verify my change, do the tests still pass, run QUnit, run OPA, execute test suite, test this module, test Button/Router/Table/Dialog/MessageBox/Input/Control, run journey, check regressions. Even if the user does not say "test" explicitly but wants to verify a code change works, use this skill.
4 projects use a version of this
brainbytes-dev/everything-claude-marketing/skills/analytics/ab-testing/SKILL.md
Design, execute, and analyze A/B tests across marketing channels. Use when running experiments on landing pages, emails, ads, or features.
Often used withfree-toolsmarketing-councilemails
nasa/fprime/.github/skills/fprime-component-integration-test/SKILL.md
Integration testing phase of F Prime component development. Guides the agent through writing reusable pytest-based integration tests in the component's test/int/ folder using the GDS Integration Test API. These tests ship with the component and can be run against any deployment that includes it. Trigger when unit tests pass and the component is ready for integration testing. Keywords: F Prime, integration test, pytest, GDS, fprime_test_api, reusable test, component test.
No other project uses it yet
hyhmrright/brooks-lint/skills/brooks-test/SKILL.md
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.
No other project uses it yet
ComposioHQ/composio/.agents/skills/python-testing/SKILL.md
Select and run Python SDK verification with nox, Makefile targets, Ruff, mypy, pytest markers, sanity tests, type inference checks, and build checks. Use when adding Python tests, diagnosing Python CI, or validating Python SDK/provider changes. Do not use for TypeScript-only checks.
Steady6 mentions in 2 weeks
53 projects use a version of this
Often used withdjango-verificationpython-patternsproject-guidelines-example
NVIDIA/skills/skills/mcore-testing/SKILL.md
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
Fractera/web4-node-starter-kit/.claude/skills/use-testing/SKILL.md
Build process. How work is PROVEN here — before you say «done», «it works», «ready to check». Load it when you are about to report a result, when a gate goes green and you feel finished, when something must be verified on the node, and when the owner asks for proof («show me the proof», «докажи»). The rule that changes behaviour: two proofs from DIFFERENT planes, one of them with a negative control, and a build log is never one of them — it reads the same whether the capability works or not.
samber/cc-skills-golang/skills/golang-testing/SKILL.md
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber/cc-skills-golang@golang-benchmark`.
45 projects use a version of this
Often used withgolang-error-handlinggolang-how-togolang-security
astDeniss/business-skills/ab-testing/SKILL.md
Designs, sizes, and analyzes A/B tests end-to-end: hypothesis writing, primary metric and MDE selection, sample size and runtime math, guardrail metrics, and ship/kill decisions. Use when the user says \"design an A/B test\", \"what sample size do I need\", \"how long should my test run\", \"is this result statistically significant\", \"write a test hypothesis\", \"my experiment is flat, what now\", \"should we ship this variant\", \"my test results look weird\", or asks about split testing, experiment analysis, peeking, or rollout decisions.
Often used withfree-toolsmarketing-councilemails
scayver/marketing-skills/skills/ab-testing/SKILL.md
Use this skill when planning, designing, or analyzing A/B tests and growth experiments. Trigger phrases: "run an A/B test," "design an experiment," "write a hypothesis," "calculate sample size," "build an experimentation backlog," "ICE scoring," "statistical significance," "multivariate test," "growth experimentation," "test velocity."
Often used withfree-toolsmarketing-councilemails
YepAPI/skills/skills/ab-testing/SKILL.md
Experiment setup, variant splitting, statistical significance, and feature flag integration.
Often used withfree-toolsmarketing-councilemails
awslabs/awsome-distributed-ai/architectures/sagemaker-hyperpod-eks/slinky-slurm/.opencode/skills/bash-testing/SKILL.md
Patterns for unit testing bash scripts using bats-core, including AWS CLI mocking, jq/sed/awk testing, and cross-platform portability
ansible/vscode-ansible/.cursor/skills/wdio-testing/SKILL.md
Write, run, and debug WebDriverIO (WDIO) UI tests for the Ansible VS Code extension. Use when creating new WDIO specs, fixing test failures, adding webview or Lightspeed tests, or troubleshooting headless/CI execution.
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 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.
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.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.