navigation-menu-generator
The navigation-menu-generator skill guides the design and optimization of site navigation menus across desktop and mobile platforms. Use it when addressing menu structure, hierarchy, SEO performance, accessibility requirements, or user experience for primary navigation, dropdowns, mega menus, mobile menus, or hamburger implementations. The skill provides frameworks for organizing menu items, implementing semantic HTML and ARIA standards, ensuring keyboard navigation and screen reader compatibility, and applying SEO best practices for crawlability and link visibility.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/navigation-menu-generator && cp -r /tmp/navigation-menu-generator/skills/components/navigation/navigation-menu ~/.claude/skills/navigation-menu-generatorSKILL.md
# Components: Navigation Menu Guides navigation menu design for SEO, UX, and accessibility. Navigation helps users find content and signals site structure to search engines. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for key pages and audience. Identify: 1. **Site structure**: Main sections, hierarchy 2. **Primary goals**: Conversion paths, key pages 3. **Platform**: Web, mobile, both ## Structure & Organization ### Menu Size - **Primary nav**: 7-9 items; avoid overwhelming users - **Sub-navigation**: Up to 2 levels; deeper topics in sub-menus - **Pattern**: Horizontal top nav or vertical side nav; avoid novel patterns ### Hierarchy - Reflect sitemap structure; need not match exactly - Prioritize what visitors need most - Logical grouping by topic or task ## SEO Best Practices | Practice | Purpose | |----------|---------| | **Semantic HTML** | `<nav>`, `<ul>`, `<li>`; proper landmark roles | | **Descriptive anchor text** | Target keywords; avoid "Click here" | | **Text links** | Prefer text over images; crawlers need readable links | | **Initial render** | All nav HTML in first paint; no JS-only menus for critical links. See **rendering-strategies** | | **Visible links** | Prefer visible over hidden; helps crawlers understand structure | ### Crawlability - Sub-menus: Ensure HTML is in DOM (e.g., CSS-hidden, not JS-injected) - Footer nav: Include secondary links - Breadcrumbs: See **breadcrumb-generator** for implementation ## UX Guidelines ### Visibility & Location - **Desktop**: Visible nav; avoid hiding behind hamburger when space allows - **Expected placement**: Primary nav in header; footer nav at bottom - **Current location**: Indicate active page/section in menu ### Accessibility | Requirement | Practice | |-------------|----------| | **Labels** | Clear, intuitive wording | | **Contrast** | 4.5:1 for link text | | **Touch targets** | >=44x44px; adequate spacing | | **Keyboard** | Full keyboard navigation; focus visible | | **Screen readers** | Proper ARIA; skip links for long menus | ### Design - Simple, clear; avoid covering entire screen with open menus on desktop - Consistent across pages - Mobile: Hamburger acceptable; ensure menu is usable when open ## Output Format - **Structure** (primary items, sub-items) - **Anchor text** suggestions - **HTML/ARIA** notes - **SEO** checklist - **Accessibility** checklist ## Related Skills - **website-structure**: Plan structure and nav hierarchy; nav reflects planned sections - **xml-sitemap**: Nav should reflect discoverable pages - **internal-links**: Nav is primary internal linking - **site-crawlability**: Nav affects crawl paths - **category-page-generator**: Category hierarchy in nav - **footer-generator**: Footer nav complements header nav - **logo-generator**: Logo typically sits in header with nav - **breadcrumb-generator**: Breadcrumb navigation; BreadcrumbList schema - **rendering-strategies**: Nav in first paint; no JS-only menus
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.