m13-domain-error

Define a structured domain error taxonomy for cross-service consistency.

Updated Aug 23, 2026

Search Tags:#architecture #debugging #exceptions #reliability #error-handling #circuit-breaker #domain-errors

Ready to run

npx skills add https://github.com/mberetvas/dbt-migrator --skill m13-domain-error-mberetvas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: m13-domain-error
Source: https://github.com/mberetvas/dbt-migrator/tree/main/.github/skills/m13-domain-error
Command: npx skills add https://github.com/mberetvas/dbt-migrator --skill m13-domain-error-mberetvas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain errors are a major source of confusion and instability in software systems. This guide provides a structured approach to classify errors, decide recovery strategies, and propagate consistent context across services.

Core Features & Use Cases

Error categorization: defines user-facing vs internal vs systemic error types.
Recovery strategies: guides retry, fallback, circuit breaker, and degradation patterns with practical examples.
Cross-layer consistency: standardizes error naming, context, and logging to ease debugging and support.

Quick Start

Define a domain error hierarchy and apply it across services to ensure consistent categorization, messaging, and recovery behavior.

Frequently Asked Questions about m13-domain-error

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a structured domain error taxonomy and why do I need it for my services?▼

A structured domain error taxonomy standardizes error types and messaging across services. It categorizes user-facing, internal, and systemic errors to enable traceability, debuggability, and recoverability throughout your software architecture.

How do I design error handling recovery strategies for asynchronous flows?▼

Design error handling recovery strategies for asynchronous flows by applying patterns for retry, fallback, circuit breaker, and degradation. This ensures recoverability and maintains system reliability when operations fail across distributed services.

How do I standardize error context and logging across synchronous and asynchronous services?▼

Standardize error context and logging across synchronous and asynchronous services by enforcing consistent error naming and context propagation. This cross-layer consistency eases debugging and support across your architecture.

When should I apply circuit breaker and degradation patterns for domain errors?▼

Apply circuit breaker and degradation patterns when domain errors threaten system stability. These recovery strategies prevent cascading failures by isolating faults and providing fallback behavior during systemic errors or service disruptions.

What's the best way to classify user-facing versus internal domain errors?▼

Classify user-facing versus internal domain errors by defining a structured error hierarchy. This categorization separates external messaging from internal faults, ensuring consistent handling and clear traceability across your services.