Depuració
Detecció i correcció de problemes i anàlisi d’errors
ux-writing
content-designer
Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.
claude-code-plugins
melodic-software
"Produce a structured 5-field bug report (title, steps to reproduce, expected vs actual, severity with justification, suggested fix location) from an informal description. Read-only, never modifies code, never opens PRs, never files issues by default. Use when the user names a defect they observed ('there is a bug in <X>', 'expected X got Y', 'I am seeing <error> in <file>') or asks for one written up ('report a bug', 'file a bug', 'write this up as a bug'). Skip when: deep investigation is needed, a fix is already in progress, or the request is a feature request (missing capability) rather than a defect. Emits Markdown to stdout by default; with --file, persists a report file and can hand off to a work-item tracker for filing."
claude-code-plugins
melodic-software
"Proactively hunt unobserved bugs in resting code: a read-only two-stage scan, recall-biased per-lens hunter subagents, then a separate fresh-context default-refute gate, over a target path/feature/diff or a rotated lane, emitting only verified 5-field findings. Use when: 'find a bug', 'bug hunt', 'scan for bugs', 'hunt for bugs in <X>'. Skip when: reviewing a diff (review:code-review); security auditing (review:security-review); root-causing an observed failure (debugging:debug); doc/config/code/arch claim drift, all dimensions (codebase-health:audit); structural tidying (code-tidying:tidy); comment markers (work-items:scan-todos); coverage gaps (testing:audit, mutation-testing:audit). Disambiguation: 'scan repo for issues' is the upstream known-issue registry (claude-ops:known-issues); 'file a bug' the user observed is bugs:write. Bare invocation neither edits nor files; --track files verified findings as raw intake (subject to the team's filing_posture)."
k8s-core
rohitg00
Core Kubernetes resource management for pods, namespaces, configmaps, secrets, and nodes. Use when listing, inspecting, or managing fundamental K8s objects.
Error Code Guide
AsiaOstrich
Design consistent error codes following the PREFIX_CATEGORY_NUMBER format. Use when: defining error codes, creating error handling, designing APIs. Keywords: error code, error handling, error format, API errors, 錯誤碼, 錯誤處理.
reliability-engineering
miles990
SRE principles, observability, and incident management
shell-bash
miles990
Shell scripting and Bash programming patterns
python
miles990
Python programming patterns and best practices
ruby
miles990
Ruby programming patterns and idioms
fix-sphix-docs
tradingstrategy-ai
Fix errors and warnings in Sphinx docs build
code-review-typescript
ssiumha
TypeScript type safety review checklist. Injected into code-reviewer agent for TypeScript/TSX projects. Use when reviewing TypeScript code for type safety or auditing type definitions.
next-devtools-guide
FradSer
This skill should be used when working with Next.js projects that have the next-devtools MCP server configured, when encountering MCP connection issues, or when needing guidance on which MCP tool to use for specific tasks such as error detection, route inspection, Server Action tracing, or Cache Components migration.
elysia
EpicenterHQ
Elysia.js server patterns for error handling, status responses, and plugin composition. Use when writing Elysia route handlers, returning HTTP errors, creating plugins, or working with Eden Treaty type safety.
github-issues
EpicenterHQ
GitHub issue comment guidelines for community interaction. Use when responding to GitHub issues, bug reports, feature requests, or any GitHub discussion.
services-layer
EpicenterHQ
Service layer patterns with createTaggedError, namespace exports, and Result types. Use when creating new services, defining domain-specific errors, or understanding the service architecture.
query-layer
EpicenterHQ
Query layer patterns for consuming services with TanStack Query, error transformation, and runtime dependency injection. Use when implementing queries/mutations, transforming service errors for UI, or adding reactive data management.
rust-errors
EpicenterHQ
Rust to TypeScript error handling patterns for Tauri apps. Use when defining Rust errors that will be passed to TypeScript, handling Tauri command errors, or creating discriminated union error types.
workflow-guide
mhylle
Helps choose between solo, small team, and full team workflow modes
templ-http
Xe
Integrate templ components with Go HTTP server using net/http. Use when connecting templ to web server, creating HTTP handlers, mentions 'templ server', 'HTTP routes', or 'serve templ components'.
templ-syntax
Xe
Learn and write templ component syntax including expressions, conditionals, loops, and Go integration. Use when writing .templ files, learning templ syntax, or mentions 'templ component', 'templ expressions', or '.templ file syntax'.
authoring-dags
astronomer
Workflow and best practices for writing Apache Airflow DAGs. Use when the user wants to create a new DAG, write pipeline code, or asks about DAG patterns and conventions. For testing and debugging DAGs, see the testing-dags skill.
review-pr
alpinejs
Review an open PR like a maintainer — checkout, fix issues, push changes, post a structured verdict comment. You just merge or close.
react
cosmix
Modern React development patterns including components, hooks, state management, routing, forms, and UI architecture. Covers React 19+, React Router v7, Jotai atoms, server components, accessibility, performance optimization, and testing. Use for building React applications with client-side routing, global state, component composition, and async data loading. Triggers: react, jsx, tsx, component, hook, useState, useEffect, useContext, useReducer, useMemo, useCallback, useRef, props, state, render, virtual DOM, reconciliation, single page application, spa, react-router, jotai, vite, bun, Next.js, Remix, client-side routing, server components, accessibility, a11y, ARIA, performance, code splitting, lazy loading, Suspense, error boundaries, form validation, UI components, design system, composition patterns.
event-driven
cosmix
Event-driven architecture patterns including message queues, pub/sub, event sourcing, CQRS, and sagas. Use when implementing async messaging, distributed transactions, event stores, command query separation, domain events, integration events, data streaming, choreography, orchestration, or integrating with RabbitMQ, Kafka, Apache Pulsar, AWS SQS, AWS SNS, NATS, event buses, or message brokers.