mateclaw_source_index

Map user questions to MateClaw documentation paths and source code entry points.

839|277|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/matevip/mateclaw --skill mateclaw-source-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mateclaw_source_index
Source: https://github.com/matevip/mateclaw/tree/main/mateclaw-server/src/main/resources/skills/mateclaw_source_index
Command: npx skills add https://github.com/matevip/mateclaw --skill mateclaw-source-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers quickly map user questions to MateClaw's documentation paths and source code entries, reducing time spent blind searching.

Core Features & Use Cases

  • Indexing & lookup: Find the most relevant document or source file by user keywords.
  • Precise path results: Return exact file paths and entry points for questions like "Where is feature X implemented?" or "Where to modify Y logic?"
  • Workflow guidance: Provides quick references to architecture or CLAUDE.md for deeper context.

Quick Start

Ask for the implementation location of a feature and the skill will return the precise path and entry description.

Frequently Asked Questions about mateclaw_source_index

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

FAQPage Schema
How do I find where a specific feature is implemented in a codebase?

Locate feature implementations by mapping user keywords directly to exact source code entry points and file paths. This approach returns precise navigational results and entry-point descriptions, reducing time spent on blind searching.

What is the best way to navigate project structure and architecture documentation?

Navigate project structure by indexing user keywords against documented indices and architecture references. This returns exact file paths and quick contextual access, supporting deeper understanding of the codebase architecture.

How do I locate the exact file path to modify existing logic?

Locate exact file paths for modifying logic by mapping modification queries to source code entries. The system returns precise file paths and workflow guidance, referencing architecture documents to provide deeper context.

Can I use code navigation without prior knowledge of the project structure?

Code navigation works without prior project structure knowledge by indexing natural language questions against documentation paths. It maps user queries directly to relevant source files and architecture references for immediate access.

Why does source reading return inaccurate entry points for my query?

Source reading returns inaccurate entry points when user keywords fail to match indexed documentation paths. Refining query vocabulary to align with architecture documents and feature names improves navigational result accuracy.

When do I need to reference architecture documents during code navigation?

Reference architecture documents during code navigation when deeper context beyond exact file paths is needed. The system provides quick references to architecture docs after returning initial source code entry points for comprehensive understanding.