Explores a web application's codebase, documentation, or live site to discover all navigable routes and produce a routes.csv file for Agentic Trust navigation. Use when the user asks to build, generate, create, or update a routes.csv, route map, sitemap, or navigation inventory for a client application.
Generate a routes.csv for a client application by exploring its documentation,
source code, or live UI. The CSV is uploaded to Agentic Trust's Navigation feature
so the agent can direct users to the right pages.
name,path,description,parameters
dashboard_home,/dashboard,Main dashboard overview,
user_detail,/users/:userId,Individual user profile,userId:string
| Column | Rules |
|---|---|
name | snake_case, unique, descriptive (e.g. settings_general, test_case_detail) |
path | URL path with :param placeholders for dynamic segments |
description | One-line plain-English summary of what the page shows or does |
parameters | Semi-colon-separated paramName:type pairs; empty if no dynamic segments |
name,path,description,parametersLook for clients/<ClientName>/ in the workspace. If it doesn't exist yet, ask the
user for the client name and create the folder.
Sources are listed from highest to lowest signal. Use every source you can find; cross-reference them against each other to build the most complete list.
docs.md)Read clients/<ClientName>/docs.md. Scan for:
/dashboard, /settings/..., /td/:workspaceId/cases)workflows/*.md)Read every workflow markdown in clients/<ClientName>/workflows/. Each workflow
typically references one or more routes in its steps (e.g. "Navigate to /td/:workspaceId/plans").
Extract every route mentioned and merge them into your list.
Search the workspace for the client's frontend source:
app/**/page.tsx files — each directory maps to a route<Route path=, createBrowserRouter, route config arraysroutes: arrays in router config filesRouterModule.forRoot, Routes type arraysIf the user provides a URL or the app is running locally:
:paramName placeholders)If a routes.csv already exists, read it as a baseline. Preserve existing entries
unless they are clearly stale, and append newly discovered routes.
name to each route following snake_case namingWrite the final CSV to clients/<ClientName>/routes.csv.
After writing, re-read the file and verify:
name,path,description,parametersname is uniquepath starts with /:paramName syntax:param placeholders in the pathReport the total route count and any issues found.
See these existing routes.csv files for format conventions:
clients/ContextQA/routes.csv — medium-complexity SPAclients/auth0/routes.csv — large enterprise dashboard with nested routesstring./#/path), strip the # and record just the path portion.