gmira-nav

Enforce mode-specific navigation patterns for Next.js and Tailwind CSS headers.

Updated Jul 25, 2026
One-click install
npx skills add https://github.com/OthmanAdi/gmira --skill gmira-nav
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gmira-nav
Source: https://github.com/OthmanAdi/gmira/tree/main/skills/gmira-nav
Command: npx skills add https://github.com/OthmanAdi/gmira --skill gmira-nav

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the issue of generic, unauthored site navigation that fails to reflect the specific material world or purpose of a product, preventing the common trap of using identical, low-effort UI patterns across different projects.

Core Features & Use Cases

  • Mode-Based Navigation: Tailors navigation structure based on the page mode (Persuade, Operate, Read, or Experience) to ensure the UI serves the user's actual intent.
  • Structural Line System: Implements a consistent, authored aesthetic using rule tokens and CSS utilities that integrate seamlessly with the page's rhythm.
  • Accessibility-First Chrome: Provides robust patterns for skip links, focus management, and mobile interactions that avoid the pitfalls of standard full-screen overlays.
  • Use Case: Use this skill when building a landing page header to ensure the navigation is specific to the product's thesis, or when auditing an existing site to replace generic hamburger menus with context-aware navigation.

Quick Start

Use the gmira-nav skill to audit the current site header and implement a mode-specific navigation structure that aligns with the page direction.

Frequently Asked Questions about gmira-nav

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

FAQPage Schema
How do I build accessible site navigation in Next.js and Tailwind CSS?

Build accessible site navigation in Next.js and Tailwind CSS by enforcing mode-specific structural patterns, semantic landmarks, focus trapping, and aria-current usage. This approach standardizes headers and menus while ensuring robust keyboard interactions.

What is mode-based navigation design for web pages?

Mode-based navigation design tailors the site header structure based on page intent, such as Persuade, Operate, Read, or Experience. This ensures the navigation chrome actively serves the user's specific goal rather than using generic layouts.

How do I implement a command palette with focus trapping in Tailwind CSS?

Implement a command palette with focus trapping in Tailwind CSS by applying accessibility-first chrome patterns and semantic landmarks. These structural rules prevent focus escape and ensure keyboard users can navigate the overlay without getting stuck.

Why does my mobile menu overlay fail accessibility audits?

Mobile menu overlays fail accessibility audits when they use generic full-screen patterns without proper focus management or skip links. Replacing them with context-aware navigation and robust focus trapping resolves these structural pitfalls.

Can I use standard line-rule systems to design web navigation chrome?

Yes, you can design web navigation chrome using a consistent structural line system with rule tokens and CSS utilities. This integrates the header and mobile menus seamlessly with the page's visual rhythm and material aesthetic.

How do I audit an existing site header for generic UI patterns?

Audit an existing site header by checking if the navigation reflects the product's thesis and mode direction. Replace generic hamburger menus with context-aware structures that enforce accessibility standards and mode-specific patterns.