Navigation and 404 repair
Make menus, old links, and missing pages useful and predictable.
Customize the recipe
Prompt preview
# Navigation and 404 repair Make menus, old links, and missing pages useful and predictable. ## Deliverable A navigation patch and validated missing-route and redirect behavior. ## Stack and visual direction - Recommended starting stack: Use the existing stack, browser tooling and the project's test commands. Capture before-and-after evidence. - Minimalism: Use deliberate spacing, a compact palette and a clear typographic hierarchy. Retain the labels, feedback and affordances people need to act. Use this direction for any new or revised UI within the agreed patch scope. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [Web Design Guidelines](https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines) (Skill) — Review frontend UI against usability and accessibility guidance. Access to the current upstream guidelines for the skill's full review. Fallback: Perform the recipe's keyboard, focus, responsive and feedback checks manually. - [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure. [Official setup](https://nextjs.org/docs/app/getting-started/installation). - [Lychee](https://github.com/lycheeverse/lychee) (Repository) — Check internal and external links and make transient failures distinguishable. - [Playwright Test](https://github.com/microsoft/playwright) (Repository) — Automate repeatable browser journeys using visible roles and assertions. Playwright-managed browser binaries. [Official setup](https://playwright.dev/docs/intro). ## Workflow 1. Map desktop and mobile navigation, footer destinations and known route changes. Repair dead or unused navigation, add redirects with clear replacements, and build a useful missing-page path. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] A missing address returns the correct HTTP status and a working way back. - [ ] The compact menu supports opening, choosing and dismissal by keyboard. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Capture a reproducible baseline, validate the changed flow afterward, and report evidence and any findings still open.
Recipe resources
Source, setup, and compatibility details.
Web Design Guidelines
Review frontend UI against usability and accessibility guidance.
Access to the current upstream guidelines for the skill's full review.
License · MIT
Next.js
Use App Router conventions, server rendering, metadata and accessible route structure.
License · MIT
Setup guide for Next.jsLychee
Check internal and external links and make transient failures distinguishable.
License · Apache-2.0 or MIT
Playwright Test
Automate repeatable browser journeys using visible roles and assertions.
Playwright-managed browser binaries.
License · Apache-2.0
Setup guide for Playwright TestPlaywright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLI