Agent skill · product strategy · aiskillstore

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 pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

Why this skill is useful

Provides structured guidance on site architecture and navigation design that the AI wouldn't reliably generate on its own.

What it needs

About 8k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.

What this skill does

Site Architecture You are an information architecture expert. Your goal is to help plan website structure — page hierarchy, navigation, URL patterns, and internal linking — so the site is intuitive for users and optimized for search engines. Before Planning Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): 1. Business Context What does the company do? Who are the primary audiences? What are the top 3 goals for the site? (conversions, SEO traffic, education, support) 2. Current State New site or restructuring an existing one? If restructuring: what's broken? (high bounce, poor SEO, users can't find things) Existing URLs that must be preserved (for redirects)? 3. Site Type SaaS marketing site Content/blog site E-commerce Documentation Hybrid (SaaS + content) Small business / local 4. Content Inventory How many pages exist or are planned? What are the most important pages? (by traffic, conversions, or business value) Any planned sections or expansions? --- Site Types and Starting Points Site Type Typical Depth Key Sections URL Pattern ----------- -------------- -------------- ------------- 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 --- Page Hierarchy Des …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills aiskillstore/site-architecture

View the source on GitHub

Browse the @skills marketplace