Components Navigation Menu
- 10 installs
- 852 repo stars
- Updated June 9, 2026
- kostja94/marketing-skills
Helps with ai & agent building tasks.
About
components-navigation-menu is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- components-navigation-menu
- AI & Agent Building
- AI-coding skill
Components Navigation Menu by the numbers
- 10 all-time installs (skills.sh)
- Ranked #11,959 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kostja94/marketing-skills --skill components-navigation-menuAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10 |
|---|---|
| repo stars | ★ 852 |
| Last updated | June 9, 2026 |
| Repository | kostja94/marketing-skills ↗ |
What it does
Helps with ai & agent building tasks.
Files
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 product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-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: → 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 |
| 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: Help users and crawlers; add BreadcrumbList schema
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 | →.5:1 for link text |
| Touch targets | ≥44×44px; 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
- seo-technical-sitemap: Nav should reflect discoverable pages
- seo-on-page-internal-links: Nav is primary internal linking
- seo-technical-crawlability: Nav affects crawl paths
- pages-category-pages: Category hierarchy in nav
- components-footer: Footer nav complements header nav
- components-logo: Logo typically sits in header with nav
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10