How do I install the Project Navigation skill?

Run npx skillmds@latest add gabrielmoreira/project-navigation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Navigation safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Navigation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Navigation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Navigation?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Navigation by gabrielmoreira

Name: Project Navigation
Rating: 4.666666666666667 (3 reviews)
Author: gabrielmoreira

Project Navigation

Navigate this project's Depth-Priority Hierarchical AI-INSTRUCT system. Use when the user asks about rules, conventions, or instructions that govern this codebase — or when you need to find the authoritative source for a topic before acting.

gabrielmoreira Updated Sep 21, 2026 17 repo stars

File contents

Skill: Project Navigation

This project uses the Depth-Priority Hierarchical AI-INSTRUCT system. When asked about project rules, conventions, or where to find guidance, follow this protocol.

Navigation Protocol

Start at the index: Read .ai/index.md
Find the topic: Look for the keyword in the index tables. Entries link at file granularity (not section anchors) because file paths are more stable than headings.
Jump to the section: Open the linked file and use its own ## Contents table to navigate to the relevant section.
Apply the rule: That section is the single source of truth — do not infer, restate, or guess.

Depth Hierarchy

Deeper .ai/instruct.md files override shallower ones. When rules conflict, the deeper file wins.

.github/copilot-instructions.md       ← META only (least authoritative for rules)
.ai/instruct.md                       ← Root (project-wide baseline)
[module]/.ai/instruct.md              ← Module (overrides root for that module)
[module]/[sub]/.ai/instruct.md        ← Submodule (overrides module)

Quick Reference

Need	File
Full topic index	`.ai/index.md`
Naming conventions	`.ai/conventions.md`
Archive / never-delete / never-reset-db	`.ai/maintenance.md`
Credential & .gitignore rules	`.ai/credentials.md`
Project overview & architecture	`.ai/instruct.md` (root)

When Rules Are Silent

If the applicable .ai/instruct.md doesn't address something:

Check parent .ai/instruct.md files going up the tree
Check the global .ai/ files
If still silent → apply the most conservative/safe interpretation
Flag the gap so the .ai/instruct.md can be updated

---name: project-navigationdescription: Navigate this project's Depth-Priority Hierarchical AI-INSTRUCT system. Use when the user asks about rules, conventions, or instructions that govern this codebase — or when you need to find the authoritative source for a topic before acting.---# Skill: Project NavigationThis project uses the **Depth-Priority Hierarchical AI-INSTRUCT** system. When asked about project rules, conventions, or where to find guidance, follow this protocol.## Navigation Protocol1. **Start at the index**: Read `.ai/index.md`2. **Find the topic**: Look for the keyword in the index tables. Entries link at *file* granularity (not section anchors) because file paths are more stable than headings.3. **Jump to the section**: Open the linked file and use its own `## Contents` table to navigate to the relevant section.4. **Apply the rule**: That section is the single source of truth — do not infer, restate, or guess.## Depth HierarchyDeeper `.ai/instruct.md` files override shallower ones. When rules conflict, the deeper file wins.```.github/copilot-instructions.md ← META only (least authoritative for rules).ai/instruct.md ← Root (project-wide baseline)[module]/.ai/instruct.md ← Module (overrides root for that module)[module]/[sub]/.ai/instruct.md ← Submodule (overrides module)```## Quick Reference| Need | File ||------|------|| Full topic index | `.ai/index.md` || Naming conventions | `.ai/conventions.md` || Archive / never-delete / never-reset-db | `.ai/maintenance.md` || Credential & .gitignore rules | `.ai/credentials.md` || Project overview & architecture | `.ai/instruct.md` (root) |## When Rules Are SilentIf the applicable `.ai/instruct.md` doesn't address something:1. Check parent `.ai/instruct.md` files going up the tree2. Check the global `.ai/` files3. If still silent → apply the most conservative/safe interpretation4. Flag the gap so the `.ai/instruct.md` can be updated

Frequently asked questions