Skip to content

Guide · Agent skill

How to use the Site Architecture Planner agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Site Architecture Planner is an agent skill (named site-architecture) that turns your AI agent into an information architecture consultant for your website. It is useful for marketers, founders and designers who need to decide which pages a site should have, how they connect, and how the navigation and URLs should be laid out. After this guide you will know what the skill does, how to install it, how to trigger it with plain requests, and what to check before you rely on its output.

Site Architecture Plannercoreyhaines31/marketingskills · MIT

Quick start

  1. 1Download the ZIP. Get the site-architecture ZIP file from the skill's page in the agents directory.
  2. 2Install the skill. Unzip it into ~/.claude/skills/ for all projects, or into .claude/skills/ inside a project, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
  3. 3Add your context file (optional). Create .agents/product-marketing.md or .claude/product-marketing.md with your business, audiences and goals so the agent asks fewer questions.
  4. 4Describe your planning task. Ask in plain language, for example: 'Plan the page hierarchy and navigation for my SaaS marketing site.'
  5. 5Answer the follow-up questions. The agent asks about your business, current site, site type and content. Answer as fully as you can.
  6. 6Review the proposal. Check the page tree, navigation and URL patterns against your goals, then refine them with follow-up requests.

What the Site Architecture skill makes the agent do

When the skill is installed, the agent works as an information architecture consultant. It first asks about your business, your audiences, your current site and your goals. It then proposes a page hierarchy, a navigation layout, URL patterns and an internal linking plan.

The skill uses templates for common site types: SaaS marketing, content/blog, e-commerce, documentation, hybrid SaaS plus content, and small business. It presents page hierarchies either as text trees or as Mermaid diagrams. It also points to reference guides on choosing a platform, migrating a site, and navigation patterns.

  • Page hierarchy: which sections and pages the site needs, and how deep they sit
  • Navigation: header, dropdown, footer, breadcrumb and contextual link layout
  • URL structure: patterns such as /features/name or /blog/slug
  • Internal linking: how pages should connect to each other
  • Platform and migration guidance when you are choosing a builder or moving an existing site

Install the Site Architecture skill

Download the ZIP file for the skill from the agents directory page. You have two ways to install it.

For Claude Code, unzip the download into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want the skill available only in that project. The skill's main file is SKILL.md, and it sits alongside a references folder and an evals folder.

If you use the Claude apps, you can upload the ZIP instead. Open Settings, go to Capabilities, then Skills, and upload it there.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ inside your project folder
  • Claude apps: Settings → Capabilities → Skills
~/.claude/skills/ site-architecture/ SKILL.md references/ evals/

Trigger the skill with natural requests

You do not need a special command. The skill is meant to activate when you describe a planning task in ordinary language. Its description lists trigger phrases such as 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, and how should I organize my site.

Be specific about your situation. The agent asks follow-up questions anyway, so a clear first message saves a round trip.

  • 'What pages does a SaaS marketing site need, and how should they link?'
  • 'Draft a visual sitemap for my new small business website.'
  • 'How should I organize my site navigation? It is currently a mess of 30 links.'
  • 'I want to add a blog to my existing site. Where should it sit in the structure?'
  • 'Which website builder should I use for a documentation site?'

Give the agent the context it needs

The skill first checks for existing product marketing context. If a file named .agents/product-marketing.md exists, or .claude/product-marketing.md, or the older product-marketing-context.md, the agent reads it before asking questions. Keeping that file current means you answer fewer questions.

If you have no such file, the agent asks for the following: what the company does, the primary audiences, the top three goals for the site, whether this is a new or restructured site, which URLs must be preserved for redirects, the platform in use, the site type, and a rough count of existing or planned pages.

  • Business description and primary audiences
  • Top three goals: conversions, SEO traffic, education or support
  • New site or restructure, and what is currently broken
  • Existing URLs that must be preserved
  • Current platform and whether a change is possible
  • Site type and the most important pages

Read and use the output

The agent's proposal is a set of recommendations. The skill applies rules of thumb such as the 3-click rule, which says important pages should be reachable within three clicks from the homepage, and a limit of 4 to 7 items in the primary header navigation.

Ask the agent to show the hierarchy as a text tree for quick review, or as a Mermaid diagram when you need to present complex relationships or navigation zones. Then check each proposed page against your real business goals before building anything.

  • Use the text tree for quick drafts and simple structures
  • Use Mermaid for presentations, nav zones and linking patterns
  • Check every page against a business goal before you build it
  • Confirm that any URLs you must keep are carried over or redirected
Homepage (/) ├── Features (/features) │ ├── Analytics (/features/analytics) │ └── Automation (/features/automation) ├── Pricing (/pricing) ├── Blog (/blog) └── Contact (/contact)

Know what the skill does not cover

The skill is for planning the structure of a site. It explicitly excludes XML sitemaps, which it describes as technical SEO. For those, and for SEO audits, the description points to the seo-audit skill. For structured data it points to the schema skill.

The skill gives planning guidance, not verified implementation steps. It does not handle large-scale migrations that require live redirect mapping. Treat its output as general best-practice advice that you review yourself.

  • Not for XML sitemaps: see seo-audit
  • Not for SEO audits: see seo-audit
  • Not for structured data: see schema
  • Not for large-scale migrations with live redirect mapping

What people use it for

  • Planning the pages and navigation for a new SaaS marketing site with features, pricing, blog and docs
  • Restructuring a confusing small business website so visitors can find services and contact details
  • Deciding where a new blog should sit inside an existing site and how its categories should link
  • Creating a visual sitemap for a designer before building a site
  • Choosing URL patterns for a documentation section, such as /docs/section/page

Frequently asked questions

How do I install the site architecture agent skill?

Download the ZIP from the skill's page in the directory. Unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.

Does the site architecture skill need anything else installed?

The skill lists no requirements. It does not run scripts and does not use the network, according to its listing. You only need a compatible agent environment where skills can be installed.

Is the Site Architecture Planner free?

The skill is published under the MIT licence, as stated on this page. Check the licence file in the source repository for the full terms.

Can this skill create an XML sitemap for my site?

No. The skill says XML sitemaps are technical SEO and should be handled by the seo-audit skill. This skill plans which pages exist and how they link.

What is the difference between this skill and the seo-audit skill?

This skill plans page hierarchy, navigation, URL structure and internal linking before you build. The seo-audit skill covers SEO audits of an existing site, and the schema skill covers structured data.

Why doesn't the agent use my existing context file?

The skill looks for .agents/product-marketing.md, .claude/product-marketing.md, or the older product-marketing-context.md. If your file has a different name or location, move it to one of those paths, or paste the key details into your request.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you are planning a new website, restructuring a confusing one, or need a sitemap and navigation plan before a designer or developer starts. It gives a clear, structured starting point, but its output is general best-practice guidance, so review it against your own business. If you need XML sitemaps, SEO audits, structured data, or a verified plan for a large migration with live redirects, use the seo-audit or schema skills or a specialist instead.

Download the skill

Find exactly what
you're looking for