nextjs-route-visualizer

Map Next.js App Router routes and API endpoints from project context.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Techlemariam/IronForge --skill nextjs-route-visualizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextjs-route-visualizer
Source: https://github.com/Techlemariam/IronForge/tree/main/.agent/skills/nextjs-route-visualizer
Command: npx skills add https://github.com/Techlemariam/IronForge --skill nextjs-route-visualizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill visualizes the Next.js App Router structure and catalogs API endpoints to help developers understand and reason about large Next.js apps.

Core Features & Use Cases

  • Route tree visualization for pages, layouts, app routes, and API routes
  • API endpoint catalogue from src/app/api
  • Middleware mapping and detection of protected vs public routes
  • Cache strategy awareness (static, dynamic, ISR)

Quick Start

Generate a visual map of your Next.js project’s routing and API surface to begin exploration.

Frequently Asked Questions about nextjs-route-visualizer

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

FAQPage Schema
How do I visualize Next.js App Router structure for a large project?

To visualize Next.js App Router structure, you map the project context from src/app to generate a route tree. This reveals the architecture of pages, layouts, and API routes to help you reason about large applications.

How do I map API endpoints and middleware in a Next.js application?

You map API endpoints and middleware in a Next.js application by extracting and cataloging handlers from src/app/api. This process also maps middleware to detect protected versus public routes.

Can I detect cache strategies like static, dynamic, and ISR in my Next.js routes?

Yes, you can detect cache strategies for Next.js routes. The visualization process includes cache strategy awareness to identify whether routes are static, dynamic, or using Incremental Static Regeneration (ISR).

Does this route visualization approach work with Next.js projects using the src/app directory?

Yes, this route visualization approach works specifically with Next.js projects that use the src/app directory structure. It applies to apps built with Next.js that use src/app routes, middleware, and API handlers.

What is the best way to catalog API endpoints in Next.js App Router?

The best way to catalog API endpoints in the Next.js App Router is to extract them directly from the src/app/api directory. This catalogs your API surface and maps it alongside the application's route tree.