project-discover

Generates a progressive-disclosure .rules/ knowledge base documenting unfamiliar codebases for AI agents.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Type3limit/TypeAxSkills --skill project-discover-type3limit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-discover
Source: https://github.com/Type3limit/TypeAxSkills/tree/main/project-discover
Command: npx skills add https://github.com/Type3limit/TypeAxSkills --skill project-discover-type3limit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Onboarding to a new or large repository forces every AI agent session to re-read the entire codebase, wasting context and producing inconsistent understanding. This Skill converts that exploration into a persistent, layered documentation system so agents locate the right module docs in one or two hops. ## Core Features & Use Cases - Progressive-Disclosure Knowledge Base: Builds a tiny always-loaded entry (CLAUDE.md/AGENTS.md) routing to a .rules/README.md index and on-demand per-module docs with load_when triggers. - Parallel Subagent Deep-Reading: Dispatches module-scoped subagents with strict templates to write L2 docs that cite code by symbol name only, never line numbers, and link rather than duplicate existing docs. - Verification & Sweep: Verifies every cited symbol against current source, fixes drift, and runs grep-based sweeps for leftover line numbers, broken links, and BOM issues. - Use Case: You inherit a 200k-line repo and keep re-explaining it to coding agents. Run this Skill once to produce a .rules/ tree, routing README, and updated CLAUDE.md/AGENTS.md entries that every future agent session reads first. ## Quick Start Ask the agent to explore this repository and build a .rules/ knowledge base with routing docs so future agents can navigate it without re-reading all the source.

Frequently Asked Questions about project-discover

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

FAQPage Schema
How do I document a large codebase for AI agents?

Build a progressive-disclosure knowledge base: a tiny always-loaded entry file (CLAUDE.md or AGENTS.md) routes to a .rules/README.md index, which points to per-module docs loaded only when their load_when condition matches the task. Parallel subagents deep-read each module to write the docs.

What is a .rules/ directory for AI coding agents?

A .rules/ directory is a project-local documentation tree combining an llms.txt-style routing index, Cursor-rules-style load_when conditional loading, and Anthropic Skills-style progressive disclosure. Agents read the README routing table first, then only the module docs relevant to their task.

Why should code documentation avoid line numbers?

Line numbers drift as code changes, making citations stale and misleading. Citing by symbol name plus file name (e.g., a class or function name) stays valid across edits and lets agents jump to the code via grep.

Does this work with existing docs in a doc/ folder?

Yes. The recommended mode leaves existing doc/ content in place and only links to it from .rules/ documents, never duplicating content. You can alternatively choose to migrate doc/ content into .rules/ during the initial scoping questions.

Should CLAUDE.md and .rules/ be committed to git?

By default they are added to .gitignore because they work via local disk reads and are treated as local agent configuration. If CLAUDE.md is already git-tracked, removing it requires git rm --cached, which affects the shared repo, so confirm with the user first.