operator-app-auth-routing

Name: operator-app-auth-routing
Availability: InStock
Author: cogni-dao

Enforce authentication routing for Next.js operator app pages and API endpoints.

4|5|Updated Nov 5, 2025

Search Tags:#testing #routing #nextjs #proxy #auth #nextauth

Ready to run

npx skills add https://github.com/cogni-dao/cogni --skill operator-app-auth-routing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: operator-app-auth-routing
Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/operator-app-auth-routing
Command: npx skills add https://github.com/cogni-dao/cogni --skill operator-app-auth-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keep page placement, chrome state, and auth enforcement separate. proxy.ts is the routing contract; route groups and UI chrome should not become alternate auth systems.

Core Features & Use Cases

Public vs app route grouping: enforce correct grouping to avoid leaking app routes.
Auth-aware public chrome: ensure session identity and wallet-connect state are reflected correctly.
API auth rules & tests: maintain consistent /api/v1 access rules and matcher tests across nodes.

Quick Start

Configure your operator app to align its routing with proxy.ts, update APP_ROUTES and config.matcher, and run tests to validate auth routing.

Frequently Asked Questions about operator-app-auth-routing

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

FAQPage Schema

How do I enforce authentication routing in a Next.js operator app?▼

To configure auth-aware routing, align your Next.js route groups with proxy.ts, update the APP_ROUTES configuration and config.matcher, then run tests to validate that routing policies and access control are synchronized across pages and API endpoints.

Why does my Next.js public route group leak protected app routes?▼

NextAuth secures API endpoints by maintaining consistent /api/v1 access rules and route matcher tests. This proxy-driven approach synchronizes routing policies across endpoints, ensuring nodes, dashboard, and knowledge routes have correct access control.

How do I test proxy-driven access control for Next.js route matchers?▼

Auth-aware chrome reflects session identity and wallet-connect state by aligning UI elements with proxy.ts routing policies. This separation ensures that chrome state accurately represents the user's authenticated session without overriding proxy access control.

What is the best way to separate UI chrome state from Next.js proxy auth?▼

The best way to separate UI chrome state from proxy auth is treating proxy.ts as the sole routing contract. This keeps page placement, chrome state, and auth enforcement separate, avoiding conflicting alternate auth systems.