Debugging
Find and fix bugs, error analysis
rust
by cosmix
Rust language expertise for writing safe, performant, production-quality Rust code. Primary language for the Loom project. Use for Rust development, ownership patterns, error handling, async/await, cargo management, CLI tools, and serialization. Triggers: rust, cargo, rustc, ownership, borrowing, lifetime, trait, impl, struct, enum, Result, Option, async, await, tokio, serde, clap, thiserror, anyhow, Arc, Mutex, RwLock, RefCell, Box, Rc, Vec, HashMap, HashSet, String, derive, macro.
Builder
by simota
å ç¢ãªãã¸ãã¹ãã¸ãã¯ã»APIçµ±åã»ãã¼ã¿ã¢ãã«ãåå®å ¨ãã¤ãããã¯ã·ã§ã³ã¬ãã£ã«æ§ç¯ããè¦å¾æ£ããã³ã¼ãã£ã³ã°è·äººããã¸ãã¹ãã¸ãã¯å®è£ ãAPIçµ±åãå¿ è¦ãªæã«ä½¿ç¨ã
review
by doodledood
Production-level PR review using consultant agent. 10-category framework focused on correctness.
md-tables
by cosmix
Fix markdown table alignment and spacing issues. Use when formatting tables in markdown files, aligning columns, normalizing cell padding, or ensuring proper table structure. Triggers: markdown table, md table, table formatting, column alignment, pipe table, GFM table, table generator, align columns, table spacing, table layout, fix table, format table, table structure.
before-after
by cosmix
Generates before/after verification pairs for loom plans. Proves a stage actually changed system behavior by capturing state before and after implementation. Use for delta-proof verification — proving new commands, endpoints, modules, or bug fixes work by comparing system state.
logging-observability
by cosmix
Comprehensive logging and observability patterns for production systems including structured logging, distributed tracing, metrics collection, log aggregation, and alerting. Triggers for this skill - log, logging, logs, trace, tracing, traces, metrics, observability, OpenTelemetry, OTEL, Jaeger, Zipkin, structured logging, log level, debug, info, warn, error, fatal, correlation ID, span, spans, ELK, Elasticsearch, Loki, Datadog, Prometheus, Grafana, distributed tracing, log aggregation, alerting, monitoring, JSON logs, telemetry.
latex-rescue
by Calix-L
Diagnose and repair LaTeX build failures in local projects or supplied logs. Make minimal source fixes, preserve scientific content and reference keys, and report actual build evidence and unresolved errors.
ux-writing
by 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
by 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
by 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)."
Error Code Guide
by 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
by miles990
SRE principles, observability, and incident management
shell-bash
by miles990
Shell scripting and Bash programming patterns
python
by miles990
Python programming patterns and best practices
ruby
by miles990
Ruby programming patterns and idioms
fix-sphix-docs
by tradingstrategy-ai
Fix errors and warnings in Sphinx docs build
code-review-typescript
by 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
by 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
by 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
by EpicenterHQ
GitHub issue comment guidelines for community interaction. Use when responding to GitHub issues, bug reports, feature requests, or any GitHub discussion.
services-layer
by 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
by 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
by 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
by mhylle
Helps choose between solo, small team, and full team workflow modes