Claude Skills

Master Python asynchronous programming with asyncio, async/await,

Use when configuring parallel test execution with TestNG including thread pools, suite configuration, and synchronization.

Use when ruboCop configuration including YAML config, departments, inheritance, and customization.

Use when applying Clippy lint categories for Rust code including correctness, performance, style, and custom lint configuration.

Use when Python's type system including type hints, mypy, Protocol, TypedDict, and Generics. Use when working with Python type annotations.

Use when eSLint built-in rules including rule configuration, severity levels, and disabling strategies.

Use when custom ESLint rules and plugins including rule development, AST traversal, and publishing.

Use when pytest plugin ecosystem including pytest-cov, pytest-mock, and custom plugin development.

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

Use when querying data with Ecto.Query DSL including where clauses, joins, aggregates, preloading, and query composition. Use for building flexible database queries in Elixir applications.

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

Use when creating troubleshooting guides and diagnostic procedures for operational issues. Covers problem diagnosis, root cause analysis, and systematic debugging.

Use when Rust error handling with Result, Option, custom errors, thiserror, and anyhow. Use when handling errors in Rust applications.

Use when active Record patterns including models, associations, queries, validations, and callbacks.

Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.

Use when building comprehensive monitoring and observability systems.

Use when creating incident response procedures and on-call playbooks. Covers incident management, communication protocols, and post-mortem documentation.

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

Use when creating structured operational runbooks for human operators. Covers runbook organization, documentation patterns, and best practices for clear operational procedures.