Frontend Error Handling
Use when the user asks about React error boundaries, Vue errorHandler, Angular ErrorHandler, svelte:boundary, fallback UI, retry and recovery, unhandled promise rejections or reporting frontend errors to Sentry. Produces layered error boundaries and user-facing recovery. Not for form validation messages (use frontend-form-handling).
Install
npx skills add j4flmao/agent-skills --skill frontend-error-handlinggit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/frontend/universal/error-handling ~/.claude/skills/frontend-error-handlingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Frontend Error Handling ## Purpose Catch, report, and recover from frontend errors without crashing the entire app. Error boundaries isolate failures. Users always see a functional fallback UI. Every error is reported to the monitoring service with context for debugging. ## Agent Protocol ### Trigger Exact phrases: "error handling", "error boundary", "error recovery", "graceful degradation", "fallback UI", "error reporting", "error logging", "crash recovery", "error state", "retry pattern", "error fallback". ### Input Context - Framework (React, Vue, Angular, Svelte) - Current error handling (if any) — try/catch patterns, boundaries - Error reporting service (Sentry, Datadog RUM, LogRocket, custom) - Critical vs non-critical components that need boundaries ### Output Artifact Error boundary implementation, error reporting integration, fallback UI components, recovery patterns. ### Response Format ``` ## Strategy <boundary-locations, reporting-service, fallback-hierarchy> ## Implementation <error-boundary-code, error-reporting-setup> ## Recovery <retry-patterns, fallback-ui, reset-mechanism> — Compression footer: frontend-error-handling/v1 | boundaries: <count> | reporter: <service> | fallback: <full|partial> ``` No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. ### Completion Criteria - [ ] Error boundaries wrap: root layout, each major route, each standalone widget
Details
- Skill name
frontend-error-handling- Repository
- j4flmao/agent-skills
- Path
skills/frontend/universal/error-handling/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Frontend Error Handling skill do?
Use when the user asks about React error boundaries, Vue errorHandler, Angular ErrorHandler, svelte:boundary, fallback UI, retry and recovery, unhandled promise rejections or reporting frontend errors to Sentry. Produces layered error boundaries and user-facing recovery. Not for form validation messages (use frontend-form-handling).
How do I install the Frontend Error Handling skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill frontend-error-handling. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Frontend Error Handling popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Frontend Feature Flags
45j4flmao/agent-skills
Use when the user asks about frontend feature flags, LaunchDarkly, OpenFeature, Unleash, Flagsmith, gradual rollout, kill switches or A/B test assignment in the UI. Produces a typed, provider-agnostic flag layer without flicker. Not for server-side flag evaluation (use backend-feature-flags) or experiment statistics (use product-ab-testing).
Frontend Design System
45j4flmao/agent-skills
Use when the user asks to build a component library, define primitive, semantic and component design tokens as CSS variables, design component APIs with CVA variants, or wire dark mode through semantic tokens. Produces coded token layers and component library structure. Not for Figma variables and token pipeline governance (use design-systems).
Frontend Form Handling
45j4flmao/agent-skills
Use when the user asks to validate a signup form with react-hook-form and Zod, Formik, TanStack Form, VeeValidate, field arrays, controlled vs uncontrolled inputs, form errors or submission UX. Produces schema-validated, accessible forms. Not for server-side validation (use backend-api-design) or general typing helpers (use frontend-typescript-patterns).
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.