> For the complete documentation index, see [llms.txt](https://docs.quilter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quilter.ai/using-quilter/design-your-schematic.md).

# Design your schematic

Concise guidelines for preparing schematics compatible with Quilter, including supported CAD platforms and design best practices.

Quilter's primary function is to design PCBs from your existing schematic. So, **before you can ask Quilter to generate your PCB, you need to have already designed your schematic.** 

Here are a few things to know when designing your schematic:<br>

1. **Supported CAD platforms:**  \
   Quilter is currently compatible with Altium, KiCAD, Cadence Allegro, and Siemens Xpedition. <br>
2. **Use native object classes whenever possible:**  \
   Whenever possible, use supported object classes to help identify important signals such as power nets, differential pairs, and important net classes. This will facilitate Quilter's automatic detection of these constraints during Circuit Comprehension.<br>
3. **Validate your design before submitting:**  \
   Quilter's objective is to faithfully represent the schematic that you provide; we do not automatically verify that your design is free from errors. Before submitting to Quilter, be sure to review your schematic as if you were designing the layout yourself.

{% hint style="warning" %}
**Multi-channel designs**\
Quilter can parse hierarchical schematics, but currently does not support symmetrical layout for multi-channel designs.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.quilter.ai/using-quilter/design-your-schematic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.