Teach Flux Your Team's Standards: Say It Once, and Every Project Follows It

Ana leads the hardware team at a company that makes industrial sensors. Her team has a two-page checklist. It is not in any datasheet, and every new engineer learns it the hard way, in the first design review: 0603 or larger passives, because the assembly house places them reliably. A labeled test point on every power rail. A Tag-Connect footprint for programming. Enclosure walls of 2 mm, because that is what the team's printer does well.

Until now, an AI agent forgot all of this at the end of the chat. Each new project started from zero, and each design review found the same problems again.

Flux remembers. Ana tells the Flux agent each rule once. Flux suggests it as knowledge, she accepts it, and the agent follows it in every project after that. When Jonas joins the team and starts his first board, the board already has the test points, the programming footprint, and the right passives. Nobody had to tell him, and nobody had to tell the agent again.

How it works

1. Say the rule in the chat. For example: "Remember this as a standard for all our projects: put a labeled test point on every power rail."
2. Check the suggestion. Flux shows a knowledge suggestion. It tells you when the rule applies and what the rule is. You can edit the text before you save it.
3. Accept it. The rule is saved, and Flux uses it from now on.
4. Keep working. In the next project, the agent finds the rule when it needs it and applies it. You do not remind it.

Example: test points on every power rail

We told Flux to remember two standards: 0603 or larger passives, and a labeled test point on every power rail. Flux suggested the test-point rule as knowledge, and we accepted it.

Then we opened a new, empty project and asked for something different: "Design a small power board for a sensor node: USB-C 5 V input, a 3.3 V LDO for the sensor, and a 4-pin I2C header." The request does not say anything about test points. The plan from Flux includes labeled 5 V and 3.3 V test points, and the chat shows that the agent read your knowledge before it started.

One rulebook, every role on the team

Each person on a hardware team has rules that the others forget. With Flux, each of them teaches the agent once, and the whole team gets the result.

The assembly engineer: boards that the factory can build

Marco works with the contract manufacturer. He teaches Flux the rules that the factory gives him: "Use 0603 or larger passives. Put three fiducials on every board. Keep parts 5 mm from the board edge." From then on, every board that the agent designs is ready for the assembly line, and Marco stops sending the same comments back.

The firmware lead: the same debug setup on every board

Priya writes the firmware for all the products. She tells Flux: "Every board with a microcontroller gets a Tag-Connect programming footprint and a debug UART on a 3-pin header." Now she can flash and debug the first prototype of every new board with the same cable, on the day it arrives.

The mechanical engineer: enclosures for the team's printer

Lena designs the enclosures. She teaches Flux the limits of the team's printer and the hardware in the drawer: "2 mm walls, 0.3 mm clearance for snap fits, and M3 heat-set inserts for every screw boss." The agent designs each new enclosure for the printer that will make it, and the first print fits.

The compliance engineer: safety rules that are never skipped

Tom checks the products for certification. He tells Flux the creepage and clearance distances for the mains section, and that every mains input gets a fuse and a varistor. These rules apply to every project in the organization, so a new product starts with them.

Purchasing: parts that the team can buy

Sara buys the parts. She teaches Flux the preferred manufacturers for passives and connectors, and the parts that the team does not use any more. The agent picks from the list that she can buy at volume, and the BOM of each new board fits the supply chain that the company already has.

You stay in control

Each knowledge entry has a scope. It can apply to one project, to all your projects, or to your organization. When you save a rule for your organization, everybody on the team gets the same standards.

The rules for all your projects are on the Knowledge page in your profile. Each project also has a Knowledge view for the rules of that project. Edit a rule when it changes, and delete it when you do not need it any more.

Each entry also has a trigger: the type of work that it applies to. The agent uses the rule when its trigger fits the work.

Rules to teach Flux today

• "Remember this as a standard for all our projects: use 0603 or larger passives."
• "Remember for our organization: every board gets a labeled test point on each power rail."
• "Remember for this project: the enclosure must fit in a 120 × 80 × 40 mm space."
• "Remember this as a standard: we use M3 heat-set inserts for all screw bosses in printed enclosures."
• "Remember this as a standard: name nets in upper case, for example VBAT_SENSE and I2C1_SDA."
• "Remember for our organization: every microcontroller board gets a Tag-Connect TC2030 programming footprint."

Try it

Open a project in Flux and tell the agent the one rule that your team repeats in every design review. Accept the suggestion. Then start your next design and see the rule in the result.