site-architecture

Audit and optimize information architecture and internal linking for Next.js sites.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Adrienenjalbert/flex-carrer-hub --skill site-architecture-adrienenjalbert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-architecture
Source: https://github.com/Adrienenjalbert/flex-carrer-hub/tree/main/.agents/skills/site-architecture
Command: npx skills add https://github.com/Adrienenjalbert/flex-carrer-hub --skill site-architecture-adrienenjalbert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits and defines the Career Hub's information architecture to ensure a coherent page hierarchy, intuitive navigation, and robust hub-and-spoke relationships that support scalable growth.

Core Features & Use Cases

  • Page hierarchy audits: verify pillar pages, detail pages, and spoke pages are reachable within the site's structure.
  • Navigation and linking validation: ensure consistent internal links, URL patterns, and breadcrumb integrity across the app.
  • Architecture guidance: provide recommended restructures to align with hub-and-spoke principles and improve SEO and discoverability.

Quick Start

Plan an architecture review of the Career Hub by outlining current pages, identifying gaps, and proposing a prioritized refactor plan.

Frequently Asked Questions about site-architecture

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

FAQPage Schema
How do I audit internal linking and navigation structure in a Next.js site?

To audit internal linking and navigation in a Next.js site, review your hub-and-spoke relationships to ensure pillar and detail pages are reachable. This process validates URL patterns and breadcrumb integrity to support scalable site architecture and SEO discoverability.

What is hub-and-spoke information architecture and when do I need it?

Hub-and-spoke information architecture organizes content around central pillar pages that link out to related detail pages. You need this structure when planning new page types or restructuring navigation to ensure coherent page hierarchy and improve content discoverability.

How do I validate URL patterns and frontmatter metadata across my site?

Validate URL patterns and frontmatter metadata by enforcing routing guidelines that check architecture rules across your Next.js application. This ensures consistent navigation, proper breadcrumb integrity, and that frontmatter-driven metadata aligns with the defined site structure.

Can I use this approach to plan new page types for a growing content hub?

Yes, you can plan new page types for a growing content hub by outlining current pages, identifying structural gaps, and proposing a prioritized refactor plan. This aligns new pages with hub-and-spoke principles to maintain coherent navigation during scalable growth.

What's the best way to restructure navigation without breaking existing URL patterns?

The best way to restructure navigation without breaking URL patterns is to audit existing hub-to-spoke links and validate routing guidelines first. This identifies unreachable pages and breadcrumb inconsistencies, allowing you to execute a prioritized refactor plan safely.

Why are some pillar pages unreachable in my site architecture?

Pillar pages become unreachable in your site architecture when internal links and hub-to-spoke relationships are inconsistent or missing. Auditing your page hierarchy reveals these gaps in navigation and linking, allowing you to restore reachability and structural coherence.