Create and map ZerospinError instances for structured error handling in Effect-based code.
npx skills add https://github.com/morgs32/skills --skill zerospin-error
Please help me install this Agent Skill. Skill: zerospin-error Source: https://github.com/morgs32/skills/tree/main/skills/zeropsin-error Command: npx skills add https://github.com/morgs32/skills --skill zerospin-error
Create and map ZerospinError instances to provide structured, stable error information for Effect-based code in zerospin. This helps when defining error codes/messages, wrapping causes, mapping/catching errors in Effects, or returning structured errors from Effect.gen/Effect.fn or promise boundaries.
Instantiate a ZerospinError with a stable code and message when an error occurs, e.g., new ZerospinError({ code: 'resource-not-found', message: 'Resource not found', cause: error }).
High-intent search queries and answers about installing and using this skill.
Handle structured errors in Effect TypeScript by creating ZerospinError instances with a stable code, human-readable message, and optional cause. This standardizes error handling across synchronous and asynchronous Effect.gen or Effect.fn flows.
Map native errors to structured errors in Effect by wrapping them as ZerospinError objects. Attach the original error as the cause and assign a stable code and message to maintain consistent error metadata throughout promise boundaries and generator flows.
Standardize error shapes across promise boundaries in Effect by returning ZerospinError objects. They enforce a stable code, human-readable message, attached cause, and optional metadata to ensure consistent error structures throughout your codebase.
ZerospinError supports HTTP status codes for API error handling by using the status field exclusively for HTTP-facing errors. This separates HTTP status mapping from the core error code and message metadata.
Add extra metadata to Effect errors in TypeScript by instantiating a ZerospinError with optional metadata fields. Alongside the required stable code, message, and cause, these optional fields provide additional context for debugging asynchronous flows.
You need structured error handling in Effect generator flows when returning errors from Effect.gen or Effect.fn. ZerospinError objects provide a consistent shape with stable codes and causes for mapping and catching errors across promise boundaries.
daeha76Assign and verify error codes for React application error messages.
aman-2709Design REST APIs with resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting.
dxosCompose typed effects with services, layers, and error handling in TypeScript.
paralleldriveCreate named, routable errors with consistent metadata in JavaScript/TypeScript.
