> 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/about-quilter/what-quilter-does-well.md).

# What Quilter does well

A concise summary of Quilter’s recommended applications and optimal design parameters.

Quilter can do a lot, but there are many things it can't do yet. For a complete list of supported physics constraints, see [Physics Constraints](/physics-constraints/overview.md).

### Recommended applications

Right now, Quilter can't typically design or optimize boards as well as skilled humans. 

Quilter's main advantage is speed—it designs boards much faster than humans, can create multiple layouts at once (for different stack-ups, fabricators, and schematic versions), and can thoroughly test whether a design will work as expected through Physics Rule Checks.

Think of Quilter as a junior EE that can support and supplement your experienced layout engineers. (see [Why should I use Quilter?](/about-quilter/why-should-i-use-quilter.md)). This makes Quilter well-suited to tackle the following types of designs:

#### Research & Development

* **IC Evaluation Boards:** Speed up lab testing with early hardware access
* **Design Validation:** Shorten functional validation cycles
* **Connector Breakouts & Harnesses:** Quick turnaround for signal access and subsystem testing

#### Testing & Automation

* **Test Fixtures and Harnesses:** Automate time-consuming internal board testing
* **Environmental Testing:** Create multi-channel IC test and validation boards

#### Time-Sensitive Layouts

* **Schematic-to-Test Workflow:** Skip the layout step in test board development
* **Agile Prototyping:** Iterate quickly with zero layout delay
* **Low-Complexity Designs:** Free up engineering time and avoid layout bottlenecks

### Recommended design parameters

We currently recommend Quilter for the following designs:

#### General specifications

* **<5,000 pins:** Quilter is most likely to generate successful candidates for designs with 5,000 pins or fewer.
* **Low to medium density designs:** Quilter cannot optimize designs better than humans, so very high-density designs (>20% pin density) are best handled manually.

#### High-speed digital designs

* **Signals < 6GHz:** Quilter uses quasi-static approximations to calculate design specifications for impedance-controlled signals, which may not be accurate above 6GHz.

#### **Low voltage**

* **Low-voltage designs (48V or less):** Quilter does not currently support the required physics constraints to manage dielectric breakdown, creepage and arcing for high-voltage designs. We recommend manually separating high-voltage signals before submitting them to Quilter.

#### **Low current**

* **Low-current designs (10A or less):** Quilter is not (yet) designed for very high current applications. When using high current designs, we recommend using pours to to route the net (see "attempt power pour" in the high power comprehension).&#x20;

<br>


---

# 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/about-quilter/what-quilter-does-well.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.