Skills › Marketing Skills › site-architecture › evals.json
evals.json
113 lines · skills/site-architecture/evals/evals.json at 88c79f6
1{
2 "skill_name": "site-architecture",
3 "evals": [
4 {
5 "id": 1,
6 "prompt": "Help me plan the site architecture for our new SaaS marketing website. We have a homepage, product page, pricing page, about page, blog, and want to add competitor comparison pages and integration pages.",
7 "expected_output": "Should check for product-marketing.md first. Should apply the page hierarchy design principles (3-click rule, flat vs deep). Should create an ASCII tree showing the full site structure. Should organize pages logically: main nav (Home, Product, Pricing, About, Blog), comparison pages section, integrations hub. Should recommend URL structure patterns for each section. Should provide navigation design recommendations (4-7 header items). Should include internal linking strategy (hub-and-spoke for comparisons and integrations). Should provide the full deliverable set: hierarchy, URL map, nav spec.",
8 "assertions": [
9 "Checks for product-marketing.md",
10 "Applies 3-click rule and flat vs deep principles",
11 "Creates ASCII tree for site structure",
12 "Organizes pages logically",
13 "Recommends URL structure for each section",
14 "Provides navigation design (4-7 header items)",
15 "Includes internal linking strategy",
16 "Provides hierarchy, URL map, and nav spec"
17 ],
18 "files": []
19 },
20 {
21 "id": 2,
22 "prompt": "Our website has grown organically and the navigation is a mess. We have 50+ pages and users can't find anything. Help us reorganize.",
23 "expected_output": "Should treat this as a site architecture audit and redesign. Should recommend starting with a content inventory of all 50+ pages. Should apply the page hierarchy design to reorganize: group related pages, establish clear parent-child relationships, apply the 3-click rule. Should redesign the navigation (reduce header items, use mega-menu or dropdowns for deeper pages). Should provide before/after ASCII tree structure. Should address URL redirects for any pages that move. Should include a visual sitemap (Mermaid).",
24 "assertions": [
25 "Recommends content inventory first",
26 "Groups related pages logically",
27 "Applies 3-click rule",
28 "Redesigns navigation structure",
29 "Provides ASCII tree or visual sitemap",
30 "Addresses URL redirects for moved pages",
31 "Reduces header navigation items"
32 ],
33 "files": []
34 },
35 {
36 "id": 3,
37 "prompt": "what should our url structure look like? we keep debating between /blog/post-name vs /resources/blog/post-name and /product/feature vs /features/feature-name",
38 "expected_output": "Should trigger on casual phrasing. Should apply the URL structure patterns guidance. Should recommend clean, descriptive URLs: prefer shorter paths (/blog/post-name over /resources/blog/post-name), use consistent patterns, avoid unnecessary nesting. Should provide URL structure recommendations for each section type (blog, features, comparisons, integrations). Should address SEO implications of URL structure. Should provide a complete URL map as a reference.",
39 "assertions": [
40 "Triggers on casual phrasing",
41 "Applies URL structure patterns",
42 "Recommends shorter, cleaner paths",
43 "Provides recommendations for each section type",
44 "Addresses SEO implications",
45 "Provides URL map reference"
46 ],
47 "files": []
48 },
49 {
50 "id": 4,
51 "prompt": "We're adding programmatic SEO pages — 200 integration pages and 50 comparison pages. How should these fit into our site architecture?",
52 "expected_output": "Should address how to integrate scaled content into the site architecture. Should recommend hub pages for both sections (/integrations and /compare or /vs). Should apply the hub-and-spoke internal linking model. Should address navigation: these shouldn't clutter the main nav, but should be accessible via hub pages. Should provide URL structure for both sections. Should address crawl budget considerations for 250 new pages. Should cross-reference programmatic-seo for the content strategy.",
53 "assertions": [
54 "Recommends hub pages for each section",
55 "Applies hub-and-spoke internal linking",
56 "Keeps programmatic pages out of main nav",
57 "Provides URL structure for both sections",
58 "Addresses crawl budget for 250 pages",
59 "Cross-references programmatic-seo skill"
60 ],
61 "files": []
62 },
63 {
64 "id": 5,
65 "prompt": "Can you create a visual sitemap for our site? We want something we can share with our design team.",
66 "expected_output": "Should provide a visual sitemap using Mermaid diagram format. Should organize the sitemap hierarchically showing page relationships. Should use the Mermaid graph syntax that can be rendered by most tools. Should include all major sections and key pages. Should be clear enough for a design team to use as a reference for navigation and wireframing.",
67 "assertions": [
68 "Provides visual sitemap in Mermaid format",
69 "Shows hierarchical page relationships",
70 "Includes all major sections",
71 "Uses clear, readable format",
72 "Suitable for sharing with design team"
73 ],
74 "files": []
75 },
76 {
77 "id": 6,
78 "prompt": "Our XML sitemap hasn't been updated in 6 months and we have crawl errors in Search Console. Can you fix our technical SEO?",
79 "expected_output": "Should recognize this is a technical SEO audit task, not a site architecture design task. Should defer to or cross-reference the seo-audit skill, which handles XML sitemaps, crawl errors, and technical SEO issues. Site-architecture focuses on page hierarchy, navigation, and URL structure design — not technical SEO troubleshooting.",
80 "assertions": [
81 "Recognizes this as technical SEO, not site architecture",
82 "References or defers to seo-audit skill",
83 "Explains site-architecture covers design, not technical SEO"
84 ],
85 "files": []
86 },
87 {
88 "id": 7,
89 "prompt": "We're a 20-person B2B SaaS on Webflow. Marketing wants a new blog and about 300 integration pages, and someone suggested moving the whole site to an AI website builder. What should we do?",
90 "expected_output": "Should start from the architecture and the questions in the platforms reference (who edits, page volume and data, integrations, lock-in, cost at real size) rather than naming a platform first. Should keep the current platform (Webflow) in the running and note that moving platforms often costs more than it fixes when the site works. Should compare a shortlist (e.g., staying on Webflow's CMS within its item limits, a reverse-proxied subpath from another tool, or an AI-native platform) with tradeoffs. Any Verified Partner tool named (e.g., Ploy) carries the disclosure and an alternative. Should cover subpath vs subdomain for the new sections and, if migrating, the redirect map and SEO checks.",
91 "assertions": [
92 "Asks or reasons through the platform criteria before recommending",
93 "Keeps the current platform as a real option",
94 "Gives a shortlist with tradeoffs, not a single answer",
95 "Discloses any partner tool and names an alternative",
96 "Covers subpath vs subdomain for the new sections"
97 ],
98 "files": []
99 },
100 {
101 "id": 8,
102 "prompt": "We're migrating our marketing site from WordPress to a new platform next month. How do we not lose our SEO traffic?",
103 "expected_output": "Should lay out the migration plan from the platforms reference: crawl and save every URL with metadata, pull top pages by clicks/conversions/backlinks, keep URLs where possible, check what the CMS import carries (many don't move routes, metadata, redirects), build a one-to-one 301 map (never all to homepage), deploy redirects at switch time, submit the new sitemap, spot-check top pages, verify tracking and forms, and monitor Search Console for 404s afterwards.",
104 "assertions": [
105 "Crawls and saves current URLs and metadata first",
106 "Builds a one-to-one 301 redirect map",
107 "Warns that imports may not carry routes, metadata, or redirects",
108 "Includes launch-day checks and post-launch Search Console monitoring"
109 ],
110 "files": []
111 }
112 ]
113}