Proactively reviews error handling patterns and suggests improvements using Result types, proper error propagation, and idiomatic patterns.
Generate error handling middleware for any framework. Use when setting up API error handling.
Error Handler Middleware - Auto-activating skill for Backend Development. Triggers on: error handler middleware, error handler middleware Part of the Backend Development skill…
Use when implementing structured error handling in backend or frontend code. Triggers for: try-catch patterns, custom exception classes, global error handlers, error logging,…
Enforce proper error handling patterns. Use when writing async code, API calls, or user-facing features.
Production-ready API error handling for Next.js with standardized error codes, request tracking, user-friendly messages, and automatic error wrapping.
Audits Go code for error handling best practices - proper wrapping with %w, preserved context, meaningful messages, no error swallowing.
Find and fix unsafe error handling in Leavn - try! force unwraps, empty catch blocks, silent try? failures
Evaluates if error handling is sufficient for new code - checks try-catch coverage, logging, user messages, retry logic. Focuses on external calls and user-facing code.
Use when when implementing or auditing a data replacement method (e.g., `mz<-`, `intensity<-`) in an MsBackend subclass that must enforce ordering or format constraints on peak…
Use when designing or implementing a cross-cutting Apex error handling framework: custom exception hierarchies, rollback-safe logging via Platform Events, BatchApexErrorEvent…
Auto-invoke when reviewing try/catch blocks, API error responses, async operations, or user feedback patterns. Enforces graceful degradation and meaningful error messages.
Verify errors are handled gracefully with meaningful user feedback. Issues result in WARNINGS.
Design and document a error handling guide with structured process, quality checks, and system integration
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.
Design error states and recovery workflows that guide users to resolution. Learn context-aware error messages, graceful degradation, and recovery patterns.
Review test cases for OAuth/OIDC error handling. Covers authorization endpoint errors, token endpoint errors, error response formats, HTTP status codes, and all error codes per…
RFC 9457 Problem Details for standardized HTTP API error responses. Use when implementing problem details format, structured API errors, error registries, or migrating from RFC…
Design error prevention, detection, and recovery across a product — message content, placement, and escape routes. Use when errors span multiple flows.
**AUTO-TRIGGER:** Invoked by yolo1 skill after every commit to analyze session errors.
Error Mapping Helper - Auto-activating skill for API Integration. Triggers on: error mapping helper, error mapping helper Part of the API Integration skill category.
Configure with error mapping helper operations. Auto-activating skill for API Integration. Triggers on: error mapping helper, error mapping helper Part of the API Integra — from…
Use when: making a mistake, breaking build/tests, realizing wrong approach, misunderstanding requirements, using wrong patterns, forgetting conventions, receiving correction from…
Sanook writes and audits user-facing error and exception messages so they state what failed, why, and the next action — actionable, specific, non-blaming, no leaked internals —…
Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.
Write errors and log lines that name the failing thing, the offending value, and the likely fix — for the 3am reader.
Audit error messages across an application for clarity, actionability, consistency, and user-friendliness by cataloging and grading every error surface.
Cross-proxy/process error check with aggregation, dedup, periodic monitoring — not bash grep -r error / tail -f / journalctl -f / curl probes.
Create custom 404 and 500 error pages with brand styling. Use at project end before release. Triggers on "404", "error pages", "not found", "500 error".
Error handling patterns: classification, recovery, logging, graceful degradation, resilience.
Use when an operation fails, an error occurs, or a warning needs to be communicated to the user
Trace error propagation through a multi-agent session by agent depth — where failures originated, the depth at which they appeared, and how they cascaded up to parent agents —…
Strategies for handling subagent failures with retry logic and escalation patterns.
Engineer resilient UI systems with layered error boundaries, retries, and fallback orchestration.
Error recovery and failure handling patterns for distributed systems including rollback strategies, circuit breakers, retry logic with exponential backoff, graceful degradation,…
Design robust error recovery, retry logic, and fallback strategies for production AI agents. Covers transient failure handling, circuit breakers, exponential backoff, state…
Turn a diagnosed learning error into the smallest corrective intervention, changed practice, and delayed re-check without shaming or answer leakage.
Generate a categorized error summary from server logs. Shows what's failing, frequency, severity, and recommendations.
Use when when a user uploads a JSON project document to the Pairing Omics Data Platform and you need to determine whether it satisfies the platform's data structure requi — from…
Expert guide for error handling patterns, resilience engineering, retry strategies, circuit breakers, and graceful degradation across React, Next.js, and Node.js / Panduan ahli…
Read the error-patrol ledger, check each linked task's current status via the task store, and resolve the corresponding Sentry issue once its gating task has reached…
Systematic error diagnosis and resolution using first-principle analysis. Use when encountering any error message, stack trace, or unexpected behavior.
Production-safe error handling that logs full details server-side while exposing only generic, safe messages to users.
Scan recent Claude Code activity for errors and failure signals across all sessions using Agent Monitor data — APIError events and PreToolUse→PostToolUse gaps (tools that started…
Standard error response taxonomy and envelope for services, including error codes, categories, retryability, correlation IDs, safe messaging, and validation error details — from…
Standard error response taxonomy and envelope for services, including error codes, categories, retryability, correlation IDs, safe messaging, and validation error details — from…
[STATUS: confirmed] [CONFIDENCE: high] [VALIDATED: 2026-04-18] После исправления бага или инцидента — структурирует урок в переиспользуемый паттерн с причиной, fix-ом, и kill…
Implement error tracking with Sentry for automatic exception monitoring, release tracking, and performance issues.
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code.
Stream errors from proxies and processes in real time via agnt watch + Monitor - Claude reacts instantly when problems appear.
GOÄ § 10 Ersatz von Auslagen: prüft die einschlägigen Voraussetzungen, Dokumente, Risiken und Ausnahmen.
Für Ersatz: Sonderfall und Edge-Case-Prüfung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.
Prüft Einsatz eigener Mitarbeiter/Subunternehmer als Indiz für Selbständigkeit und rechtliche Nebenrisiken im Sozialversicherungsstatus Prüfer.
MRO-Gesellschaft oder Airline braucht Inventar-Dashboard für Ersatzteillager: EASA-Zertifizierungsstatus Pfandrechte Cape-Town-Eintrag Versicherung Wert.
Ersatzteillager für Luftfahrzeuge: unklar welche Behörde zuständig ist LBA EASA Zollbehoerde oder Gefahrgut-Aufsicht.
Ersatzteillager braucht Genehmigungen: EASA Part-145 AMO-Zertifizierung LBA-Anerkennung Zollgenehmigung Gefahrguterlaubnis.
MRO-Betrieb oder Airline mit grossem Ersatzteillager zeigt Insolvenzzeichen. Prüft InsO §§ 47 50 103 Aus- und Absonderungsrechte an Ersatzteilen und Werkzeugpfandrecht des…
Deutsches Kanzleiteam muss ausländischen Anwalt für Ersatzteillager-Mandat briefen: EASA-Zertifizierungsstatus Cape-Town-Triebwerks-Pfandrecht deutsches Insolvenzrecht.