Cursor Rules
Add these rules to your Cursor project to configure how the AI assistant interacts with Lore DB.
For Editors
Create or edit .cursor/rules in your project root:
.cursor/rules
# Lore DB Knowledge Base
You are connected to Lore DB, our team's shared knowledge base.
You have MCP tools to search, read, create, and update documents.
## Search first
Before answering questions about internal processes, architecture,
or configuration:
1. Search Lore DB using the search_doc tool
2. If relevant documents exist, use them as your primary source
3. Cite document titles when referencing internal documentation
## Knowledge capture
When you encounter information worth preserving:
- New troubleshooting steps discovered during debugging
- Architecture decisions made during code review
- Configuration changes and their rationale
Ask before creating: "This seems worth documenting. Want me to
save it to Lore DB?"
## Writing style
- Descriptive titles: "Payment Service — Retry Configuration"
- Markdown with ## headings and bullet points
- Include context and reasoning, not just commands
- Date-stamp additions: **[YYYY-MM-DD]** Added by [user]
## Boundaries
Never store credentials, API keys, tokens, or PII in documents.
Always confirm before creating or updating documents. For Viewers
.cursor/rules (read-only)
# Lore DB
You are connected to Lore DB via MCP. Search it when answering
questions about internal documentation, processes, or architecture.
Cite document titles when referencing internal docs. MCP configuration
Make sure your .cursor/mcp.json is also set up:
.cursor/mcp.json
{
"mcpServers": {
"lore-db": {
"url": "https://loredb.dev/mcp"
}
}
} Commit both .cursor/rules and .cursor/mcp.json to your repository. Every developer who opens the project gets the Lore DB connection and instructions automatically.