magnus-update-nav

Update Magnus site navigation and footer across all pages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ssu96ld/magnus-claude-plugins --skill magnus-update-nav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magnus-update-nav
Source: https://github.com/ssu96ld/magnus-claude-plugins/tree/main/plugins/magnus-site/skills/magnus-update-nav
Command: npx skills add https://github.com/ssu96ld/magnus-claude-plugins --skill magnus-update-nav

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update the Magnus site navigation and footer across all pages to reflect new menu items, labels, and structure.

Core Features & Use Cases

  • Edit Nav.astro and Footer.astro to add, remove, rename, or reorder top-level items and adjust submenus.
  • Rewire activeLink references across src/pages/ so all pages stay consistent with navigation changes.
  • Preview changes safely and secure approvals before publish.

Quick Start

Edit the navigation structure and wiring, then obtain approval before publishing the changes.

Frequently Asked Questions about magnus-update-nav

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update site navigation and footer across all pages consistently?

To update site navigation consistently, edit Nav.astro and Footer.astro to add, remove, or reorder items, then rewire activeLink references across all page routes to ensure structural alignment. This guarantees every page reflects the new menu architecture safely.

What is activeLink wiring and why does it break when I reorder navigation menus?

activeLink wiring tracks the current page route to highlight the active navigation item. Reordering menus or renaming routes breaks this mapping, requiring an audit of all activeLink usages across src/pages/ to restore consistent active state highlighting.

How to add submenus to a website architecture without breaking existing page routes?

To add submenus without breaking routes, edit the navigation structure to nest new items, then audit and update all activeLink references across affected pages to ensure the route mapping remains completely consistent with the new architecture.

Can I preview navigation changes safely before publishing to the live website?

Yes, you can preview navigation changes safely before publishing. The workflow requires auditing all activeLink usages, updating affected routes, and securing an explicit approval lock before any navigation or footer modifications are published.

Does updating the footer structure require rewiring activeLink references across pages?

Updating the footer structure focuses on layout and links, but if changes affect route mappings, activeLink wiring must be audited. Ensuring all activeLink usages across src/pages/ remain consistent prevents navigation highlighting errors.