Site Architecture

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/site-architecture

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

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.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Before Planning, Site Types and Starting Points, Page Hierarchy Design, Navigation Design, URL Structure, Visual Sitemap Output (Mermaid).

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when planning or restructuring page hierarchy, navigation, and URL structure.
• Use when mapping site sections, breadcrumbs, and internal linking.
• Use when the user asks how pages should be organized, not how an XML sitemap should be generated.
• Use when the request clearly matches the imported source intent: Plan or restructure website hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Use when mapping pages, sections, and site structure, but not for XML sitemap auditing or schema markup.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

metadata.json

ORIGIN.md

references/mermaid-templates.md

references/navigation-patterns.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Before Planning

Check for product marketing context first: If

.agents/product-marketing-context.md

.claude/product-marketing-context.md

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?

Examples

Example 1: Ask for the upstream workflow directly

Use @site-architecture to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @site-architecture against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @site-architecture for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @site-architecture using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/site-architecture

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @server-management

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @service-mesh-expert

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @service-mesh-observability

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @sexual-health-analyzer

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/mermaid-templates.md

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

• mermaid-templates.md
• navigation-patterns.md
• site-type-templates.md
• evals.json
• mermaid-templates.md
• navigation-patterns.md

Imported Reference Notes

Imported: Site Types and Starting Points

/features/name

/blog/slug

/blog/slug

/category/slug

/category/subcategory/product

/docs/section/page

/product/feature

/blog/slug

/services/name

For full page hierarchy templates: See references/site-type-templates.md

Imported: 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

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

/

/features

/blog

/pricing

/features/analytics

/blog/seo-guide

/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

Imported: Navigation Design

Navigation Types

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

Imported: 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

/

example.com

/features/{name}

/features/analytics

/pricing

/pricing

/blog/{slug}

/blog/seo-guide

/blog/category/{slug}

/blog/category/seo

/customers/{slug}

/customers/acme-corp

/docs/{section}/{page}

/docs/api/authentication

/{page}

/privacy

/terms

/{slug}

/lp/{slug}

/free-trial

/lp/webinar

/compare/{competitor}

/vs/{competitor}

/compare/competitor-name

/integrations/{name}

/integrations/slack

/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:

/features/analytics

/blog/seo-guide

/docs/api/auth

Imported: Visual Sitemap Output (Mermaid)

Use Mermaid

graph TD

Basic Hierarchy

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

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

Imported: Internal Linking Strategy

Link Types

/features/analytics

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

Imported: 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

3. URL Map Table

/

/features

/features/analytics

/pricing

/blog

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

Imported: 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?

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.