site-architecture · 스킬 지원 에이전트
사이트의 메뉴, 페이지 계층과 내부 링크를 사용자가 찾는 일에 맞춰 정리합니다.
메뉴가 늘어나면서 원하는 자료가 어디에 있는지 알기 어려울 때 활용합니다. 사용자 유형과 주요 작업을 기준으로 목록, 모음집, 상세 페이지가 맡을 역할을 나눕니다.
현재 페이지 목록과 방문자가 하려는 일을 함께 알려주세요. 메뉴 이름, 페이지 계층과 URL 규칙을 비교할 수 있습니다. XML 사이트맵 파일을 만드는 작업과는 목적이 다르며 실제 탐색 구조를 먼저 설계하는 스킬입니다.
site-architecture로 스킬·AI·크롬 도구 모음집의 메뉴 구조를 점검해줘. 처음 방문한 사람이 원하는 작업을 찾는 경로와 상세에서 목록으로 돌아오는 경로를 정리해줘.
받을 수 있는 결과페이지 계층·URL·내부 링크 설계
스킬 지원 에이전트가 필요합니다. 실제 화면 수정과 URL 이전 처리는 별도입니다.
현재 사용 중인 스킬 지원 에이전트에 아래 요청을 붙여넣으세요. SKILL.md만 복사하면 보조 파일이 빠질 수 있어요.
https://github.com/coreyhaines31/marketingskills 에서 skills/site-architecture 스킬을 현재 에이전트의 스킬 폴더에 설치해줘. SKILL.md와 이 스킬이 참조하는 scripts·references·assets와 공통 파일을 함께 유지하고, 필요한 실행 환경과 추가 연결을 확인한 뒤 알려줘. 설치가 끝나면 site-architecture 스킬을 인식하는지 확인해줘.
“site-architecture 스킬을 사용해줘. 입력 자료: 페이지 목록·독자 작업·현재 메뉴”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘페이지 계층·URL·내부 링크 설계’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: site-architecture description: 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. metadata: version: 2.0.0 --- # 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?--- name: site-architecture description: 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. metadata: version: 2.0.0 --- # 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](references/site-type-templates.md) --- ## Page Hierarchy Design ### The 3-Click Rule 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. ### Flat vs Deep | 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. ### Hierarchy Levels | 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` | ### ASCII Tree Format Use this format for page hierarchies: ``` Homepage (/) ├── Features (/features) │ ├── Analytics (/features/analytics) │ ├── Automation (/features/automation) │ └── Integrations (/features/integrations) ├── Pricing (/pricing) ├── Blog (/blog) │ ├── [Category: SEO] (/blog/category/seo) │ └── [Category: CRO] (/blog/category/cro) ├── Resources (/resources) │ ├── Case Studies (/resources/case-studies) │ └── Templates (/resources/templates) ├── Docs (/docs) │ ├── Getting Started (/docs/getting-started) │ └── API Reference (/docs/api) ├── About (/about) │ └── Careers (/about/careers) └── Contact (/contact) ``` **When to use ASCII vs Mermaid**: - ASCII: quick hierarchy drafts, text-only contexts, simple structures - Mermaid: visual presentations, complex relationships, showing nav zones or linking patterns --- ## Navigation Design ### Navigation Types | Nav Type | Purpose | Placement | |----------|---------|-----------| | Header nav | Primary navigation, always visible | Top of every page | | Dropdown menus | Organize sub-pages under parent | Expands from header items | | Footer nav | Secondary links, legal, sitemap | Bottom of every page | | Sidebar nav | Section navigation (docs, blog) | Left side within a section | | Breadcrumbs | Show current location in hierarchy | Below header, above content | | Contextual links | Related content, next steps | Within page content | ### Header Navigation Rules - **4-7 items max** in the primary nav (more causes decision paralysis) - **CTA button** goes rightmost (e.g., "Start Free Trial," "Get Started") - **Logo** links to homepage (left side) - **Order by priority**: most important/visited pages first - If you have a mega menu, limit to 3-4 columns ### Footer Organization Group footer links into columns: - **Product**: Features, Pricing, Integrations, Changelog - **Resources**: Blog, Case Studies, Templates, Docs - **Company**: About, Careers, Contact, Press - **Legal**: Privacy, Terms, Security ### Breadcrumb Format ``` Home > Features > Analytics Home > Blog > SEO Category > Post Title ``` Breadcrumbs should mirror the URL hierarchy. Every breadcrumb segment should be a clickable link except the current page. **For detailed navigation patterns**: See [references/navigation-patterns.md](references/navigation-patterns.md) --- ## URL Structure ### Design Principles 1. **Readable by humans** — `/features/analytics` not `/f/a123` 2. **Hyphens, not underscores** — `/blog/seo-guide` not `/blog/seo_guide` 3. **Reflect the hierarchy** — URL path should match site structure 4. **Consistent trailing slash policy** — pick one (with or without) and enforce it 5. **Lowercase always** — `/About` should redirect to `/about` 6. **Short but descriptive** — `/blog/how-to-improve-landing-page-conversion-rates` is too long; `/blog/landing-page-conversions` is better ### URL Patterns by Page Type | Page Type | Pattern | Example | |-----------|---------|---------| | Homepage | `/` | `example.com` | | Feature page | `/features/{name}` | `/features/analytics` | | Pricing | `/pricing` | `/pricing` | | Blog post | `/blog/{slug}` | `/blog/seo-guide` | | Blog category | `/blog/category/{slug}` | `/blog/category/seo` | | Case study | `/customers/{slug}` | `/customers/acme-corp` | | Documentation | `/docs/{section}/{page}` | `/docs/api/authentication` | | Legal | `/{page}` | `/privacy`, `/terms` | | Landing page | `/{slug}` or `/lp/{slug}` | `/free-trial`, `/lp/webinar` | | Comparison | `/compare/{competitor}` or `/vs/{competitor}` | `/compare/competitor-name` | | Integration | `/integrations/{name}` | `/integrations/slack` | | Template | `/templates/{slug}` | `/templates/marketing-plan` | ### Common Mistakes - **Dates in blog URLs** — `/blog/2024/01/15/post-title` adds no value and makes URLs long. Use `/blog/post-title`. - **Over-nesting** — `/products/category/subcategory/item/detail` is too deep. Flatten where possible. - **Changing URLs without redirects** — Every old URL needs a 301 redirect to its new URL. Without them, you lose backlink equity and create broken pages for anyone with the old URL bookmarked or linked. - **IDs in URLs** — `/product/12345` is not human-readable. Use slugs. - **Query parameters for content** — `/blog?id=123` should be `/blog/post-title`. - **Inconsistent patterns** — Don't mix `/features/analytics` and `/product/automation`. Pick one parent. ### Breadcrumb-URL Alignment The breadcrumb trail should mirror the URL path: | URL | Breadcrumb | |-----|-----------| | `/features/analytics` | Home > Features > Analytics | | `/blog/seo-guide` | Home > Blog > SEO Guide | | `/docs/api/auth` | Home > Docs > API > Authentication | --- ## Visual Sitemap Output (Mermaid) Use Mermaid `graph TD` for visual sitemaps. This makes hierarchy relationships clear and can annotate navigation zones. ### Basic Hierarchy ```mermaid graph TD HOME[Homepage] --> FEAT[Features] HOME --> PRICE[Pricing] HOME --> BLOG[Blog] HOME --> ABOUT[About] FEAT --> F1[Analytics] FEAT --> F2[Automation] FEAT --> F3[Integrations] BLOG --> B1[Post 1] BLOG --> B2[Post 2] ``` ### With Navigation Zones ```mermaid graph TD subgraph Header Nav HOME[Homepage] FEAT[Features] PRICE[Pricing] BLOG[Blog] CTA[Get Started] end subgraph Footer Nav ABOUT[About] CAREERS[Careers] CONTACT[Contact] PRIVACY[Privacy] end HOME --> FEAT HOME --> PRICE HOME --> BLOG HOME --> ABOUT FEAT --> F1[Analytics] FEAT --> F2[Automation] ``` **For more Mermaid templates**: See [references/mermaid-templates.md](references/mermaid-templates.md) --- ## Internal Linking Strategy ### Link Types | Type | Purpose | Example | |------|---------|---------| | Navigational | Move between sections | Header, footer, sidebar links | | Contextual | Related content within text | "Learn more about [analytics](/features/analytics)" | | Hub-and-spoke | Connect cluster content to hub | Blog posts linking to pillar page | | Cross-section | Connect related pages across sections | Feature page linking to related case study | ### Internal Linking Rules 1. **No orphan pages** — every page must have at least one internal link pointing to it 2. **Descriptive anchor text** — "our analytics features" not "click here" 3. **5-10 internal links per 1000 words** of content (approximate guideline) 4. **Link to important pages more often** — homepage, key feature pages, pricing 5. **Use breadcrumbs** — free internal links on every page 6. **Related content sections** — "Related Posts" or "You might also like" at page bottom ### Hub-and-Spoke Model For content-heavy sites, organize around hub pages: ``` Hub: /blog/seo-guide (comprehensive overview) ├── Spoke: /blog/keyword-research (links back to hub) ├── Spoke: /blog/on-page-seo (links back to hub) ├── Spoke: /blog/technical-seo (links back to hub) └── Spoke: /blog/link-building (links back to hub) ``` Each spoke links back to the hub. The hub links to all spokes. Spokes link to each other where relevant. ### Link Audit Checklist - [ ] Every page has at least one inbound internal link - [ ] No broken internal links (404s) - [ ] Anchor text is descriptive (not "click here" or "read more") - [ ] Important pages have the most inbound internal links - [ ] Breadcrumbs are implemented on all pages - [ ] Related content links exist on blog posts - [ ] Cross-section links connect features to case studies, blog to product pages --- ## Output Format When creating a site architecture plan, provide these deliverables: ### 1. Page Hierarchy (ASCII Tree) Full site structure with URLs at each node. Use the ASCII tree format from the Page Hierarchy Design section. ### 2. Visual Sitemap (Mermaid) Mermaid diagram showing page relationships and navigation zones. Use `graph TD` with subgraphs for nav zones where helpful. ### 3. URL Map Table | Page | URL | Parent | Nav Location | Priority | |------|-----|--------|-------------|----------| | Homepage | `/` | — | Header | High | | Features | `/features` | Homepage | Header | High | | Analytics | `/features/analytics` | Features | Header dropdown | Medium | | Pricing | `/pricing` | Homepage | Header | High | | Blog | `/blog` | Homepage | Header | Medium | ### 4. Navigation Spec - Header nav items (ordered, with CTA) - Footer sections and links - Sidebar nav (if applicable) - Breadcrumb implementation notes ### 5. Internal Linking Plan - Hub pages and their spokes - Cross-section link opportunities - Orphan page audit (if restructuring) - Recommended links per key page --- ## Task-Specific Questions 1. Is this a new site or are you restructuring an existing one? 2. What type of site is it? (SaaS, content, e-commerce, docs, hybrid, small business) 3. How many pages exist or are planned? 4. What are the 5 most important pages on the site? 5. Are there existing URLs that need to be preserved or redirected? 6. Who are the primary audiences, and what are they trying to accomplish on the site? --- ## Related Skills - **content-strategy**: For planning what content to create and topic clusters - **programmatic-seo**: For building SEO pages at scale with templates and data - **seo-audit**: For technical SEO, on-page optimization, and indexation issues - **cro**: For optimizing individual pages for conversion - **schema**: For implementing breadcrumb and site navigation structured data - **competitors**: For comparison page frameworks and URL patterns
Original skill: coreyhaines31/marketingskills/skills/site-architecture/SKILL.md Source: https://github.com/coreyhaines31/marketingskills/blob/dda3841f0b294e01e93b1541486beefbfab0915e/skills/site-architecture/SKILL.md License: MIT MIT License Copyright (c) 2025 Corey Haines Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.