in software development, we should conduct tests and ensure everything is covered and passes 100%. the same applies to life... every day is a test case that we should pass. the way you live your life affects the world and determines your success in the afterlife
The main issue with current vibe coders is redundancy. AI agents currently can't get the full context of the codebase. Unless you're a programmer who knows the code and workflow of the project, you can tell them through prompts when starting vibe coding, such as "you should create this class, this db with this structure, and reuse these functions, and the result should be like this," etc.
Building a codebase indexing mcp for claude code seems interesting. It would work like this:
1. MCP tools: `codebase_search`
2. Config: Qdrant (for vector DB), path to codebase
3. When `codebase_search` is called, it will run claude code again internally to search the codebase code snippets and get summaries (so we can save window context tokens rather than blindly returning many search results to the main claude code session)
4. When done, the mcp will give results with a more meaningful message to the main session
Let me know if you have any information about whether this workflow already exists or not