| name | knowledge-search |
| description | Teaches how to use Bluera Knowledge for accessing library sources and reference material. Explains two approaches - vector search via MCP/slash commands for discovery, or direct Grep/Read access to cloned repos for precision. Shows when to use each method and example workflows for querying library internals. |
Using Bluera Knowledge (BK)
BK provides access to definitive library sources for your project dependencies.
Purpose: Authoritative References, Not Project Search
CKB is for: Reference material and external sources
- Library sources: Clone Vue.js/Pydantic/Hono for authoritative API reference
- Specifications: Add project requirements, API specs, RFCs
- Documentation: Add design docs, architecture guides, research papers
- Reference material: Best practices, coding standards, examples
CKB is NOT for: Searching your current project code
- Use Grep/Read directly on project files
- BK stores are for external reference material
Two Ways to Access Library Sources
1. Vector Search (MCP or slash command)
Find concepts and patterns across library docs:
search("vue reactivity system")
/bluera-knowledge:search "pydantic custom validators"
2. Direct File Access (Grep/Read)
Precise lookups in cloned library source:
Grep: pattern="defineReactive" path=".bluera/bluera-knowledge/repos/vue/"
Read: .bluera/bluera-knowledge/repos/pydantic/pydantic/validators.py
Both Are Valid!
You can use either or both approaches on the same cloned repo:
- Vector search to discover relevant files
- Grep/Read to find specific functions/classes
- Or just Grep/Read if you know what you're looking for
Example Workflow
User: "How does Vue's computed properties work internally?"
Claude:
- Check stores:
list_storesMCP tool → vue store exists - Vector search:
search("vue computed properties")→ finds computed.ts - Read file:
.bluera/bluera-knowledge/repos/vue/packages/reactivity/src/computed.ts - Grep for implementation: pattern="class ComputedRefImpl"
- Explain with authoritative source code examples