m13-domain-error

Design error-handling frameworks with categorization, recovery options, and implementation patterns for resilient software systems.

287|18|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/fjrevoredo/mini-diarium --skill m13-domain-error-fjrevoredo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m13-domain-error
Source: https://github.com/fjrevoredo/mini-diarium/tree/main/.agents/skills/m13-domain-error
Command: npx skills add https://github.com/fjrevoredo/mini-diarium --skill m13-domain-error-fjrevoredo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides the design and categorization of domain errors, improving error handling strategies across systems.

Core Features & Use Cases

  • Error Categorization: Helps classify errors for user, internal, system, transient, and permanent cases, enabling precise recovery and notification strategies.
  • Design Guidance: Offers prompts and best practices for defining error types suitable for different audiences and recovery methods.
  • Use Case: Use this Skill when building a resilient application that needs structured error management, such as distinguishing between recoverable network errors and fatal data corruption issues.

Quick Start

Use the m13-domain-error skill to understand how to categorize and handle errors in your application's architecture.

Frequently Asked Questions about m13-domain-error

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

FAQPage Schema
What is domain error categorization and how does it improve system resilience?

Domain error categorization classifies errors into user, internal, system, transient, and permanent types. This structured classification improves system resilience by enabling precise recovery strategies and targeted notifications for different failure scenarios.

How do I design an error hierarchy for a resilient application architecture?

Design an error hierarchy by defining specific error types tailored to different audiences and recovery methods. Use structured guidance to distinguish between recoverable transient issues and fatal permanent failures, applying appropriate retry policies and fallback mechanisms for each category.

When should I apply retry policies versus fallback mechanisms in error handling?

Apply retry policies for transient errors like network timeouts, and use fallback mechanisms when retries are exhausted or for permanent errors like data corruption. Categorizing errors by their transient or permanent nature determines the correct recovery strategy.

What is the best way to structure error handling for different audiences in software engineering?

The best way to structure error handling is to classify errors into categories suitable for different audiences. This ensures users receive appropriate notifications while internal teams get detailed diagnostics through structured logging.

Can I use this approach to distinguish between recoverable network errors and fatal data corruption?

Yes, you can use domain error categorization to explicitly distinguish between recoverable network errors and fatal data corruption issues. This allows you to apply targeted recovery options and maintain system stability during failures.