mandu-fs-routes

Map app/ folder files to Mandu URL routes for pages, APIs, and layouts.

46|4|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/konamgil/mandu --skill mandu-fs-routes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mandu-fs-routes
Source: https://github.com/konamgil/mandu/tree/main/packages/mcp/src/resources/skills/mandu-fs-routes
Command: npx skills add https://github.com/konamgil/mandu --skill mandu-fs-routes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File-system based routing automates turning the app/ folder structure into URL routes, reducing boilerplate and configuration overhead.

Core Features & Use Cases

  • Maps app/page.tsx, API route.ts, and layout.tsx to URL paths, supporting dynamic segments like [id] and [...slug]
  • Supports page routes, API routes, and shared layouts with conventional file names to ensure predictable routing
  • Use case: rapidly scaffold pages and APIs by mirroring the desired URL structure in the app/ directory.

Quick Start

Create an app/ folder with page.tsx, route.ts, and layout.tsx files to define your routes.

Frequently Asked Questions about mandu-fs-routes

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

FAQPage Schema
How does file-system based routing work for web applications?

File-system based routing maps your app/ folder structure to URL paths automatically, reducing configuration overhead. By placing files like page.tsx and route.ts in directories, you mirror your desired URL hierarchy to generate pages and API endpoints predictably.

How do I create dynamic routes and API endpoints using folder structures?

Create dynamic routes by using conventional files like page.tsx and route.ts within the app/ folder. Use bracketed folder names like [id] for single dynamic parameters or [...slug] for catch-all routes to map folder structures to dynamic URL paths.

Can I apply shared layouts across multiple pages using file-system routing?

Yes, you can apply shared layouts by adding a layout.tsx file to your app/ directory structure. This file wraps child page routes, ensuring consistent UI elements and standardized layout behavior across the corresponding URL segments.

What is the best way to standardize routing behavior across large web applications?

Standardize routing behavior using file-system based routing with strict naming conventions. Relying on fixed file names like page.tsx and frontmatter metadata standardizes page generation, API routes, and layouts predictably across the app/ folder.

Do I need to manually configure URL paths when using file-system based routing?

No, you do not need to manually configure URL paths. File-system based routing automatically maps the app/ folder structure to URL routes, eliminating boilerplate so you can rapidly scaffold pages and APIs by simply mirroring the desired URL structure in directories.