Testing

Unit tests, integration tests, test automation

Showing 2713-2736 of 5551 skills
bnadlerjr

developing-typescript

by bnadlerjr

Comprehensive TypeScript/React development expertise covering advanced type systems, React component architecture, hooks patterns, state management, GraphQL integration with Apollo, performance optimization, and React Testing Library. Use when working with .ts/.tsx files, React components, or when the user mentions TypeScript, React, hooks, Context, Apollo, GraphQL codegen, React Testing Library, Vite, or Next.js. Also use for generic types, component patterns, or bundle optimization.

Testing 5 4mo ago
dangeles

synthesizer

by dangeles

Use when multiple reviews or paper notes need integration, cross-cutting themes must be identified, or project-specific implications must be drawn from disparate sources

Academic 5 4mo ago
negz

nix-flake

by negz

Develop projects that use a Nix flake. Use when building, testing, linting, running dev commands, or entering a dev shell for a project that has a flake.nix. NOT for running ad-hoc CLI tools - use nix-tools for that.

CLI Tools 5 3mo ago
ranbot-ai

add_repo_inst

by ranbot-ai

Please browse the current repository under /workspace/{{ REPO_FOLDER_NAME }}, look at the documentation and relevant code, and understand the purpose of this repository.

File Ops 5 4mo ago
Lightprotocol

light-sdk

by Lightprotocol

"Build rent-free Solana programs with Light SDK. For DeFi (AMMs, vaults, lending), infrastructure, or any Solana program. Anchor macros or Pinocchio patterns. Covers state structs, account creation, CPI, client SDK, router integration, and testing."

Automation 5 3mo ago
bnadlerjr

refactoring-code

by bnadlerjr

Identifies code smells and applies refactoring patterns for OOP and FP codebases. Use when improving code structure, reducing technical debt, cleaning up messy code, or when the user mentions refactoring, code smells, or "make this cleaner".

File Ops 5 4mo ago
v1-io

debug

by v1-io

Use when debugging errors, diagnosing failures, or tracing root causes from error output. Triggers on "debug this", "why is this failing", "trace the error".

Debugging 5 4mo ago
ranbot-ai

ab-test-setup

by ranbot-ai

Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

Monitoring 5 3mo ago
Lightprotocol

testing

by Lightprotocol

"Test Light Protocol programs and clients for localnet, devnet and mainnet"

Automation 5 3mo ago
bnadlerjr

practicing-tdd

by bnadlerjr

Enforces test-first development with Red-Green-Refactor cycle. Use when implementing features, fixing bugs, writing tests, or when someone mentions TDD, test-driven, "test first", or "write a failing test".

Debugging 5 4mo ago
dangeles

ai-strategist

by dangeles

Use when evaluating AI tools and agentic workflows against workflow gaps, when conducting quarterly landscape scans, or when assessing integration feasibility of new tools for startup workflows.

Agents 5 4mo ago
negz

skill-creator

by negz

Create new skills, modify and improve existing skills. Use when users want to create a skill from scratch, turn a workflow into a skill, update or optimize an existing skill, improve a skill's description for better triggering accuracy, or when they mention SKILL.md files.

Agents 5 3mo ago
bnadlerjr

creating-agents

by bnadlerjr

Expert guidance for creating, auditing, and improving Claude Code agent definition files (.md). Use when working with ~/.claude/agents/ files, authoring new sub-agents, improving existing agents, or understanding agent configuration and system prompt best practices.

Agents 5 4mo ago
robdtaylor

Algorithm

by robdtaylor

Universal 7-phase execution pattern for all work. USE WHEN starting complex tasks, needing structured approach, defining success criteria, or tracking work phases.

Code Gen 5 4mo ago
negz

go-code-factoring

by negz

Factor and structure Go code for clarity, testability, and composability. Use when writing new Go code, refactoring existing code, reviewing code structure, adding interfaces, decomposing large functions or structs, or when the user mentions factoring, refactoring, architecture, or code organization. Also use before writing unit tests to ensure code is well structured.

Debugging 5 3mo ago
third774

eslint-plugin

by third774

Author custom ESLint plugins and rules with test-driven development. Supports flat config (ESLint 9+) and legacy formats. Uses @typescript-eslint/rule-tester for testing. Covers problem, suggestion, and layout rules including auto-fixers and type-aware rules. Use when creating or modifying ESLint rules, plugins, custom linting logic, or authoring auto-fixers.

Linting 5 4mo ago
v1-io

interview-me

by v1-io

Collaboratively refine ideas through structured questioning - helping both Claude understand and the user crystallize their thinking. Use when the user provides an idea, feature request, Linear ticket, or concept that needs fleshing out. Triggers on requests like "interview me about X", "help me spec out Y", "I have an idea for Z", or when explicitly invoked. Output format adapts to context (update existing artifacts, create new specs, or just synthesize insights).

Code Gen 5 5mo ago
bnadlerjr

testing-elixir

by bnadlerjr

Provides expert guidance for writing ExUnit tests in Elixir. Covers core ExUnit patterns, assertions, sociable testing philosophy, Ecto sandbox and database testing, Phoenix controller/LiveView/channel tests, and external API testing with Bypass and Req.Test. Use when working with ExUnit tests, assertions, describe blocks, test organization, Bypass, Req.Test, factories, ExMachina, Ecto sandbox, ConnTest, LiveViewTest, ChannelTest, or test helpers.

API Dev 5 4mo ago
v1-io

fix-tests

by v1-io

Use when tests are failing and need systematic fixing until all pass. Triggers on "fix tests", "tests failing", "make tests pass".

CLI Tools 5 4mo ago
robdtaylor

Controlplan

by robdtaylor

Generate AIAG-format Control Plans linked to PFMEAs with proper inspection methods, frequencies, and reaction plans. Supports Prototype/Pre-launch/Production phases. USE WHEN user says 'control plan', 'CP', 'inspection plan', 'process control', 'sampling frequency', 'reaction plan', or 'special characteristics'. Integrates with PFMEA, AutomotiveManufacturing, and MSA skills.

Code Review 5 4mo ago
negz

go-unit-tests

by negz

Write unit tests for Go code. Use when creating, adding, or updating Go tests, writing table-driven tests, creating mocks or fakes, adding test coverage, or when the user mentions testing, cmp.Diff, assertions, or test cases. Also use when reviewing whether code is testable.

Debugging 5 3mo ago
robdtaylor

Automotiveproductplanning

by robdtaylor

Strategic 5-10 year product planning for low-volume sportscar and specialist vehicle manufacturers. Covers new production vehicles, restomods/continuation cars, bespoke commissions, and motorsport programmes. Board-ready financial analysis with NPV/IRR. Integrates with HoshinKanri, SupplyChain, and AutomotiveManufacturing skills. USE WHEN creating product roadmaps, model lifecycle planning, platform strategy, powertrain transitions, competitive positioning, or OEM partnership evaluation.

Code Gen 5 4mo ago
robdtaylor

Costengineering

by robdtaylor

Manufacturing cost accounting, analysis, and reduction for automotive operations. Covers overhead/burden rate calculation, variance analysis, make vs buy decisions, value engineering, and cycle time to cost conversion. USE WHEN user says 'cost analysis', 'overhead rate', 'burden rate', 'variance analysis', 'make vs buy', 'value engineering', 'cost reduction', 'should cost', 'labour rate', or needs manufacturing cost guidance.

Finance 5 4mo ago
v1-io

e2e-testing

by v1-io

Use when implementing E2E tests, debugging flaky tests, testing web applications with Playwright, or establishing E2E testing standards. Triggers on "e2e test", "end-to-end", "Playwright", "flaky test", "browser test".

Auth 5 4mo ago