m13-domain-error

Design domain-specific error handling strategies with categorization and recovery patterns.

51|6|Updated Mar 28, 2019

Search Tags:#error handling #resilience #circuit breaker #retry pattern #domain error #recovery strategy

Ready to run

npx skills add https://github.com/Mte90/dotfiles --skill m13-domain-error-mte90

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: m13-domain-error
Source: https://github.com/Mte90/dotfiles/tree/main/.config/opencode/skills/m13-domain-error
Command: npx skills add https://github.com/Mte90/dotfiles --skill m13-domain-error-mte90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers design effective strategies for handling domain-specific errors, ensuring applications are resilient and user-friendly.

Core Features & Use Cases

Error Categorization: Differentiates between user-facing, internal, system, transient, and permanent errors.
Recovery Strategies: Guides the selection of appropriate recovery patterns like retries, fallbacks, and circuit breakers.
Contextual Debugging: Emphasizes the importance of providing necessary context for error debugging.
Use Case: When building a payment processing system, this Skill helps define how to handle transient network errors versus permanent invalid card errors, ensuring appropriate user feedback and system behavior.

Quick Start

Use the m13-domain-error skill to design a strategy for handling payment failures, considering retry policies and user-facing messages.

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 domain error handling strategies for critical system operations?▼

Designing domain error handling strategies involves categorizing errors as transient or permanent, selecting recovery patterns like circuit breakers, and providing debugging context to ensure system resilience. This framework traces error requirements from domain constraints down to implementation details.

What is the best way to handle transient network errors versus permanent validation errors in payment processing?▼

Handling transient versus permanent payment errors requires differentiating recovery strategies: apply retry patterns for transient network failures and provide clear user-facing feedback for permanent invalid card errors. This ensures appropriate system behavior and user communication.

When should I use a circuit breaker or retry pattern for software resilience?▼

You should use circuit breaker or retry patterns when designing recovery strategies for transient system errors. These resilience patterns prevent cascading failures by controlling repeated execution attempts and providing fallback mechanisms during critical system operations.

Can I use this domain error framework to categorize user-facing and internal system errors?▼

Yes, you can use this domain error framework to categorize user-facing, internal, system, transient, and permanent errors. It guides the selection of appropriate recovery patterns and ensures necessary context is provided for effective debugging.

How do I provide contextual debugging information when implementing error recovery strategies?▼

Providing contextual debugging information requires tracing error handling requirements up to domain constraints and down to implementation details. This approach emphasizes including necessary context within error handling strategies to facilitate effective debugging.