m13-domain-error

Categorize domain errors and design recovery strategies for software systems.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/yumazak/kodo --skill m13-domain-error-yumazak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m13-domain-error
Source: https://github.com/yumazak/kodo/tree/main/.agents/skills/m13-domain-error
Command: npx skills add https://github.com/yumazak/kodo --skill m13-domain-error-yumazak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams to design and reason about domain error handling, including categorization, recovery strategies, and user-facing considerations.

Core Features & Use Cases

  • Structured error categorization (user-facing, internal, transient, permanent)
  • Recovery strategies and patterns (retry with backoff, fallback, circuit breakers)
  • Domain error hierarchy design and mapping to implementation and testing

Quick Start

Model and document domain errors with a clear taxonomy and retry rules for resilient services.

Frequently Asked Questions about m13-domain-error

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

FAQPage Schema
How do I design a domain error hierarchy for resilient services?

Design a domain error hierarchy by categorizing errors as user-facing, internal, transient, or permanent, then mapping recovery strategies and retry rules to each category for resilient services.

What is the best way to implement retry with backoff and circuit breakers?

The best way to implement retry with backoff and circuit breakers is by applying structured recovery patterns that categorize transient errors first, ensuring safe fallbacks and system stability during failures.

When should I use graceful degradation instead of failing a request?

Use graceful degradation instead of failing a request when error categorization identifies the issue as transient or user-facing, allowing the system to apply fallbacks and maintain partial functionality.

How do I categorize transient versus permanent errors in software engineering?

Categorize transient versus permanent errors by modeling a clear domain error taxonomy that separates temporary failures, which require retry strategies, from permanent failures that need immediate user-facing feedback.

Does this approach work for user-facing and internal error contexts?

Yes, this approach works for user-facing and internal error contexts by designing a domain error hierarchy that maps specific recovery strategies and fallback patterns across both system boundaries.