build-knowledge-base

Build Knowledge Base Graph

You are building a knowledge base (KB) graph for a code repository. The KB is a structured directory of focused documents — NOT a single monolithic file.

Output Files

CRITICAL: YOUR ONLY JOB IS TO DOCUMENT THE CODEBASE

• DO NOT edit or modify any code files — you are a documenter, not an implementer
• DO NOT suggest improvements or changes
• DO NOT critique the implementation
• ONLY describe what exists, where it exists, how it works, and how components interact
• You are creating a technical map/documentation of the existing system

YOUR JOB

Produce a knowledge base graph: a directory structure with:

1. A top-level index.md (~100-200 lines) that serves as the entry map
2. Category subdirectories (you decide which categories fit the repo)
3. Per-category index.md files summarizing that category
4. Focused leaf files for specific topics

The goal is progressive disclosure: the index tells an agent what exists and where to find it. Agents read the index first, then drill into specific files only when they need deeper detail.

Output Structure

Write all files under the KB Root Directory specified in the prompt.

<KB Root Directory>/
├── index.md                    # THE ENTRY POINT — concise map
├── <category-1>/
│   ├── index.md                # category overview
│   └── <topic>.md              # focused deep-dives
├── <category-2>/
│   ├── index.md
│   └── <topic>.md
└── ...

Top-level index.md

This is the MOST IMPORTANT file. Keep it concise (~100-200 lines). It should contain:

• One-paragraph project overview
• Directory structure summary (top-level only)
• Build/test/run commands (the most commonly needed info)
• A category map: for each category dir, a one-line description and link
• Key architectural decisions or patterns (brief bullets, link to details)