From shipshitdev-backend
Provides error handling patterns, exception filters, error boundaries, logging, retries, and recovery strategies for React, Next.js, and NestJS apps. Use for async errors, monitoring integration, and graceful degradation.
npx claudepluginhub shipshitdev/libraryThis skill uses the workspace's default tool permissions.
Expert in error handling patterns, exception management, error responses, logging, and error recovery strategies for React, Next.js, and NestJS applications.
Provides error handling patterns, exception filters, error boundaries, logging, retries, and recovery strategies for React, Next.js, and NestJS apps. Use for async errors, monitoring integration, and graceful degradation.
Implements error handling patterns including custom error hierarchies, structured logging, retries, circuit breakers, and graceful degradation in JavaScript/TypeScript/Express. Use for try/catch, error responses, logging, and resilience.
Implements error handling patterns like retries, circuit breakers, and async error management for resilient apps, APIs, distributed systems, and debugging.
Share bugs, ideas, or general feedback.
Expert in error handling patterns, exception management, error responses, logging, and error recovery strategies for React, Next.js, and NestJS applications.
Before providing guidance:
.agents/SYSTEM/ARCHITECTURE.md for error patternsApplication Errors: 400, 401, 403, 404, 409, 422 System Errors: 500, 502, 503, 504
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Validation failed",
"details": [...],
"timestamp": "2025-01-01T00:00:00Z",
"path": "/api/users",
"requestId": "req-123456"
}
}
@Catch()
export class AllExceptionsFilter implements ExceptionFilter {
catch(exception: unknown, host: ArgumentsHost) {
// Log, format, respond
}
}
class ErrorBoundary extends React.Component {
componentDidCatch(error, errorInfo) {
// Log to monitoring
}
}
async function retryWithBackoff<T>(fn, maxRetries = 3): Promise<T>
For complete exception filter implementations, custom exceptions, validation pipe setup, error boundaries, circuit breaker pattern, logging integration, and database/API error patterns, see: references/full-guide.md