Browse / Learning Documentation / AboutMe Index

AboutMe Index

Accelerates file discovery by mapping project components to their specific purposes using a centralized JSON index.

SkillLearning DocumentationCode SearchProject Management

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Automated index rebuilding and stale header detection
  • Index-based file discovery via purpose-driven headers
  • Dedicated maintenance commands for index health
  • Keyword filtering using jq integration
  • Incremental updates during file edits

Use cases

  • Locating implementation details in large, unfamiliar codebases
  • Finding files by purpose instead of performing slow grep searches
  • Identifying files responsible for specific features like authentication

FAQ

What is the AboutMe Index Claude Code Skill?

AboutMe Index is a specialized developer tool for Claude Code that creates a centralized JSON map of your project files. It maps specific file paths to their functional purposes, allowing for near-instant file discovery without manual searching.

How do I maintain the file index?

Maintenance is largely automated. The index rebuilds on session start and updates during edits, but you can also use dedicated commands like /aboutme-check to find missing headers or /aboutme-rebuild to refresh the entire mapping.

What capabilities does the AboutMe Index provide?

The skill provides automated index rebuilding, stale header detection, and jq-powered filtering. It also features incremental updates, ensuring your project map stays current as you edit files during a session.

How does this skill improve my AI coding workflow?

It streamlines the 'discovery phase' of coding tasks. By providing Claude with a purpose-driven index, the AI spends less time scanning irrelevant files and more time performing actual development, code reviews, or bug fixes.

When should I use this skill instead of standard search tools?

You should use this skill whenever you need to find files based on features, intent, or logic (e.g., 'which files handle login?') rather than exact text matches. It is significantly faster and more accurate than using grep or the Explore agent for architectural discovery.