agentleFS
Sign inStart free
phoenixvnphoenixvn/claude-code-agency/.claude/skills/sitemap/SKILL.md

sitemap

Skill0 starsChanged 7 months agoMITView on GitHub

Create a sitemap, page hierarchy, and page definitions. "Primary navigation items (4-7 recommended)?" Present options based on analysis with recommended structure. Follow-up for: secondary navigation, footer links, key landing pages. Present and ask for approval. Suggest /wireframe for next step.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a sitemap, page hierarchy, and page definitions.

    line 3
  2. Distinctive:

    Read brief, discovery report, and strategy docs (if available).

    line 8
  3. Distinctive:

    Use AskUserQuestion for navigation structure:

    line 18
  4. Distinctive:

    Follow-up for: secondary navigation, footer links, key landing pages.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/sitemap — Information Architecture

Create a sitemap, page hierarchy, and page definitions.

Instructions

Phase 1: Context

Read brief, discovery report, and strategy docs (if available).

Phase 2: Content Inventory

Spawn ux-lead to:

  • List all required pages/sections from brief and strategy
  • Define content types (landing page, article, product page, form, etc.)
  • Map user flows to pages
  • Identify entry points and conversion pages

Phase 3: IA Design

Use AskUserQuestion for navigation structure:

"Primary navigation items (4-7 recommended)?" Present options based on analysis with recommended structure.

Follow-up for: secondary navigation, footer links, key landing pages.

Phase 4: Sitemap Creation

Write hierarchical sitemap:

Home
├── About
│   ├── Team
│   └── Mission
├── Services
│   ├── Service A
│   └── Service B
├── Blog
│   ├── Category 1
│   └── Category 2
├── Contact
└── [Other pages]

Phase 5: Page Definitions

For each page, define: | Page | Purpose | Key Content Blocks | Primary CTA | SEO Priority | Save to deliverables/design/sitemap.md.

Present and ask for approval. Suggest /wireframe for next step.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free