菜单
Use when designing error pages (4xx, 5xx, app errors, form errors). Covers tone, what to include (clear cause + next action), and the difference between API errors and user-facing errors.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/x3allamerican/design-skills-fleetsafety --skill error-page-design命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when designing 404 pages and the broader empty-state pattern library. Covers tone, illustration, search recovery, and the difference between 'no data yet' and 'this URL doesn't exist'.
Use when designing A/B tests. Covers hypothesis-driven testing, sample-size calculation, the test-design template, and the cultural rituals that make testing productive.
Use when shipping any user-facing UI. Covers the non-negotiable accessibility baseline: contrast, focus states, semantic HTML, keyboard navigation, screen-reader support, motion preferences. The minimum to avoid embarrassment and ADA risk.
基于 SOC 职业分类
正在显示 SKILL.md
| name | error-page-design |
| description | Use when designing error pages (4xx, 5xx, app errors, form errors). Covers tone, what to include (clear cause + next action), and the difference between API errors and user-facing errors. |
Errors are friction. Good error UX reduces the friction; bad UX amplifies it.
Headline naming the problem (not just '500 Internal Server Error'). 1-paragraph explanation. Suggested action. Optional: technical details collapsed.
Calm, specific, not performative. NEVER 'Oops!' or 'Yikes!' — sounds infantile.
Always tell user what to do next: 'Refresh', 'Go to dashboard', 'Contact support', 'Try again in a few minutes'.
Show the HTTP status code in small text (helpful for support). Don't lead with it.
Friendly headline. Search bar. Links to most-visited pages. Image / illustration if brand allows.
Raw stack traces. 'Something went wrong.' (what? what now?). No way back. 'Oops! Hold on while we fix this.' performative tone. Error pages that look like the rest of the product is broken too.
Applied in the X3 Compass build via the relevant pages and components.