epic-routing

File-based routing in an Epic Stack application is configured using react-router-auto-routes to automatically map URLs to components. This skill applies conventions for nested layouts and route groups, ensuring YAML frontmatter defines route name and description metadata.

Resource routes in React Router are API-like endpoints created using loaders and actions without rendering a UI component. You should use them when you need to handle data fetching or form submissions server-side while keeping the routing logic within your file-based route structure.

You organize related pages without changing the URL by using Route Groups within your file-based routing structure. This approach applies shared nested layouts to specific component groups while maintaining a clean browser path for the end user.

Yes, Epic Stack routing enforces YAML frontmatter for defining route name and description. This metadata convention is required alongside the file-based routing setup to properly identify and document the purpose of each route within the application architecture.

Loaders and actions are added to nested routes by defining them within the route module using React Router conventions. This skill demonstrates routing patterns that integrate data fetching and mutations directly into the file-based route components for seamless nested layout rendering.