navigator

Locate backend routers, frontend pages, and design specs in repositories.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/dankofly/Swing_B2B --skill navigator-dankofly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: navigator
Source: https://github.com/dankofly/Swing_B2B/tree/main/.claude/skills/navigator
Command: npx skills add https://github.com/dankofly/Swing_B2B --skill navigator-dankofly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers quickly understand project structure and locate important files, eliminating time spent scanning large or unfamiliar codebases.

Core Features & Use Cases

  • Quick Paths: Provides direct paths to common locations such as backend routers, frontend pages, and design specs.
  • Guided Reading: Points to architecture and API documentation to accelerate onboarding and debugging.
  • Use Case: When joining a monorepo, use this Skill first to find entry points, routers, and API maps before making changes.

Quick Start

Use the navigator skill to locate backend routers and frontend pages for a given feature and summarize the key file paths and documentation to read.

Frequently Asked Questions about navigator

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

FAQPage Schema
How do I locate backend routers and frontend pages in an unfamiliar monorepo?

To locate backend routers and frontend pages in an unfamiliar monorepo, use codebase orientation techniques to provide direct paths to common locations and summarize key file paths for developers during onboarding.

What is codebase orientation and when do I need it for project navigation?

Codebase orientation is the process of understanding project structure and locating important files. You need it when navigating unfamiliar repositories during developer onboarding, debugging, or feature development to eliminate time spent scanning.

How do I find API flow mappings and design specs in a large web application?

You can find API flow mappings and design specs in a large web application by applying file discovery techniques that point toward architecture and API documentation to accelerate onboarding.

What's the best way to get project orientation before making changes to a codebase?

The best way to get project orientation before making changes is to locate entry points, routers, and API maps first. This provides concise navigation instructions and targeted file locations for feature development.

Do I need architecture documentation to navigate an unfamiliar repository?

Yes, you need access to architecture documentation and repository file paths. These predefined quick paths are required to produce concise navigation instructions and targeted file locations during onboarding.

Codebase navigation not working for my monorepo, what are the limitations?

Codebase navigation limitations include requiring predefined quick paths and architecture documentation. Without repository file paths and API flow mappings, it cannot produce targeted file locations for monorepos.