meridian-repo-navigation

Route AI tasks to Meridian subsystems using repository navigation references.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-repo-navigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meridian-repo-navigation
Source: https://github.com/rodoHasArrived/Meridian-main/tree/main/.agents/skills/meridian-repo-navigation
Command: npx skills add https://github.com/rodoHasArrived/Meridian-main --skill meridian-repo-navigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meridian’s large, multi-surface architecture makes it hard to quickly find the right subsystem and entrypoints, so this Skill helps you get oriented without getting lost in file-by-file searching.

Core Features & Use Cases

  • Subsystem-first routing: classifies a task to the closest Meridian subsystem and identifies the first projects/contracts/docs to inspect.
  • AI task-to-structure translation: routes requests like “provider bug”, “WPF issue”, “storage regression”, or “MCP tool work” to the most likely owning area.
  • Authoritative-doc guidance: directs you to the generated repo-navigation map and MCP navigation resources/tools when available, before deeper implementation work.

Quick Start

Use the meridian-repo-navigation skill to classify your task and tell me the first 2-3 projects and authoritative docs I should open inside Meridian.

Frequently Asked Questions about meridian-repo-navigation

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

FAQPage Schema
How do I find the right subsystem for a bug in a large multi-project repository?

Subsystem routing resolves your task to the correct Meridian subsystem by reading shared project context and repo-navigation docs, then proposes entrypoints and authoritative documentation that explain execution flow.

What is the best way to orient in Meridian's codebase without searching every file?

Codebase orientation uses generated repository navigation maps and optional MCP navigation resources to classify your task, directing you to the most likely owning area and authoritative docs before deeper implementation work.

How does repository navigation handle MCP tools and multi-surface architecture?

Repository navigation leverages generated navigation references and optional MCP navigation resources to route AI tasks like provider bugs or storage regressions to the correct multi-surface subsystem entrypoints.

Can I use repository navigation for WPF issues and storage regressions in Meridian?

Yes, repository navigation translates AI task requests like WPF issues, storage regressions, or MCP tool work by routing them to the most likely owning subsystem area and identifying relevant entrypoints.

Do I need MCP navigation resources to route tasks to the correct subsystem?

No, MCP navigation resources are optional; the skill satisfies deterministic repo-grounding by reading the shared project context and generated repo-navigation docs to propose correct subsystem entrypoints.

Why does exhaustive file searching fail in large-repo codebase orientation?

Exhaustive file searching fails because large multi-surface architectures contain too many files; deterministic repo-grounding reads shared project context to propose entrypoints and authoritative docs instead of manual searching.