M13 Domain Error
zhanghandong/rust-skillsWhen software fails, how you handle the error makes all the difference. A good domain error strategy helps you decide who should see the error and how they can recover. You can separate errors into user-facing, internal, and system types. Each has its own best response.
Some errors are transient and can be fixed by retrying with a short wait. Others are permanent and need a person to investigate. You can also use patterns like fallback values or a circuit breaker to keep your system running even when things go wrong.
By categorizing errors early, you make your code easier to debug and more resilient. Your users see clear messages, your developers get useful details, and your operations team can alert on real problems. This skill gives you the building blocks for solid error handling in any application.
Add M13 Domain Error skill to your workflow
Global
mkdir -p ~/.claude/skills/m13-domain-errorProject
mkdir -p .claude/skills/m13-domain-errorSource Repository
More Debugging Claude Code Skills
Azure Diagnosticsmicrosoft/azure-skills
Debug Azure production issues with systematic diagnostics and AI-powered tools
Azure Messagingmicrosoft/azure-skills
Troubleshoot and fix Azure messaging SDK errors for Event Hubs and Service Bus
Use My Browserxixu-me/skills
Work inside your live browser session for real page inspection and debugging
Diagnosemattpocock/skills
A step-by-step debug loop for finding and fixing hard bugs
Systematic Debuggingobra/superpowers
Find the root cause of every bug before attempting any fix to save time
Safe Debuglllllllama/rigorpilot-skills
Debug deep learning failures safely with conservative diagnosis and minimal patches
Firebase Crashlyticsfirebase/agent-skills
Set up crash reporting for your Android or iOS app with ease
Python Performance Optimizationwshobson/agents
Profile and optimize Python code to find and fix performance bottlenecks quickly