Full MCP Rules: See
mcp-docs/claude-code/MCP_STANDARD_RULES.mdfor complete documentation access workflowThis repository uses MCP Local RAG for semantic search over [AUTO-DETECT: infer from mcp-docs/ directory structure].
The following variables configure MCP for this repository (referenced in mcp-docs/claude-code/MCP_STANDARD_RULES.md):
{{DOC_TYPE}}: [AUTO-DETECT: Infer from mcp-docs/ subdirectory names or file patterns or ask user if unclear]{{DOCS_DIR}}: [AUTO-DETECT: Find where documentation files are located - typicallymcp-docs/if files are at root]{{SETUP_SCRIPT}}:mcp-docs/claude-code/setup.sh{{MCP_EXTERNAL_PATH}}: [OPTIONAL: Skip unless user specifies]
Available Documentation: [AUTO-DETECT: List unique directory paths containing documentation files, mark others as "(to be added)"]
Supported Formats: PDF, DOCX, TXT, Markdown (.md), HTML
[AUTO-DETECT: Read README.md or infer from repository structure and package names]
[AUTO-DETECT: Discover using ls -la, describe based on directory names and structure]
New team members should set up MCP Local RAG after cloning:
cd mcp-docs
./claude-code/setup.shAfter setup:
- Restart Claude Code
- Documentation files can be auto-ingested on first use
- See
mcp-docs/claude-code/MCP_STANDARD_RULES.mdfor detailed workflow
For detailed information about specific modules, see their individual CLAUDE_CONTEXT.md files.
To discover all module contexts in this repository, use:
find . -name "CLAUDE_CONTEXT.md" -not -path "*/mcp-docs/*"Key module contexts: [AUTO-DETECT: List discovered CLAUDE_CONTEXT.md files, or remove this section if none found]
[AUTO-DETECT: Identify from build files, dependencies, and imports]
[AUTO-DETECT: Extract from README.md or infer from build tool]
- Documentation Access: Always use MCP Local RAG tools (see
mcp-docs/claude-code/MCP_STANDARD_RULES.md) - Module Context: See module-specific CLAUDE_CONTEXT.md files for implementation details
[AUTO-DETECT: Add repository-specific notes if found in README or other docs]