Flux Knowledge Base
Flux Knowledge Base allows you to teach Flux how you work—once, and it remembers forever. This persistent memory system helps Flux retain your design preferences, best practices, and project-specific guidance across conversations.
{% image url="https://uploads.developerhub.io/prod/86Yw/vrr84c95td63sdqu8rsb8r5wz2sy1r0hvztip82myxu7dwjdyosb6sz1xhbtwfu0.png" mode="responsive" height="1124" width="2000" %} {% /image %}
Overview
The Knowledge Base feature enables Flux to automatically apply your design context during conversations without requiring you to repeat the same instructions. Whether it's your preferred components, naming conventions, review checklists, or layout guidelines—Knowledge Base helps Flux work like someone who's been on your team for years.
What is Knowledge?
Knowledge is persistent memory for Flux that stores information about how you design, allowing it to apply that context automatically during conversations.
You can save Knowledge about:
- Preferred components or manufacturers
- Naming and labeling conventions
- Derating protocols
- Testing protocols
Each Knowledge entry includes:
- A summary of the instruction
- When it should be used (its "trigger")
- Where it applies (user-wide or project-specific)
Knowledge entries are automatically suggested based on your conversations but can also be created manually.
How Knowledge Works
Getting Started with Knowledge
- Open a project in Flux
- Interact with Flux normally.
- Look for Knowledge suggestions—and start teaching.
You can also add Knowledge manually from your profile or the project sidebar:
Automatic Suggestion Generation
As you chat with Flux, it listens for teachable moments in your conversations. For example:
Flux will then suggest turning these statements into Knowledge entries.
You'll see suggestions in the Knowledge tab, where you can:
- Accept (save it as-is)
- Edit (customize the wording or trigger)
- Reject (ignore or dismiss)
Once accepted, Flux will reference that Knowledge automatically when relevant to future conversations.
Where Knowledge Lives
Knowledge entries can be stored at two different levels:
User-Level Knowledge
Stored in your profile and applied across all your projects. Ideal for:
- Personal preferences
- Naming conventions
- General workflow habits
{% image url="https://uploads.developerhub.io/prod/86Yw/fnie7mip41p1pmiu0lga1m1z9pos5p51katp6yz08d2te7mqxo3r3wrjbdccmgzo.png" mode="responsive" height="1124" width="2000" %} {% /image %}
Project-Level Knowledge
Tied to a specific Flux project. Ideal for:
- Project-specific constraints
- Unique design rules
{% image url="https://uploads.developerhub.io/prod/86Yw/m8e2gmv7r3youdc80gpytay7502krzzz5m9izlg0gg02hcvwubfuo3fypusjzc8x.png" mode="responsive" height="1424" width="2532" %} {% /image %}
Project-level Knowledge takes precedence over user-level Knowledge when both apply to the same situation.
Example Use Cases
Here are a few ways you might use Knowledge:
| Scenario | Knowledge Entry |
|---|---|
| You always use TI boost converters | "When selecting voltage boosters, prefer Texas Instruments." |
| You use a specific test point label format | "Use TP_ prefix for all test point nets." |
| Your team has a DRC-first layout policy | "Always run DRC before starting layout." |
| You want Flux to avoid certain part families | "Avoid recommending parts from ABC123 series." |
Using Knowledge in Conversations
When Flux uses a Knowledge entry in a response, you'll see a reference under the "Accessed Knowledge" section in the chat. You can click to view which entry was used, and make edits if needed.
This builds trust—and lets you fine-tune how Flux applies your expertise over time.
{% image url="https://uploads.developerhub.io/prod/86Yw/rr3uarc5sb472nzzxdwnzbq3n9xohhgqw13dq07gnw1nbrz5f6lkyvd642hcmdwp.png" mode="responsive" height="768" width="1366" %} {% /image %}
You can disable specific Knowledge entries temporarily without deleting them if you don't want them to apply to a particular conversation.
Best Practices
Think of Flux like onboarding a new team member. The better you teach it, the more helpful it becomes.
- Start small. Save preferences you often repeat.
- Set clear triggers. The more specific, the better the match.
- Keep it organized. Use project-level entries when information isn't universal.
- Review and prune. Clean up entries as your workflows evolve.
What's Next
- Getting Started with Flux - Learn the basics of using Flux in your workflow
- Adapt Flux to Your Goals - Customize Flux for your specific design needs
- Flux Use Cases - Discover different ways to leverage Flux in your workflow
- AI for Hardware Design - Understand how AI can enhance your hardware design process