Claude Skills

Writing effective step definitions and organizing test code

Use when advanced Cypress features including custom commands, plugins, and network stubbing.

Use when building GraphQL APIs with Apollo Server requiring resolvers, data sources, schema design, and federation.

Use when implementing Apollo Client patterns for queries, mutations, cache management, and local state in React applications.

Use when implementing async/await, Task management, actors, or Combine reactive patterns in iOS applications.

Use when jest configuration, setup files, module resolution, and project organization for optimal testing environments.

Use when managing Helm values files and configuration overrides for customizing Kubernetes deployments.

Use when vitest performance optimization including fast execution, watch mode, and parallelization strategies.

Use when working with Helm templates and template functions for generating Kubernetes manifests dynamically.

Use when testing Effect code including Effect.gen in tests, test layers, mocking services, and testing error scenarios. Use for writing tests for Effect applications.

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

Use when implementing data-driven tests with TestNG DataProviders, factory methods, and parameterization patterns.

Use when responding to production incidents following SRE principles and best practices.

Use when managing state and side effects in Ink applications using React hooks for terminal UIs.

Use when designing monorepo structure, organizing packages, or migrating to monorepo architecture with architectural patterns for managing dependencies and scalable workspace configurations.

Use when creating terminal layouts with Ink using Flexbox-based positioning and styling for CLI applications.

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

Use when eSLint configuration including config files, extends, plugins, and environment setup.

Use PROACTIVELY when a user describes work that sounds like a feature, project, or task. Detects intent patterns and offers to start AI-DLC elaboration.