> For the complete documentation index, see [llms.txt](https://docs.lumi-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumi-ai.com/setting-up/configure-knowledge-base/configuration-tips.md).

# Configuration Tips

## Recommended Approach to Configure Knowledge Base

#### Incremental Development

The best, most proven approach is to take an incremental development approach where only necessary fields are added for specific insight group, context is applied, tested and iterated upon.

<mark style="background-color:yellow;">Add Fields -> Contextualize -> Test -> Validate -> Iterate</mark>

This top down approach is superior to the bottom up, "add all and prune" approach as it leads to unused artifacts, confusion, and degraded performance.

We recommend making small incremental context changes, testing and tweaking as needed. This incremental approach ensures greater confidence in the context that you're deploying into production.

## Overall Knowledge Base Best Practices

{% hint style="danger" %}
Enterprise customers can connect multiple tables to the knowledge base, but we recommend limiting it to **no more than 10 tables** for optimal performance.
{% endhint %}

1. **Clarity and Precision:**
   * **Clear Definitions:** Use clear, concise language to define terms and explain methods. Avoid ambiguity to ensure users can easily understand and use the knowledge base.
   * **Avoid Ambiguity:** Ensure that instructions and explanations are precise and unambiguous to avoid misinterpretation when giving Lumi context.
   * **Relevant Terminology:** Add business context for domain-specific terms that are familiar to your audience, ensuring the knowledge base is relevant.
   * **Avoid SQL Keywords:** Ensure that table names and other elements do not use reserved SQL keywords or database-specific terms to avoid technical issues.
2. **Consistency:**
   * **Uniform Terminology:** Use consistent terminology and definitions across all entries in the knowledge base to prevent confusion.
   * **Consistent Naming Conventions:** Decide on naming conventions early (e.g., snake\_case) and apply them uniformly.
   * **Descriptive Names:** Use descriptive names for fields that clearly reflect the content and purpose. This provides more context for Lumi
   * **Avoid Abbreviations:** Unless universally understood, avoid abbreviations and acronyms to prevent confusion.
3. **Validation and Testing:**
   * **Test for Accuracy:** After adding new information, test it to ensure it is accurately understood and applied by users. Adjust based on feedback and outcomes.