Automated summary
Provides standardized patterns for handling API errors, showing user-friendly messages, implementing retry logic, and using error boundaries in frontend applications.
Strengths
- Clear API error categorization by status code
- Includes React Error Boundary component pattern
- Covers both user-facing messages and debugging logs
- Retry logic for transient failures
Limitations
- Focused on React and TypeScript; may need adaptation for other frameworks
- Does not cover state management for errors (e.g., Redux, Zustand)
- Retry logic shown generically without exponential backoff specifics
When building or refactoring frontend error handling to ensure consistency and user-friendly experiences.
For simple static sites without API calls or complex error states.
Security analysis
SafeThe skill provides frontend error handling guidelines and code examples; no executable commands or destructive actions are present.
No concerns found
How this analysis is madeExamples
Given this fetch call, add error handling with retry logic for transient errors and proper error categorization.Create a React Error Boundary component that catches errors and displays a fallback UI, with logging to console.Transform this raw API error into a user-friendly message with different handling for 404, 500, and network errors.name: frontend-data-error-handling description: Standardized guidelines and patterns for Frontend Data Error Handling.
Frontend Data Error Handling
When to use this skill
- Handling API errors
- Showing error messages
- Implementing retry logic
- Error boundaries
Workflow
- [ ] Catch errors at API layer
- [ ] Show user-friendly messages
- [ ] Log errors for debugging
- [ ] Implement retry for transient errors
- [ ] Use error boundaries for crashes
Instructions
API Error Handling
try {
const data = await fetchUser(id);
return data;
} catch (error) {
if (error.response?.status === 404) {
throw new NotFoundError('User not found');
}
if (error.response?.status >= 500) {
throw new ServerError('Server error, please try again');
}
throw error;
}
React Error Boundary
class ErrorBoundary extends React.Component {
state = { hasError: false, error: null };
static getDerivedStateFromError(error) {
return { hasError: true, error };
}
componentDidCatch(error, errorInfo) {
console.error('Error:', error, errorInfo);
}
render() {
if (this.state.hasError) {
return <ErrorFallback error={this.state.error} />;
}
return this.props.children;
}
}
Resources
- Show friendly messages to users
- Log detailed errors for debugging
- Retry transient failures
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/frontend-error-handling-mm78no3v/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/frontend-error-handling-mm78no3v' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/frontend-error-handling-mm78no3v/download' --output '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md.part' && mv '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md.part' '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md' && test -s '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/frontend-data-error-handling' && cp -R '.skill-downloads/frontend-error-handling-mm78no3v' '.claude/skills/frontend-data-error-handling'Cursor
test -f '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md' && test -s '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/frontend-data-error-handling' && cp -R '.skill-downloads/frontend-error-handling-mm78no3v' '.cursor/skills/frontend-data-error-handling'Codex
test -f '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md' && test -s '.skill-downloads/frontend-error-handling-mm78no3v/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/frontend-data-error-handling' && cp -R '.skill-downloads/frontend-error-handling-mm78no3v' '.agents/skills/frontend-data-error-handling'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/frontend-error-handling-mm78no3v'openskills read 'frontend-error-handling-mm78no3v'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/frontend-error-handling-mm78no3v/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.