Claude Skills

Use when writing shell scripts that need to run across different systems, shells, or environments. Covers POSIX compatibility and platform differences.

Use when designing GraphQL schemas with type system, SDL patterns, field design, pagination, directives, and versioning strategies for maintainable and scalable APIs.

Use when configuring Sentry alerts, managing issues, or setting up notifications. Covers alert rules, issue triage, and integrations.

Use when creating temporary files, drafts, experiments, or any content that should not be committed to version control. Ensures proper placement in .claude/.scratch with gitignore configuration.

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

Use when Go concurrency with goroutines, channels, and sync patterns. Use when writing concurrent Go code.

Use when configuring shfmt for shell script formatting including .shfmt.toml setup, EditorConfig integration, and project-specific settings.

Use when defining completion criteria for AI-DLC tasks. Covers writing verifiable, specific, and measurable criteria that enable autonomous operation and clear exit conditions.

Use when formatting shell scripts with shfmt. Covers consistent formatting patterns, shell dialect support, common issues, and editor integration.

Use when advanced RSpec features including custom matchers, shared examples, metadata, and hooks.

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

Use when creating implementation plans for features or tasks. Focuses on tactical execution planning with clear tasks, dependencies, and success criteria.

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.

Configure markdownlint rules and options including rule management, configuration files, inline comments, and style inheritance.

Use when auditing GraphQL operations for complexity metrics, depth analysis, directive usage, or query performance concerns.

Use when Go error handling with error wrapping, sentinel errors, and custom error types. Use when handling errors in Go applications.

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

Use when jUnit fundamentals including annotations, assertions, and test lifecycle for Java testing.

Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.

Use when prettier configuration including options, config files, ignore patterns, and formatting rules.

Use when configuring Docker environments for act, selecting runner images, managing container resources, or troubleshooting Docker-related issues with local GitHub Actions testing.

Configure markdownlint rules and options including rule management, configuration files, inline comments, and style inheritance.

Use when jUnit parameterized tests with various value sources and test factories.

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