component-update-navigation

component-update-navigation is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (3,879 once invoked), scanned A, original, MIT.

A set of instructions for improving an existing website navigation component, including its speed, accessibility, mobile behavior, and navigation features.

In plain words
What is it for?
Use it to review rendering, loading, state, and memory use; improve ARIA and keyboard support; and refine responsive and touch interactions.
Why use it?
It gives developers a checklist for reducing unnecessary work and making navigation easier to use with keyboards, screen readers, touch, and small screens.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/oakensoul/nextjs-cursor-prompts/component-update-navigation
Clone the repo
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-prompts

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for component-update-navigation

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-navigation.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-navigation)
Your own site
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-navigation"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-navigation.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,879 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03879
Opus 5 $0.00000 $0.01939
Sonnet 5 $0.00000 $0.00776
Haiku 4.5 $0.00000 $0.00388

Measured 5d ago against content hash df70acda514a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

component-update-navigation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/prompts/component/component-update-navigation.mdc · 602 lines

How it starts

The opening of the file, as written. The whole thing — 602 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Please enhance the existing navigation component with performance optimizations, accessibility improvements, mobile experience upgrades, and advanced navigation features.

  1. OPTIMIZE performance with efficient rendering, lazy loading, and state management improvements
  2. ENHANCE accessibility with advanced ARIA patterns, keyboard navigation, and screen reader support
  3. IMPROVE mobile experience with touch interactions, responsive patterns, and progressive enhancement
  4. ADD advanced features like analytics integration, dynamic navigation, and user preferences
  5. MAINTAIN backward compatibility while implementing modern navigation patterns

STEP 1: Current Navigation Assessment

Performance Analysis:
  • Rendering efficiency: Identify unnecessary re-renders and optimization opportunities
  • Bundle size impact: Analyze navigation component size and lazy loading potential
  • State management: Review current state patterns and optimization opportunities
  • Memory usage: Check for memory leaks in navigation interactions
Accessibility Audit:
  • WCAG compliance: Verify current WCAG 2.1 AA compliance level
  • Keyboard navigation: Test comprehensive keyboard accessibility
  • Screen reader compatibility: Validate screen reader announcements and navigation
  • Focus management: Review focus indicators and logical tab order
Mobile Experience Review:
  • Touch target sizing: Ensure minimum 44px touch targets
  • Responsive behavior: Test navigation across different screen sizes
  • Performance on mobile: Analyze mobile-specific performance issues
  • Gesture support: Evaluate touch gesture implementation

STEP 2: Performance Optimization Strategies

Rendering Optimization:
// Memoized navigation component for performance
const NavigationComponent = memo(({ items, currentPath, ...props }) => {
  // Memoize active state calculations
  const activeStates = useMemo(() => 
    calculateActiveStates(items, currentPath), 
    [items, currentPath]
  )

  // Memoize navigation items with stable references
  const memoizedItems = useMemo(() => 
    items.map(item => ({
      ...item,
      isActive: activeStates[item.href],
      children: item.children?.map(child => ({
        ...child,
        isActive: activeStates[child.href]
      }))
    })), 
    [items, activeStates]
  )

  return (
    <NavigationContainer 
      items={memoizedItems}
      {...props}
    />
  )
})

Read the full file on GitHub · 602 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 602 lines · 0 tokens per session scan A df70acda514a

Subscribe to this mod's changes

component-update-navigation is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,879 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.