Error page design
Skill Dragoon0x/everything-design-taste/skills/error-page-design
Error pages (404, 500, 403), error states, and graceful failure design.From its SKILL.md
npx -y skills add Dragoon0x/everything-design-taste --skill error-page-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 239 tokens by cl100k_base, as published. Nobody here has run it
Error Page Design
Error Page Hierarchy
404 — Not Found
- Acknowledge the error clearly: "This page doesn't exist."
- Offer: Search bar, popular pages, homepage link.
- Don't blame the user.
- Optional: brand-appropriate illustration.
500 — Server Error
- Acknowledge without technical jargon: "Something went wrong on our end."
- Offer: Retry button, status page link, support contact.
- Log the error automatically.
- Don't say "We're working on it" unless you actually are.
403 — Forbidden
- Explain why: "You don't have permission to view this page."
- Offer: Login link, request access button, contact admin.
Offline
- Detect offline state.
- Show cached content if available.
- "You're offline. Some features aren't available."
- Auto-retry when connection returns.
Principles
- Every error needs: What happened + What to do next.
- Use the brand voice. Error pages are touchpoints.
- Never show stack traces or error codes to users.
- Include a way to report the issue.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.