skillboardUpdated every 6 hours
skillboardWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
Guides 404 error page design for UX, conversion recovery, and brand consistency.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand voice, key pages, and Section 12 (Visual Identity).
Identify:
| Element | Purpose | |---------|---------| | Site navigation | Header/footer so users know they're still on your site | | Search | Help users find what they need | | Popular pages | Links to homepage, features, pricing, blog | | Similar URLs | Suggest corrections for common typos | | Avoid auto-redirect | Unless confident of user intent |
404 pages can drive conversions by:
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/404 · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/404"
cp -r "skills/pages/utility/404" ".claude/skills/404"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.