Error Handling Patterns
Robust error handling patterns for TypeScript, Python and Go: typed errors, retries, circuit breakers, and user-facing messages that never leak internals.
- What
- Robust error handling patterns for TypeScript, Python and Go: typed errors, retries, circuit breakers, and user-facing messages that never leak internals.
- Cost
- Free
- Needs
- Use "Error Handling Patterns" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: consistent, robust error handling patterns for production applications in TypeScript, Python and Go. Five core principles anchor everything: fail fast and loudly (surface errors at the boundary where they occur, never bury them); typed errors over string messages (errors are first-class values with structure, e.g. an AppError hierarchy with code and statusCode in TypeScript); user messages are not developer messages (friendly text for users, full context logged server-side); never swallow errors silently (every catch block must handle, re-throw or log); and errors are part of your API contract (document every error code a client may receive). Covers designing error types and exception hierarchies, retry logic with backoff and circuit breakers for unreliable dependencies, reviewing API endpoints for missing handling, user-facing failure messages, and debugging cascading failures or silent error swallowing. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: these are patterns to adapt to your stack, not a linter; some teams will disagree on details (exceptions vs result types), pick one convention and hold it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Error Handling Patterns" with your Muse. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/error-handling/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Apply the error handling patterns to [module/service] in [TypeScript/Python/Go]" or "Review [endpoint/module] for missing error handling." 3. Work through the five principles with Muse: typed errors first, then retries and circuit breakers for external calls, then user-facing messages. Tip: start new modules by defining the error hierarchy before writing happy-path code; retrofitting errors is where silent swallowing creeps in. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste real secrets or customer data when asking Muse to review error paths.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.