What problem does it solve? Designing application navigation for complex enterprise web apps often leads to inconsistent decisions — overflowing menus, hover-triggered sub-navs, icon-only rails, modals polluting browser history, and forms split across tabs. This Skill provides opinionated, enforceable house rules so AI assistants and designers make consistent structural choices for sidebars, top bars, breadcrumbs, and tabs. ## Core Features & Use Cases - Routing and history rules: Every navigable view gets a unique URL; modals and panels stay out of browser history unless deliberately deep-linkable; each tab gets its own sub-path. - Navigation structure decisions: Horizontal top bar vs. vertical sidebar based on responsive targets and item-count growth, 7 ± 2 items per level, click-not-hover sub-nav disclosure, and collapsed-by-default groups. - Hard prohibitions and checklists: No icon-only rails, no wrapped or scrolling horizontal nav, no bottom navigation bars, permission-based hiding vs. disabling, and a 28-point pre-flight checklist. - Use Case: When asked to build an app shell with a sidebar, sub-menus, and tabbed detail views, the Skill ensures each tab is a route, sub-nav opens on click, groups load collapsed except the active one, and overflow is fixed structurally rather than with scrollbars. ## Quick Start Review my app shell layout with a sidebar, nested menus, and tabbed detail pages against the Recursica navigation house rules.
