Claude Skills

Use when mocha configuration including reporters, config files, plugins, and CI integration.

Use when nestJS guards and interceptors for auth, logging, and transformation. Use when implementing cross-cutting concerns.

Use when implementing navigation in React Native Web projects. Provides patterns for React Navigation, deep linking, and web-specific routing.

Use when validating GraphQL operations/documents against a schema, checking query depth, complexity, or fragment usage.

Use when mocha test structure, hooks, and async testing patterns for JavaScript testing.

Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.

Use when pylint checkers including built-in checkers, custom checkers, and checker development.

Core BDD concepts, philosophy, and the Three Amigos practice

Use when understanding and creating Helm charts for packaging and deploying Kubernetes applications.

Use when jest testing patterns including unit tests, mocks, spies, snapshots, and assertion techniques for comprehensive test coverage.

Use when Go interfaces including interface design, duck typing, and composition patterns. Use when designing Go APIs and abstractions.

Use when publishing CocoaPods libraries to CocoaPods Trunk. Covers pod trunk registration, podspec validation, version management, and publishing best practices for successful library distribution.

Use when ensuring accessible gluestack-ui implementations. Covers WAI-ARIA patterns, screen reader support, keyboard navigation, focus management, and WCAG 2.1 AA compliance.

Use when building reusable component patterns with Tailwind CSS. Covers component extraction, @apply directive, and composable design patterns.

Use when configuring Playwright BDD projects, setting up defineBddConfig(), configuring feature and step file paths, and integrating with Playwright config.

Use when managing multiple environments with Pulumi stacks for development, staging, and production deployments.

Use when investigating bugs, diagnosing issues, or understanding unexpected behavior. Provides systematic approaches to finding root causes.

Use when creating atomic-level UI components like buttons, inputs, labels, and icons. The smallest building blocks of a design system.

Use when vitest configuration, Vite integration, workspace setup, and test environment configuration for modern testing.