site-architecture
An agent skill by coreyhaines31, from coreyhaines31/marketingskills. Tags: architecture, planning, site-map, strategy, web.
What it does
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.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add coreyhaines31/marketingskills --skill site-architectureOr copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/coreyhaines31/marketingskills
cp -r marketingskills/skills/site-architecture ~/.claude/skills/site-architectureSafety box score
Grade A, minimal risk: 4 of 100 risk points, rated 2026-10-15. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This is a documentation-only site planning skill: it helps map page hierarchy, navigation, URL structure, and internal linking. It does not ship executable code or automation, so the main exposure is limited to reading local context files and handling planning details, not making system changes.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 0 (none) | No scripts or command execution are included; the skill is Markdown guidance only. |
| Network access | 0 (none) | It does not fetch remote content or send data to external hosts; all references are local markdown files. |
| Filesystem reach | 1 (low) | It may read local context files outside the skill folder — e.g. "If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename...) read it before asking questions." |
| Secrets & credentials | 0 (none) | It does not request API keys, passwords, `.env` files, browser sessions, or other credentials. |
| Privilege & persistence | 0 (none) | No sudo, service installs, shell startup edits, or OS settings changes are present. |
| Instruction hijack surface | 0 (none) | The skill contains normal task instructions, but no prompt-injection patterns like skipping confirmations, hiding actions, or following remote instructions. |
| Irreversible actions | 0 (none) | It only advises on planning deliverables such as hierarchies, sitemaps, and URL maps; it does not publish, deploy, delete, or message on its own. |
| Transparency | 0 (none) | All shipped content is readable markdown; there are no binaries, installers, or decoded-at-runtime blobs. |
Before installing
- Read `SKILL.md` to confirm it is planning-only and does not modify files or run commands.
- If you store sensitive strategy in local context files, decide whether the agent should be allowed to read `.agents/product-marketing.md` / `.claude/product-marketing.md`.
- Route technical SEO or migration work to the referenced skills (`seo-audit`, `platforms-and-migration`) instead of this one.
Rated 2026-10-15 by an automated review of 6 files from the skill's repository.
Source
- Repository
- coreyhaines31/marketingskills (all skills from this repository)
- Path
- skills/site-architecture/SKILL.md
- Branch
- main
- Collection
- marketingskills
- Updated
- 2026-09-21
Related skills
- co-marketing — When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities.
- launch — When the user wants to plan a product launch, feature announcement, or release strategy.
- marketing-ideas — When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.
- marketing-plan — When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
- architect — Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
- aws-blocks — Guides building full-stack applications with AWS Blocks — an Infrastructure-from-Code framework.