sk-navigation

Centralize Next.js navigation in a single config with RBAC filtering.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-navigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sk-navigation
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/sk-navigation
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill sk-navigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents navigation drift and duplicated UI logic by making the app’s sidebar and mobile tabs render from a single declarative navigation config with consistent role-based filtering.

Core Features & Use Cases

  • Config-driven navigation (SSOT): Define all routes once in src/config/navigation.ts, and have Sidebar, BottomNav, and BottomNavMoreSheet consume the same registry.
  • RBAC runtime filtering: Apply role visibility consistently at render time using filterNavigationByRole, getBottomNavItems, and getMoreSheetItems.
  • Mobile composition with overflow: Enforce the “max 4 tabs + Más” behavior, preserve grouped items in the overflow sheet, and support collapsible sections.
  • Notifications badge integration: Show unread-count badges on the appropriate nav items when notifications are enabled.
  • iOS safe-area handling: Respect env(safe-area-inset-bottom) so the bottom UI doesn’t get covered by the home indicator.

Quick Start

Add or modify your new link by editing only src/config/navigation.ts, then verify visibility across Sidebar, BottomNav, and the More sheet using the appropriate user role.

Frequently Asked Questions about sk-navigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage role-based access control for Next.js navigation items?

Manage role-based access control for Next.js navigation by defining all routes in a single config file and applying runtime RBAC filtering with helper APIs to render only the items visible to each user's role.

What is the best way to configure a mobile bottom navigation bar with overflow in Next.js?

Configure a mobile bottom navigation bar by defining routes in a central config and using helper APIs to enforce a maximum of four tabs plus an overflow sheet, preserving grouped and collapsible structures for extra items.

How do I gate Next.js sidebar links with feature flags for notifications?

Gate Next.js sidebar links with feature flags by defining their visibility in the central navigation config, allowing the system to conditionally render items like notifications and display unread-count badges when enabled.

Does config-driven navigation support iOS safe-area handling for mobile bottom nav?

Config-driven navigation supports iOS safe-area handling by respecting the bottom safe-area inset environment variables, ensuring the mobile bottom navigation UI remains unobstructed by the iOS home indicator.

How do I add a new link to both the Next.js sidebar and mobile bottom nav without duplicating logic?

Add a new link to both the Next.js sidebar and mobile bottom nav by editing the single source of truth config file once, which automatically propagates the update to all consuming UI components with consistent role-based filtering.

Why does my Next.js navigation drift between the sidebar and mobile tabs?

Next.js navigation drifts between the sidebar and mobile tabs when they are not rendered from a single declarative navigation config, causing duplicated UI logic and inconsistent role-based visibility across components.