BeginnerCorey Haines (marketingskills)

Site Architecture

Site Architecture is an ecommerce AI skill for Corey Haines (marketingskills), built for teams working with Codex, Claude Code, OpenClaw. Use it to you are…

Views
0
Installs
0
Favorites
0
Supported Platforms
Codex · Claude Code · OpenClaw
01

What this Skill does

You are investigating why a product, category, or landing page is missing expected organic traffic. The first decision to test is whether Planning a new SaaS marketing site structure before development and Restructuring a bloated content site with poor navigation and orphan… Start with a small test around “Planning a new SaaS marketing site structure before development”, then check whether “Restructuring a bloated content site with poor navigation and orphan pages” fits the way your team actually works.

02

What makes it different

01

Uses inventory signals for operating decisions

The source works with stock, demand, or reorder information to identify what should be replenished, monitored, or investigated.

02

Structures the analysis before making a recommendation

The source asks for analysis, classification, ranking, or scoring before it reaches a conclusion or next action.

03

No installation needed

Copy and paste into a model chat
  1. Expand and copy the complete original Skill.md below.
  2. Open a new conversation in a compatible AI model, then paste it into the chat box.
  3. Add verified task details, run one low-risk example, and review the result before using it in store operations.
04

Original Skill.md

The complete source is shown below. Copy it from the top right to use it.

You are an information architecture expert. Plan the website structure by first gathering context: business goals, primary audiences, site type (SaaS/content/e-commerce/docs/hybrid/small business), current state, and content inventory. Design page hierarchy following the 3-click rule — important pages reachable within 3 clicks from homepage. Organize into levels: L0 (homepage), L1 (primary sections), L2 (section pages), L3+ (detail). Design navigation: 4-7 header items max, CTA button rightmost, logo links home, order by priority. Define URL structure: human-readable, hyphens not underscores, lowercase, reflecting hierarchy, consistent trailing slash policy. Output an ASCII tree showing full page hierarchy, a Mermaid visual sitemap, a URL map with redirects for restructures, navigation specs for header/footer/sidebar, and an internal linking plan using hub-and-spoke models with contextual linking rules.
05

Get started

Starter prompts for the main use cases—copy and use them directly.

01

Start with one real task

Do not begin with a store-wide rollout. Pick one reversible task where Site Architecture can help you create, localize, or check product content and visual assets. Use this when the input boundary, owner, and one primary measure from factual corrections, editing time, approval rate, and conversion quality are written down.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Start with one real task.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Do not begin with a store-wide rollout. Pick one reversible task where Site Architecture can help you create, localize, or check product content and visual assets.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
02

Prepare the input and guardrails

Collect only the verified product facts, source images, brand rules, target channel, and prohibited claims needed for this test. Remove unrelated personal data and state which actions must never run automatically. Use this when every input has a known source, sensitive fields are minimized, and the approver knows what the trial can read or change.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Prepare the input and guardrails.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Collect only the verified product facts, source images, brand rules, target channel, and prohibited claims needed for this test. Remove unrelated personal data and state which actions must never run automatically.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
03

Inspect the source Skill, then run it

Read the source, installation method, and permission notes before adding Site Architecture to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a product-content draft that a responsible operator can inspect, and it stayed inside the approved boundary.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Inspect the source Skill, then run it.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Read the source, installation method, and permission notes before adding Site Architecture to a separate test project. Keep commands and Skill text exactly as published.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
04

Review it against a baseline

Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time. Use this when factual corrections, editing time, approval rate, and conversion quality has a pre-test baseline, and errors and exceptions are logged separately.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Review it against a baseline.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
06

Risks and operating notes

A chat instruction does not update inventory

If the instruction mentions inventory, treat that as an operational step to verify. A pasted Skill cannot change stock records unless a separately configured and approved integration performs that action.

Community rating results

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result

No reviews yet.

Leave a review

Rate every dimension, then share your real experience.

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result
Author / maintainer

Corey Haines

Creator of Marketing Skills, an open-source collection of reusable agent skills for content, SEO, conversion, launch, and growth work.

Risk, permissions, and limitations

Review third-party permission scopes before providing store data. Never paste payment credentials, customer passwords, or unnecessary personal data into a model. Outputs must be checked by the operator responsible for the workflow.

Content checked: