navigator

Navigate codebases by reading architecture docs and predefined quick paths.

28.1k|5.0k|Updated Apr 8, 2020
One-click install
npx skills add https://github.com/srbhr/Resume-Matcher --skill navigator-srbhr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: navigator
Source: https://github.com/srbhr/Resume-Matcher/tree/main/.claude/skills/navigator
Command: npx skills add https://github.com/srbhr/Resume-Matcher --skill navigator-srbhr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New developers and contributors often struggle to quickly understand a codebase's structure and locate relevant files across large repositories.

Core Features & Use Cases

  • Orientation guidelines: Read backend and frontend architecture docs to understand the project layout.
  • Quick paths: Use the predefined directories to jump to core areas like backend routers, frontend pages, and design specs.
  • Use Case: When starting a new feature, quickly map the code organization and locate the relevant modules.

Quick Start

Use the navigator to infer the codebase structure and list key directories. Example: Navigator, show me where the backend routers are located.

Frequently Asked Questions about navigator

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

FAQPage Schema
How do I quickly navigate a codebase and understand its structure?

To quickly navigate a codebase, you can use orientation guidelines that read backend and frontend architecture docs to locate core project files and understand the overall structure without requiring additional tooling.

What's the best way to locate backend routers and frontend pages in a new project?

The best way to locate backend routers and frontend pages is by using predefined quick paths that jump directly to core directories, allowing you to map code organization and find relevant modules fast.

Can I orient myself in a large repository using existing documentation?

Yes, you can orient yourself in a large repository by relying on existing architecture documentation to infer the codebase structure and list key directories for backend and frontend layouts.

Does navigating a codebase structure require installing additional dependencies?

Navigating a codebase structure does not require installing additional dependencies, as it relies entirely on existing docs and predefined quick paths to help you locate files and understand the project layout.

When do I need to map code organization across backend and frontend layouts?

You need to map code organization across backend and frontend layouts when starting a new feature and you must quickly locate relevant modules, design specs, and routers within a large repository.