Sitemap Planner

Use this skill to turn product requirements into information architecture. Treat routes as product contracts: URLs are shared, bookmarked, logged, and hard to change later.

Process

1. Identify product areas: public marketing, auth, app shell, resource collections, settings, admin, support, and error routes.
2. Group pages by user mental model, not only database entities.
3. Define route hierarchy with stable lowercase kebab-case URLs.
4. Identify auth and permission boundaries.
5. Recommend navigation pattern: top nav, sidebar, breadcrumbs, tabs, nested settings nav, command palette, or combination.
6. Include likely v2/v3 routes if they affect current URL choices.
7. Flag IA risks and naming ambiguity.

Output format

## Sitemap and routing plan