Claude Skills

Use when restructuring code to improve quality without changing external behavior. Emphasizes safety through tests and incremental changes.

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

Use when Rust async programming with tokio, async/await, and futures. Use when writing asynchronous Rust code.

Use when building modular Angular applications requiring dependency injection with providers, injectors, and services.

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

Use when typeScript async patterns including Promises, async/await, and async iterators with proper typing. Use when writing asynchronous TypeScript code.

Use when implementing Apollo caching strategies including cache policies, optimistic UI, cache updates, and normalization.

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 configuring Sentry alerts, managing issues, or setting up notifications. Covers alert rules, issue triage, and integrations.

Use when updating, versioning, deprecating, or maintaining existing Standard Operating Procedures. Covers keeping SOPs accurate, relevant, and synchronized with implementation changes.

Use when writing technical documentation, READMEs, or project documentation in markdown. Covers structure, conventions, and best practices.

Use when creating or formatting tables in markdown. Covers table syntax, alignment, escaping, and best practices.

Use when writing SOPs that require precise requirement levels using RFC 2119 constraint keywords (MUST, SHOULD, MAY). Covers proper usage of requirement keywords for deterministic agent behavior.

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

Mark a Linear issue as complete after validating acceptance criteria

Use when defining and working with Ecto schemas including field types, associations, and embedded schemas. Use when modeling database entities in Elixir.

Use when defining data structures using Ecto schemas including fields, associations, embedded schemas, and schema metadata. Use for modeling domain data in Elixir applications.

Use when explaining code, technical concepts, or implementation decisions. Provides structured approach to creating clear, understandable explanations tailored to the audience.

Search for ClickUp tasks