Testing

interview-me

by mycelium-hq

Use when an ask is underspecified ("build me X" without who it's for, why now, or what success looks like), when a request is conventional rather than specific ("a dashboard", "make it faster" with no number), when Claude catches itself silently filling in ambiguous requirements before any plan, spec, or code exists, or when the user says "interview me", "grill me", "are we sure?", or "stress-test my thinking". Needs a live user; not for CI, scheduled runs, or autonomous loops.

istio

by cosmix

Service mesh implementation with Istio for microservices traffic management, security, and observability. Use when implementing service mesh, mTLS, traffic routing, load balancing, circuit breakers, retries, timeouts, canary deployments, A/B testing, or service-to-service communication. Triggers: istio, service mesh, envoy, sidecar, virtualservice, destinationrule, gateway, mtls, peerauthentication, authorizationpolicy, serviceentry, traffic management, traffic splitting, canary, blue-green, circuit breaker, retry, timeout, load balancing, ingress, egress, observability, tracing, telemetry.

backend-tester

by olehsvyrydov

Senior QA Engineer with 10+ years Java testing experience. Use when writing unit tests with JUnit, creating integration tests with Testcontainers, implementing API tests, following TDD methodology, or testing reactive code with StepVerifier.

test-driven-development

by lv416e

"Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first 機能やバグ修正を実装する際、実装コードを書く前に使用 - まずテストを書き、失敗を確認し、最小限のコードで通す。最初に失敗を求めることで、テストが実際に動作を検証することを保証"

add-package

by remix-run

Create or align a package in the Remix monorepo to match existing package conventions. Use when adding a brand new package under packages/, or when fixing an existing package's structure, test setup, TypeScript/build config, code style, and README layout to match the rest of Remix 3.

nx-run-tasks

by nrwl

Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.

nx-run-tasks

by nrwl

Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.

nx-generate

by nrwl

Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a ... app, create a ... lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.

dart-test

by dartsim

DART testing patterns - unit tests, integration tests, CI validation

dart-python

by dartsim

DART Python bindings (dartpy) - nanobind, wheel building, API patterns

dart-test

by dartsim

"DART Test: unit tests, integration tests, CI validation, and debugging"

dart-mechanical-refactor

by dartsim

"DART Mechanical Refactor: perform a behavior-preserving mechanical refactor"

dart-build

by dartsim

DART build system knowledge - CMake, pixi, dependencies, troubleshooting

indicator-buffer

by DaveSkender

Implement BufferList incremental indicators with efficient state management. Use for IIncrementFromChain or IIncrementFromQuote implementations. Covers interface selection, constructor patterns, and BufferListTestBase testing requirements.

nuxt-modules

by nuxt-content

"Use when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables, plugins), (4) Server extensions (API routes, middleware), (5) Releasing/publishing modules to npm, (6) Setting up CI/CD workflows for modules. Provides defineNuxtModule patterns, Kit utilities, hooks, E2E testing, and release automation."

testing-standards

by DaveSkender

Testing conventions for Stock Indicators. Use for test naming (MethodName_StateUnderTest_ExpectedBehavior), FluentAssertions patterns, precision requirements, and test base class selection.

indicator-stream

by DaveSkender

Implement StreamHub real-time indicators with O(1) performance. Use for ChainHub or QuoteProvider implementations. Covers provider selection, RollbackState patterns, performance anti-patterns, and comprehensive testing with StreamHubTestBase.

code-completion

by DaveSkender

Quality gates checklist for completing code work before finishing implementation cycles

Invalid_Name_With_Underscore

by iwillig

Test with <angle brackets>

interview

by BenjaminG

Interview user to clarify any topic - exploring codebase, investigating issues, planning features, understanding requirements, or drilling into plans. Socratic questioning to uncover details.

mz-test

by MaterializeInc

This skill should be used when the user wants to "run tests", "run testdrive", "run sqllogictest", "run mzcompose", "run cargo test", "run pgtest", "rewrite test results", "add a test", "reproduce a bug", "write a regression test", or mentions testing, testdrive, sqllogictest, mzcompose, pgtest, cargo test, nextest, flaky tests, or test failures in the Materialize repository. Use this skill even if the user just says "test this" or "how do I verify this works" without naming a specific framework.

materialize

by MaterializeInc

nextauth

by claude-dev-suite

NextAuth.js authentication for Next.js. Covers providers, sessions, and callbacks. Use for Next.js authentication. USE WHEN: user mentions "NextAuth", "Next.js auth", "Auth.js", asks about "Next.js authentication", "App Router auth", "next-auth", "authentication providers" DO NOT USE FOR: generic OAuth (use oauth2 skill), JWT implementation (use jwt skill), non-Next.js projects, Express/Fastify auth

testing-principles

by shinpr

Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.