testing
lobehub/lobehub/.agents/skills/testing/SKILL.md
Use for Vitest tests, mocks, coverage and failing-test diagnosis.
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.
lobehub/lobehub/.agents/skills/testing/SKILL.md
Use for Vitest tests, mocks, coverage and failing-test diagnosis.
iOfficeAI/AionUi/.claude/skills/testing/SKILL.md
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
JetBrains/intellij-community/.agents/skills/testing/SKILL.md
Run or troubleshoot IntelliJ `tests.cmd` tests and discovery.
JetBrains/intellij-community/.claude/skills/testing/SKILL.md
Run or troubleshoot IntelliJ `tests.cmd` tests and discovery.
kortix-ai/suna/.agents/skills/testing/SKILL.md
Use for every Kortix test task, behavior change, bug fix, refactor, API route change, CLI change, SDK change, browser journey, test failure, coverage question, local benchmark, or testing infrastructure change. Enforce the single local-first runner, black-box flow contracts, package-local SDK tests, browser-only Playwright tests, and real input/output verification.
modelcontextprotocol/inspector/.claude/skills/testing/SKILL.md
Run, place and fix tests in this repo. Use when choosing which npm command runs a given suite (web unit, web integration, Storybook, cli, tui, launcher, scripts); when deciding where a new test file belongs — beside its source, under src/test/, or in a client's __tests__/; when a per-file coverage check fails or a v8 ignore is in question; when asking which test tier spawns the built binary rather than importing it; or when rendering, mounting or asserting on Mantine components and their transitions in a test.
microsoft/fast/.github/skills/testing/SKILL.md
Use this skill when running or writing tests in the FAST monorepo — local test execution, CI workflows, Playwright fixtures, and WebUI integration testing.
bytebase/dbhub/.claude/skills/testing/SKILL.md
Run and troubleshoot tests for DBHub, including unit tests, integration tests with Testcontainers, and database-specific tests. Use when asked to run tests, fix test failures, debug integration tests, troubleshoot Docker/database container issues, or add new tests. Also use when verifying code changes work correctly or when CI test failures need investigation.
BankrBot/skills/ethskills-testing/SKILL.md
Smart contract testing with Foundry — unit tests, fuzz testing, fork testing against live state, and invariant testing. What to test, what to skip, and what LLMs commonly get wrong.
vm0-ai/vm0/.claude/skills/testing/SKILL.md
Comprehensive testing patterns and anti-patterns for writing and reviewing tests
cloudflare/sandbox-sdk/.agents/skills/testing/SKILL.md
Use when writing or running tests for this project. Covers unit vs E2E test decisions, test file locations, mock patterns, and project-specific testing conventions. (project)
microsoft/CCF/.github/skills/testing/SKILL.md
Select, run, and write CCF unit, end-to-end, partition, compatibility, coverage, and Python SDK tests. Covers prerequisites, the tests.sh wrapper, test labels, and e2e registration.
evanca/flutter-ai-rules/skills/testing/SKILL.md
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
FerroxLabs/wayland/.claude/skills/testing/SKILL.md
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
notque/vexjoy-agent/skills/process/testing/SKILL.md
Testing: TDD, E2E, preferred patterns, verification, agent testing.
Mindrally/skills/testing/SKILL.md
General testing best practices and guidelines for writing comprehensive, maintainable tests across different testing frameworks and languages.
NVIDIA/nvcf/src/uis/nvcf-ui/.claude/skills/testing/SKILL.md
Writing frontend tests for the nvcf-ui app — Vitest, Testing Library, MSW, and project-specific render helpers. Use when creating test files, writing component tests, setting up MSW handlers in tests, deciding which render helper to use, or when the user is adding or modifying a UI component and hasn't mentioned tests yet (tests are required). Covers TypeScript/React only — Go backend tests follow standard Go patterns.
alexeykrol/claude-code-starter/.claude/skills/testing/SKILL.md
Запуск тестов проекта: unit, integration. Определение типа проекта и выбор стратегии.
dylanroscover/Embody/.claude/skills/testing/SKILL.md
MUST READ before declaring any TouchDesigner build, fix or show done, and before any soak or performance test: the verification ladder (structure, errors, frame, motion, data, performance, soak, end to end), run_soak_test and the observer-effect rules that keep measuring from perturbing the show, the iterate-by-capture loop, and what done means.
VeryGoodOpenSource/vgv-ai-flutter-plugin/skills/testing/SKILL.md
Best practices for Dart unit tests, Flutter widget tests, and golden file tests, covering group and test naming, setUp lifecycle and isolation, mocking with package:mocktail, and the shared pumpApp helper. Use when writing, modifying, or reviewing tests, goldens included, that use package:test, package:flutter_test, package:mocktail, or package:bloc_test. Use it also when no package is named: "add a golden test for my AppButton widget", "write a goldens test", goldens, matchesGoldenFile, tagging or updating goldens, writing a unit test or widget test, or adding a test helper or mock. A one-line golden or widget test request is in scope, including under "Dart code only"; a widget in a UI package is ui-package's. Use it too when the request asks for what these standards forbid: package:mockito, a raw string test tag instead of TestTag, an inline pumpWidget(MaterialApp(...)), asserting padding, color or font size in a widget test, or state shared between tests. Those requests are in scope, not out of it.
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.