Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/site-architecture
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what page
Passed 18 of 23 test cases with the skill, and 13 of 23 without it.
and 8 more in the full report
6 fixed12 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are launching a new B2B SaaS platform for team collaboration and need a complete site architecture plan. Please produce the full architectural breakdown including an ASCII text tree of the page hierarchy with sample path slugs, a visual Mermaid flowchart mapping page relationships across header and footer zones, a URL mapping table listing page names, paths, parents, and navigation locations, a navigation design spec covering top navigation, footer groupings, and breadcrumbs, and an internal linking strategy with hub-and-spoke models.
| Checked | Without skill | With skill |
|---|---|---|
| Includes an Internal Linking Plan section as a distinct deliverable. | Missed | Passed |
| Uses a flat feature URL structure formatted like `/features/{name}`. | Missed | Passed |
| Includes a Priority column in the URL mapping table. | Missed | Passed |
| Uses `graph TD` syntax in the Mermaid diagram. | Passed | Passed |
The instructions your model reads when the skill loads.
--------|--------------|--------------|-------------|
| SaaS marketing | 2-3 levels | Home, Features, Pricing, Blog, Docs | /features/name, /blog/slug |
| Content/blog | 2-3 levels | Home, Blog, Categories, About | /blog/slug, /category/slug |
| E-commerce | 3-4 levels | Home, Categories, Products, Cart | /category/subcategory/product |
| Documentation | 3-4 levels | Home, Guides, API Reference | /docs/section/page |
| Hybrid SaaS+content | 3-4 levels | Home, Product, Blog, Resources, Docs | /product/feature, /blog/slug |
| Small business | 1-2 levels | Home, Services, About, Contact | /services/name |
For full page hierarchy templates: See references/site-type-templates.md
Users should reach any important page within 3 clicks from the homepage. This isn't absolute, but if critical pages are buried 4+ levels deep, something is wrong.
| Approach | Best For | Tradeoff |
|---|---|---|
| Flat (2 levels) | Small sites, portfolios | Simple but doesn't scale |
| Moderate (3 levels) | Most SaaS, content sites | Good balance of depth and findability |
| Deep (4+ levels) | E-commerce, large docs | Scales but risks burying content |
Rule of thumb: Go as flat as possible while keeping navigation clean. If a nav dropdown has 20+ items, add a level of hierarchy.
| Level | What It Is | Example |
|---|---|---|
| L0 | Homepage | / |
| L1 | Primary sections | /features, /blog, /pricing |
| L2 | Section pages | /features/analytics, /blog/seo-guide |
| L3+ | Detail pages | /docs/api/authentication |
Use this format for page hierarchies:
test cases passed, vs 13 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.