Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

global-error-handling

Estrellas0

Forks0

Actualizado7 de febrero de 2026 a las 10:02

Implement robust error handling with user-friendly messages, specific exception types, centralized error boundaries, graceful degradation, retry strategies, and proper resource cleanup. Use this skill when handling errors in backend or frontend code; when providing clear, actionable error messages to users; when validating input and failing fast with explicit error messages; when using specific exception types instead of generic errors; when implementing centralized error handling at appropriate boundaries; when designing systems to degrade gracefully when services fail; when implementing retry strategies with exponential backoff for external service calls; when cleaning up resources in finally blocks or equivalent mechanisms; when handling errors in React components with error boundaries; when logging errors for debugging and monitoring; or when structuring error handling across the application architecture.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

shynlee04

shynlee04/idumb-v2

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name

Global Error Handling

description

Global Error Handling

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global error handling.

When to use this skill

When providing clear, actionable error messages to users without exposing technical details
When validating input and failing fast with explicit error messages
When using specific exception types instead of generic errors
When implementing centralized error handling at appropriate boundaries
When designing systems to degrade gracefully when services fail
When implementing retry strategies with exponential backoff for external services
When cleaning up resources in finally blocks or equivalent mechanisms
When handling errors in React components with error boundaries
When logging errors for debugging and monitoring descriptions

Instructions

For details, refer to the information provided in this file: global error handling

Más de este repositorio

mismo repositorio

agent-browser

shynlee04/idumb-v2

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

2026-02-070

gap-analysis

shynlee04/idumb-v2

Systematically identify what's missing, unknown, or needs investigation before making changes or decisions. Use proactively when proposing features, implementing changes, or making technical decisions to ensure all critical areas are covered. This skill catches overlooked dependencies, edge cases, and integration points before they become problems. Examples: - "Implement user authentication" → trigger gap analysis (what's the current auth system?) - "Add caching to API" → trigger gap analysis (what caching infrastructure exists?) - "Migrate to TypeScript" → trigger gap analysis (what's the build pipeline?) - "Refactor this module" → trigger gap analysis (what depends on this module?) - "Add new API endpoint" → trigger gap analysis (what endpoints exist, what patterns?)

2026-02-070

intent-clarification

shynlee04/idumb-v2

Detect ambiguous or underspecified research requests and guide through structured clarification questions before executing any research. Use proactively when user requests are vague, lack specificity, missing context, or have unclear goals. This skill prevents wasted research by ensuring intent is crystal clear before any web searches, file reads, or data gathering. Examples: - "Research the codebase" → ❌ Too vague, trigger clarification - "Why is this slow?" → ❌ Missing context (what is "this"?), trigger clarification - "Add a feature" → ❌ Not research, this is implementation - "Investigate authentication flow" → ❌ What specifically about it? Trigger clarification - "Compare React and Vue" → ✅ Specific enough, but still validate dimensions

2026-02-070

multi-aspect-assessment

shynlee04/idumb-v2

Evaluate requests, proposals, or decisions from multiple dimensions (technical, business, UX, security, performance, maintainability, etc.) to ensure holistic understanding before proceeding. Use proactively when making technical decisions, choosing solutions, or proposing changes. This skill prevents single-minded thinking and uncovers trade-offs, risks, and opportunities across all relevant aspects. Examples: - "Use Redis for caching" → assess multiple aspects (performance, cost, complexity, ops) - "Add AI to our app" → assess aspects (technical feasibility, user experience, data privacy) - "Refactor to microservices" → assess aspects (benefits, costs, migration complexity, team readiness) - "Implement authentication" → assess aspects (security, UX, integration effort, maintenance) - "Switch to React 19" → assess aspects (benefits, migration cost, breaking changes, learning curve)

2026-02-070

opencode-primitive-selector

shynlee04/idumb-v2

Choose the right OpenCode primitive (Command, Skill, Tool, Prompt, CustomTool, Plugin hook) for a given task or workflow. Use proactively when deciding which OpenCode capability to use, or when trying to understand what's available. This skill maps research and development needs to appropriate OpenCode mechanisms, ensuring optimal use of the platform's capabilities. Examples: - "How do I search the codebase?" → select tool (read/grep) - "I need a reusable workflow for feature development" → select command - "How do I intercept file writes?" → select plugin hook - "What primitive should I use for systematic debugging?" → select skill - "I need a custom tool for X" → select CustomTool (if innate tools insufficient)

2026-02-070

research-workflow-planner

shynlee04/idumb-v2

Create structured, executable research plans with clear phases, checkpoints, and validation criteria. Use proactively when research intent is clear but execution plan is missing. This skill transforms research goals into actionable workflows with defined deliverables, time estimates, and success metrics, ensuring research is systematic and produces useful outputs. Examples: - "Research how to add OAuth" (intent clear, need plan) → trigger workflow planner - "Investigate performance bottlenecks" (intent clear, need plan) → trigger workflow planner - "Analyze codebase architecture" (intent clear, need plan) → trigger workflow planner - "Find best practices for X" (intent clear, need plan) → trigger workflow planner - "Compare technology options" (intent clear, need plan) → trigger workflow planner

2026-02-070

name

Global Error Handling

description

Global Error Handling

This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global error handling.

When to use this skill

When providing clear, actionable error messages to users without exposing technical details
When validating input and failing fast with explicit error messages
When using specific exception types instead of generic errors
When implementing centralized error handling at appropriate boundaries
When designing systems to degrade gracefully when services fail
When implementing retry strategies with exponential backoff for external services
When cleaning up resources in finally blocks or equivalent mechanisms
When handling errors in React components with error boundaries
When logging errors for debugging and monitoring descriptions

Instructions

For details, refer to the information provided in this file: global error handling