routing-patterns

Teach pattern-based routing concepts for modern web apps.

35|5|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Kinfe123/fm-skills --skill routing-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routing-patterns
Source: https://github.com/Kinfe123/fm-skills/tree/main/routing-patterns
Command: npx skills add https://github.com/Kinfe123/fm-skills --skill routing-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps architects and developers design robust routing strategies that map URLs to content across server and client boundaries, enabling predictable navigation, improved SEO, and resilient meta-framework configurations.

Core Features & Use Cases

  • Server-side routing concepts (URL-to-handler mapping, full HTML renders)
  • Client-side routing (history API, SPA navigation, hash routing)
  • File-based routing patterns and folder-structure conventions
  • Dynamic routes, catch-all and optional parameters, and nested layouts
  • Route guards, middleware, and prefetching strategies
  • Real-world scenarios: multi-layout apps, nested routes, and 404 handling

Quick Start

Outline a routing plan for a blog site with pages '/', '/about', '/blog/[slug]', and catch-all '/docs/*', including nested layouts and client-side vs server routing decisions.

Frequently Asked Questions about routing-patterns

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

FAQPage Schema
How do I design a routing strategy for a mix of SPA and MPA pages?

Design routing for SPA and MPA by mapping URLs to handlers across server and client boundaries, applying predictable navigation patterns to ensure consistent content mapping and resilient meta-framework configurations.

What's the best way to structure file-based routing with dynamic routes and nested layouts?

Structure file-based routing using folder-structure conventions that map to dynamic route parameters, catch-all segments, and nested layouts, ensuring consistent URL mapping across server-side and client-side environments.

How does middleware work with route guards and prefetching in modern web apps?

Middleware in modern web apps works by intercepting route guards and prefetching strategies, controlling navigation access and optimizing content loading before rendering routes across server-side or client-side routing environments.

Can I apply dynamic route parameters and catch-all routes in both server-side and client-side routing?

Yes, dynamic route parameters and catch-all routes like '/docs/*' apply across both server-side and client-side routing, enabling consistent URL-to-content mapping and flexible 404 handling within meta-framework configurations.

How do I handle 404 errors and multi-layout apps using nested routes?

Handle 404 errors and multi-layout apps by configuring nested routes with catch-all parameters, allowing predictable fallback rendering and distinct layout mapping across server-side and client-side navigation boundaries.