December 4, 2023
If this sounds interesting to you and you'd like to request a demo or learn more, please contact sales.
It’s tempting to think that LLMs are able to read our minds, but in practice, that’s far from the truth. While Copilot is surprisingly good at filling in the blanks when you ask it a question, to get the best results, you need to ask the best questions. Imagine you’re onboarding a coworker. The more detail and context you provide the new employee, the faster they’ll get up to speed and the more productive they’ll become.
We want to make this process as easy as possible for all Flux users. So, after hundreds of hours of testing and talking to dozens of real users, we’ve put together six prompting tips that will help you get the most out of Copilot. Read on to learn more!
When it comes to LLMs, what you put in is what you get out. So if you want clear and detailed answers, you need to make sure that you provide Copilot with descriptive prompts. When you let Copilot know your goals, constraints, or more details about what you want to build - it can give better answers.
Here’s an example of a “bad” and “good” version of the same prompt:
Bad:
@copilot what’s the best IMU for this project?
Good:
@copilot can you recommend a suitable IMU for this project? I want to keep overall board power consumption below 1A. This is an automotive design, so all components must also be ASIL-D certified. I’m also on a budget, so the total BOM must be less than $2.00.
The best way to give Copilot context is to use Copilot Presets. A powerful new feature that allows you to declare project requirements like operating temperature, voltage, or compliance standards. They are the go-to way to help Copilot understand the full context of your project.
A good prompt is also specific. Don’t just ask Copilot for help finding a component; tell it what factors it should consider so that it knows your criteria.
Bad:
@copilot review my decoupling capacitors
Good:
@copilot list all ICs and the decoupling capacitors attached to each. Ensure to include all ICs present in the design, including digital ICs, power converters, LDOs, etc. For every IC, clearly state:
• What power net the decoupling capacitors are attached to. What is the stated voltage of that net?
• The voltage rating and value of the attached decoupling capacitors.
Another tip here is to mention components explicitly by their component designator so that Copilot knows exactly which components you’re referring to. For example,
Bad:
@copilot what is the operating voltage of my microcontroller?
Good:
@copilot what is the operating voltage of U1 in my project?
Copilot is a text-based assistant, but that doesn’t limit what kind of responses it can give you. Users can prompt Copilot to respond in a variety of different ways, including tables, LaTeX, code blocks, and markdown formatting.
Also, many users might not know that Copilot can even output files for you—if you know how to ask! For example, you can ask Copilot to produce a CSV of your project BOM for you with a prompt like the following:
@copilot can you generate a BOM for this project in a CSV format?
With unique output formatting, Copilot’s responses can more easily integrate into your workflow.
First off, a good prompt is one that is technically accurate. If your question doesn’t make sense, then the response is likely to be inaccurate as well.
Here’s an example of a technically “bad” and “good” version of the same prompt:
Bad:
@copilot how do I choose the right material for a PCB?
Good:
@copilot what are the key considerations when choosing the right dielectric and stackup for a PCB?
Fortunately, you can also use Copilot’s assistance to gauge whether or not your question is technically accurate, and it’ll help you formulate better questions. To get to the good prompt above, you could ask Copilot
@copilot what are PCBs made out of? What are the materials called and why do they vary?
If you’re still not getting the results you want out of Copilot, we have you covered. We provide users with premade Copilot Shortcuts that are accessible through the Copilot Context Menu. Simply right-click on a component or project and choose the prompt you want to use, knowing that it was engineered for the best results possible.
Some options include:
We recently launched a feature called Copilot Experts, which provides you with a set of specialized AI models, each tailored for distinct aspects of hardware design. You can choose which AI model you want to access based on the task at hand, allowing for a more specialized experience that’s tailored to your needs. Right now, our three Expert models are
• Generalist: This is the default Copilot model that you know and love. He’s a jack of all trades who retains the versatility to do anything you need. Try this prompt:
@copilot how does a CAN transceiver work?
• Librarian: This model excels in parts inquiries and navigates datasheets with ease. The next time you have a question about a part, Librarian has got you covered! For example,
@copilot How do I use U1 as a CAN transceiver?
• Help: This is your go-to for Flux product guidance. Have questions about how to use the tool? Don’t feel like sifting through the documentation? Just ask the Help Expert for the answers. You can ask questions like
@copilot How do I connect U1's ground pins to ground?
For the best results with Copilot, make sure you’re working with the right Expert for the job!
Flux is driven by our community, and that means you have a unique opportunity to help make Copilot even better. We’d love for you to participate in pushing the limits of Copilot and share your findings with the community on what works well. If you discover a prompt that’s really impactful, let us know so that we can share it with everyone!
The best way to get involved is to join our Slack channel and share with our community of 2,000 and growing. Together, we’ll change the future of PCB design!