Error handling
Skill amadeus-dlc/amadeus/amadeus/spaces/default/knowledge/amadeus-shared/software-design/error-handling
Agent skills, templates, examples, validators, and docs for operating Amadeus DLC, a lifecycle contract for AI driven software development.
npx -y skills add amadeus-dlc/amadeus --skill error-handlingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when designing or reviewing error handling across domain logic, application services, and infrastructure. Uses recoverability to choose typed errors, Result/Either, exceptions, retries, and logging. Trigger for improving error handling, Result types, exception design, recoverable errors, domain errors, or error-handling refactors.
SKILL.md
1.6 KB, as published. Nobody here has run it
Error Handling
Choose error mechanisms by recoverability and caller responsibility.
Workflow
-
Classify each error as domain, validation, application, infrastructure, programming defect, or fatal system condition.
-
Use typed
Result/Either-style returns for recoverable domain and validation errors. -
Use exceptions or panics for defects and truly exceptional infrastructure failures when callers cannot make a local decision.
-
Preserve causal context without leaking secrets.
-
Put retry, timeout, and circuit-breaker policy at integration boundaries.
Rules
-
Domain errors should be explicit in function signatures where the language supports it.
-
Do not use exceptions for ordinary business branching.
-
Log once at the boundary that handles or reports the error.
-
Convert low-level errors into application-facing errors at layer boundaries.
Reference
Read references/guidelines.md for detailed patterns.
Detailed Reference
For non-trivial implementation, review, or refactoring work, read references/details.md before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.
Output
Return the error taxonomy, mechanism choices, API changes, and tests.