Testing
Unit tests, integration tests, test automation
response-compression
by athola
hype, and unnecessary framing. Includes termination and directness guidelines.
mcp-code-execution
by athola
'Use this skill BEFORE building complex tool chains. Optimize proactively.
cpu-gpu-performance
by athola
'Use this skill BEFORE resource-intensive operations. Establish baselines
shared-patterns
by athola
'Reference these patterns to validate consistency across the ecosystem.
bikeshed-conversion
by w3c
Guidelines for converting W3C specs to Bikeshed format. Covers anchor ID preservation, dfn handling, and common pitfalls. Read this before any Bikeshed conversion or migration work.
playwright-best-practices
by NeverSight
Provides Playwright test patterns for resilient locators, Page Object Models, fixtures, web-first assertions, and network mocking. Must use when writing or modifying Playwright tests (.spec.ts, .test.ts files with @playwright/test imports).
e2e
by NeverSight
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.
data-driven-testing
by NeverSight
"DEPRECATED: Use testing-best-practices instead. This skill has been retired."
email-metrics-benchmarks
by sachacoldiq
Email metrics to track, 2X levers, and structure checklist for cold outreach. Use when analyzing campaign performance, setting benchmarks, or optimizing email metrics.
bridgebound-in-market-20
by sachacoldiq
20 "In Market" Bridgebound triggers from Flip The Script - Adjacent Vendors, Competitors, and Time-Based signals. Use when targeting active buyers, building competitive displacement campaigns, or leveraging seasonal/event timing.
list-building-tips
by sachacoldiq
Pro tips for B2B list building - source mixing, enrichment workflow, template usage, and efficiency principles. Use when building prospect lists, optimizing data quality, or improving prospecting efficiency.
regression-auto-baseline
by jmagly
@.claude/rules/executable-feedback.md - Executable feedback rules
systematic-debugging
by FradSer
Provides systematic debugging methodology with 4-phase process (root cause investigation, pattern analysis, hypothesis testing, implementation). Use when encountering any bug, error, failure, broken functionality, test failure, unexpected behavior, troubleshooting issue, or investigating why something isn't working. Always apply before proposing fixes or making changes.
quick
by FradSer
Streamlined code review for rapid assessment and targeted feedback. Use when reviewing small PRs, simple changes, or when you need a quick triage to determine if deeper review is required.
behavior-driven-development
by FradSer
Apply BDD principles including Gherkin scenarios and the Red-Green-Refactor cycle. Use when implementing features, fixing bugs, or refactoring to ensure test-driven development and shared understanding of requirements.
signup-flow-cro
by freekmurze
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
ios-simulator-skill
by freekmurze
21 production-ready scripts for iOS app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management. Optimized for AI agents with minimal token output.
playwright-best-practices
by currents-dev
Provides comprehensive guidance for writing, debugging, and maintaining Playwright tests in TypeScript. Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
skill-authoring
by athola
'Guide to effective Claude Code skill authoring using TDD methodology
causal-inference-root-cause
by lyndonkl
Use when investigating why something happened and need to distinguish correlation from causation, identify root causes vs symptoms, test competing hypotheses, control for confounding variables, or design experiments to validate causal claims. Invoke when debugging systems, analyzing failures, researching health outcomes, evaluating policy impacts, or when user mentions root cause, causal chain, confounding, spurious correlation, or asks "why did this really happen?"
telnyx-ai-assistants-java
by team-telnyx
Create and manage AI voice assistants with custom personalities, knowledge bases, and tool integrations. This skill provides Java SDK examples.
time-series-analysis
by nimrodfisher
Temporal pattern detection and forecasting. Use when analyzing trends over time, detecting seasonality, identifying anomalies in time series, or building simple forecasting models.
ab-test-analysis
by nimrodfisher
Rigorous A/B test statistical analysis. Use when analyzing experiment results, calculating statistical significance, checking for sample ratio mismatch, or validating test design before launch.
dashboard-specification
by nimrodfisher
Design specifications for effective dashboards. Use when planning new dashboards, improving existing ones, or documenting dashboard requirements before development.