agent-notepad-map

Organize .codex/notes taxonomy into a navigable memory tree.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/MithrilMan/neomithril-ui --skill agent-notepad-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-notepad-map
Source: https://github.com/MithrilMan/neomithril-ui/tree/main/.codex/skills/agent-notepad-map
Command: npx skills add https://github.com/MithrilMan/neomithril-ui --skill agent-notepad-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize the note taxonomy within .codex/notes into a navigable memory tree to maintain discoverability as the project grows.

Core Features & Use Cases

  • Incremental restructuring: propose and apply the smallest structural changes (new branch folders, sub-branches, or file renames) to relieve pressure.
  • Index maintenance: update all affected INDEX.md links to preserve navigability.
  • Operational guidance: ensure changes are non-destructive and preserve factual content during moves.

Quick Start

Inspect .codex/notes/INDEX.md, identify structure pressure, and apply the smallest branch split to restore navigability.

Frequently Asked Questions about agent-notepad-map

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

FAQPage Schema
How do I organize notes when a knowledge management branch becomes too crowded?

Restructuring note taxonomy focuses on incremental, non-destructive moves that preserve factual content during file renames and branch splits. It ensures all note content remains intact while applying the smallest structural changes to improve discoverability.

What's the best way to maintain INDEX.md links when refactoring a notes directory?

The best approach is incremental restructuring, proposing the smallest structural changes like new branch folders or file renames to relieve pressure. This method avoids large-scale overhauls by targeting only the areas where note discovery slows.

When do I need to restructure my note taxonomy for scalable growth?

Use this restructuring approach when new domains emerge, branches become crowded, or note discovery slows. It provides operational guidance for minimal structural changes to maintain a navigable memory tree as the project grows.

How do I split crowded note branches without losing existing content?

Restructuring is non-destructive and preserves factual content during moves. It ensures inspection of INDEX.md indexes and propagation of changes to all links, guaranteeing no note content is lost during branch splits or file renames.

Can I rename ambiguous note files without breaking navigability?

Yes, you can rename ambiguous files without breaking navigability by propagating all changes to affected INDEX.md indexes. This ensures the memory tree remains fully navigable and all structural links stay connected.

Why does note discovery slow down as my project grows?

Note discovery slows because branches become crowded and ambiguous as new domains emerge without structural adjustments. Creating new branches and splitting crowded folders relieves this pressure and restores efficient navigability.