routing

Coding rules for a file-based routing system in a Vite application. File-based routing means that folders and filenames determine which URLs the application serves.

In plain words
What is it for?
It helps add and organise synchronous and asynchronous routes, create layout files, and map page files to application URLs.
Why use it?
It removes guesswork about route filenames, lazy loading, synchronous pages, and layouts that wrap child pages.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/innei-template/smart-webapp-template/routing
Clone the repo
git clone --depth 1 https://github.com/innei-template/smart-webapp-template

Made for: Cursor.

Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 476 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00005 $0.00476
Opus 5 $0.00003 $0.00238
Sonnet 5 $0.00001 $0.00095
Haiku 4.5 $0.00001 $0.00048

Measured 2d ago against content hash 4c96ab32638e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

routing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/routing.mdc · 69 lines

What it actually says

File-Based Routing System

This project uses vite-plugin-route-builder for file-based routing. Follow these patterns:

Route Types

Sync Routes: .sync.tsx files

  • Synchronous routes without code splitting
  • Used for critical pages that should load immediately
  • Example: src/pages/(main)/index.sync.tsx becomes root route

Async Routes: .tsx files (without .sync)

  • Asynchronous routes with lazy loading and code splitting
  • Used for non-critical pages to optimize initial bundle size
  • Example: src/pages/about.tsx becomes /about route

Layout System

Layout Files: layout.tsx files serve as layout containers

  • Use <Outlet /> within layout components to render child routes
  • Layouts automatically wrap their corresponding route segments
  • Example: src/pages/(main)/layout.tsx wraps all routes in the (main) group

Route Structure Examples

// Sync route - no code splitting
// File: src/pages/(main)/index.sync.tsx
export default function HomePage() {
  return <div>Home Page</div>
}

// Async route - with code splitting
// File: src/pages/dashboard.tsx
export default function DashboardPage() {
  return <div>Dashboard</div>
}

// Layout component
// File: src/pages/(main)/layout.tsx
import { Outlet } from 'react-router'

export default function MainLayout() {
  return (
    <div className="min-h-screen">
      <nav>Navigation</nav>
      <main>
        <Outlet />
      </main>
    </div>
  )
}

Generated Routes

  • Routes are auto-generated in src/generated-routes.ts
  • DO NOT EDIT the generated routes file manually
  • The routing plugin handles all route generation automatically

Documentation Reference

For detailed usage, advanced patterns, and configuration options, always refer to the official documentation: https://github.com/Innei/vite-plugin-route-builder

Important: When encountering unclear routing patterns or advanced use cases, consult the official documentation before implementation.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 69 lines · 5 tokens per session scan A 4c96ab32638e

Subscribe to this mod's changes

routing is a cursor rule published in the GitHub repository innei-template/smart-webapp-template (142 stars, last pushed 6d ago), licensed MIT. It adds 5 tokens to every session and 476 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.