error-class-hierarchy-builderlisted

# Error Class Hierarchy Builder ## Prerequisites & Dependencies - Node.js 18+ or Python 3.10+, TypeScript strongly preferred - Understanding of try/catch blocks and error propagation - Optional: `npm i @types/node` for TS, or built-in `http`/`status` codes ## Execution Steps 1. Define a base custom error class that captures domain-wide concerns: `errorCode`, `httpStatus`, `metadata` (retry-after, correlation ID, etc.) 2. Extend the hierarchy for specific domains: validation errors, authentication failures, not-found resources, server errors 3. Standardize the constructor signature: `new AppError(message, httpStatus, metadata)` across all subclasses 4. Add helper methods: `isOperational`, `sendDev`, `sendProd` (different error output for dev vs prod) 5. Use the hierarchy consistently across the codebase, replacing generic `try/catch` with typed catches 6. Document the error taxonomy and ensure all team members throw/customize errors using the same pattern ```typescript // Base AppError with code, status, and metadata class AppError extends Error { public readonly errorCode: string; public readonly httpStatus: number; public readonly metadata: Record<string, unknown>; constructor(message: string, httpStatus = 500, metadata: Record<string, unknown> = {}) { super(message); this.name = 'AppError'; this.errorCode = metadata.code || 'UNKNOWN_ERROR'; this.httpStatus = httpStatus; this.metadata = metadata; Error.captureStackTrace(this, this.construc