Prorise-coolSkillwebapp-testing
Prorise-cool/Claude-Code-Multi-Agent/.claude/skills/webapp-testing/SKILL.md
使用 Playwright 与本地 Web 应用程序交互和测试的工具包。支持验证前端功能、调试 UI 行为、捕获浏览器截图和查看浏览器日志。
Find the best CLAUDE.md, AGENTS.md and Claude skills
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.
Best matches · from page 15Worked for most · soon
Prorise-coolSkill
vasceannieSkillslopgate-test-extender
vasceannie/slopgate/.claude/skills/slopgate-test-extender/SKILL.md
Extend Python test suites with parametrization, fixture reuse, and quality enforcement. Use when asked to add tests, extend existing tests, improve test coverage, consolidate duplicate tests, fix test quality issues, or when Slopgate reports untested-production-code, missing test references, or coverage gaps. Triggers on requests like "add tests for X", "extend these tests", "parametrize tests", "consolidate tests", "fix test quality", "improve test coverage", "write tests for this function", "test this module", "behavior tests", "integration tests", "missing tests", "coverage holes", "untested code", or when a hook denies with test-related findings.
MADTeacherSkillflutter-testing
MADTeacher/mad-agents-skills/flutter-testing/SKILL.md
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins. Use when adding unit tests, widget tests, integration tests, MethodChannel or plugin mocks, Mockito or mocktail test doubles, golden or accessibility checks, CI test commands, test failures, MissingPluginException, pump or pumpAndSettle problems, finder errors, build_runner mock generation, device integration testing, web integration testing, or flaky Flutter tests.
osteelSkilltest-audit
osteel/agent-skills/test-audit/SKILL.md
Audit the existing test suite for structural and quality issues — wrong-layer tests, redundant browser tests, infrastructure overuse, flaky/unreliable patterns, rotted skipped tests, unclear test names, dataset opportunities, duplicate tests, folder drift — then fix the approved issues. Use when the user says things like "audit the tests", "review the test suite", "our tests are slow", "our tests are flaky", "improve test distribution", "too many end-to-end tests", "tests are taking too long", "are our tests in the right layer", or "clean up the test suite". Also invoke proactively after a major feature milestone when the suite has grown significantly. Distinct from `cover` (which adds tests for recent code changes) — this skill audits what's already there and never adds net-new tests for uncovered code. Use the `test` skill to run the suite during the baseline and verification phases.
loulanyueSkillkotlin-testing
loulanyue/awesome-claude-notes/skills/kotlin-testing/SKILL.md
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
loulanyueSkillpython-testing
loulanyue/awesome-claude-notes/skills/python-testing/SKILL.md
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
MindrallySkillpython-testing
Mindrally/skills/python-testing/SKILL.md
Expert in Python testing with pytest and test-driven development
devpilotXSkilltest-strategy
devpilotX/skills/skills/test-strategy/SKILL.md
Decide what deserves a test and write tests that fail for the right reason. Use when the user asks what or how to test, asks about unit, integration or end to end tests, test coverage, mocking, fixtures, flaky tests, test driven development, snapshot tests or contract tests, asks why their tests pass while production breaks, or asks how to add tests to code that has none. Allocates effort by what a failure costs rather than by a coverage target, tests behaviour instead of implementation so refactoring does not break the suite, makes flakiness a defect rather than a retry, and states plainly that coverage percentage measures execution rather than correctness. Triggers on what should I test, how do I test, unit tests, integration tests, end to end tests, test coverage, mocking, flaky tests, TDD, snapshot tests, my tests pass but production breaks, add tests to legacy code.
PIXARTSeuSkilltest-master
PIXARTSeu/Synapse/.agents/skills/test-master/SKILL.md
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.
MicrosoftSkillort-test
microsoft/onnxruntime/.github/skills/ort-test/SKILL.md
Run ONNX Runtime tests. Use this skill when asked to run tests, debug test failures, or find and execute specific test cases in ONNX Runtime.
GitHubSkillspring-boot-testing
github/awesome-copilot/skills/spring-boot-testing/SKILL.md
Expert Spring Boot 4 testing specialist that selects the best Spring Boot testing techniques for your situation with Junit 6 and AssertJ.
devdavvSkilluw-unity-test-runner
devdavv/unity-ai-workflow/.claude/skills/uw-unity-test-runner/SKILL.md
Generates EditMode and PlayMode tests using NUnit, mapped from GDD Gherkin scenarios. Use when writing tests, validating features, ensuring code quality, or verifying behavior after changes. Triggers on requests like "write tests for this", "test the health system", "add unit tests", "verify this works", "add PlayMode tests", "test this feature", "write integration tests", "make sure this doesn't break", "add test coverage", "TDD this feature", or any task involving test creation, test-driven development, or quality assurance. Maps Given/When/Then scenarios directly to test methods using NUnit assertions.
asgard-ai-platformSkillmkt-ab-testing
asgard-ai-platform/skills/mkt-ab-testing/SKILL.md
Design and execute marketing A/B tests for landing pages, email campaigns, ad creatives, and pricing with proper test design and result analysis. Use this skill when the user needs to test marketing variations, improve conversion rates through experimentation, or decide between two campaign approaches — even if they say 'which version performs better', 'test this landing page', 'A/B test our email subject line', or 'should we change our CTA'.
trotsky1997Skillpytest-testing
trotsky1997/My-Claude-Agent-Skills/pytest-testing/SKILL.md
Comprehensive guide for writing and running pytest tests in Python projects. Use when (1) Setting up pytest for a new project, (2) Writing test files and test cases, (3) Using fixtures, mocks, and parametrization, (4) Improving test coverage, (5) Debugging test failures, (6) Organizing test structure, or any Python testing tasks with pytest.
saikumaryerraSkillregression-testing-agent
saikumaryerra/AutoCodeReview/.claude/skills/regression-testing-agent/SKILL.md
Design test strategies, generate test cases, analyze test results, and manage regression testing. Use this skill when the user mentions test plans, test cases, regression testing, test coverage, QA, smoke tests, integration tests, E2E tests, test automation, bug triage, or asks "what should we test", "write test cases for this feature", or "analyze these test results". Also triggers for impact analysis ("what could this change break"), flaky test investigation, test data generation, test strategy design, test automation frameworks, coverage analysis, or any request about ensuring software quality through testing. Even casual questions like "did we test enough" or "what's risky about this release" should activate this skill.
jmrplensSkillgolang-testing
jmrplens/gitlab-mcp-server/.github/skills/golang-testing/SKILL.md
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
MicrosoftSkillsmoke-tests
microsoft/vscode/.github/skills/smoke-tests/SKILL.md
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.
ChrisWilesSkilltesting-patterns
ChrisWiles/claude-code-showcase/.claude/skills/testing-patterns/SKILL.md
Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
lawless-mSkillauto-testing
lawless-m/claude-skills/.claude/skills/auto-testing/SKILL.md
Use when building an automated test → issue → fix loop with Claude Code and GitHub issues — overnight auto-fixing, regression loops, self-healing CI.
bestdeejay-designSkillfrontend-testing
bestdeejay-design/agent-skills/skills/frontend-testing/SKILL.md
Scaffold and advise on frontend testing for production readiness, mapped to the Front-End-Checklist Testing category (13 rules). Defines a testing pyramid (unit, integration, E2E, visual, a11y, cross-browser, real-device, perf-budget, mutation, error-monitoring, coverage, mocking, contract) and emits copy-pasteable configs: Playwright config + smoke specs, axe a11y (jest-axe / @axe-core/playwright), Pact contract tests, and a GitHub Actions perf-budget + coverage CI. Use when the user asks for 'frontend testing', 'test strategy', 'e2e', 'visual regression', 'playwright setup', 'playwright test', 'unit test', 'integration test', 'write tests', 'test generation', 'test coverage', 'regression test', 'perf budget CI', 'accessibility testing in CI', 'contract testing', 'mutation testing', 'настрой тесты фронта', or wants tests before a release. Scaffolds & advises only — does not run your full CI; you wire the configs in. Composes with frontend-perfection, frontend-a11y, frontend-performance, /frontend.
Agent instruction files
What are agent instruction files?
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.