Claude Skills

Use when Java generics including type parameters, wildcards, and type bounds. Use when writing type-safe reusable code.

Use when creating page objects or refactoring Playwright tests for better maintainability with Page Object Model patterns.

Use when prettier integration with editors, pre-commit hooks, ESLint, and CI/CD pipelines.

Use when pylint configuration including pylintrc, message control, plugins, and scoring system.

Use when deciding between inheritance and composition in object-oriented design. Use when creating class hierarchies or composing objects from smaller components.

Use when styling React Native Web components. Provides patterns for StyleSheet API, platform-specific styles, responsive design, and theming.

Use when managing Kubernetes resources including deployments, services, configmaps, and secrets.

Validate checklist items for a ClickUp task without changing status

Use when working with design tokens, CSS custom properties, and primitive values that form the foundation below atoms. Quarks are the sub-atomic building blocks.

Use when creating custom React Flow nodes, edges, and handles. Covers custom node components, resizable nodes, toolbars, and advanced customization.

Core BDD concepts, philosophy, and the Three Amigos practice

Use when setting up or organizing Claude Code project memory (CLAUDE.md, .claude/rules/) for better context awareness, consistent behavior, and project-specific instructions.

Use when designing modules and components requiring Composition Over Inheritance, Law of Demeter, Tell Don't Ask, and Encapsulation principles that transcend programming paradigms.

Use when applying encapsulation and information hiding principles in object-oriented design. Use when controlling access to object state and behavior.

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 investigating bugs, diagnosing issues, or understanding unexpected behavior. Provides systematic approaches to finding root causes.

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 managing memory safely in C++ with smart pointers including unique_ptr, shared_ptr, weak_ptr, and RAII patterns.

Use when prettier plugins including plugin ecosystem, custom parsers, and plugin development.

Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.

Integrate markdownlint into development workflows including CLI usage, programmatic API, CI/CD pipelines, and editor integration.

Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.

Use when advanced Pytest features including markers, custom assertions, hooks, and coverage configuration.

Use when creating generic and type-safe C++ libraries with templates, SFINAE, concepts, and compile-time metaprogramming.