dragoon0x/everything-design-taste

error-page-design

Error pages (404, 500, 403), error states, and graceful failure design.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill error-page-design

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,203 B
  • docs SUMMARY.md 96 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

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

  1. Every error needs: What happened + What to do next.
  2. Use the brand voice. Error pages are touchpoints.
  3. Never show stack traces or error codes to users.
  4. Include a way to report the issue.