> 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.md).

# About Quilter

- [Why we're building Quilter](https://docs.quilter.ai/about-quilter/why-were-building-quilter.md): An overview of Quilter’s mission to streamline PCB layout through physics-driven automation, enabling engineers to rapidly explore, iterate, and optimize their designs.
- [Why should I use Quilter?](https://docs.quilter.ai/about-quilter/why-should-i-use-quilter.md): Key reasons to adopt Quilter’s AI-powered PCB layout automation, highlighting faster time-to-market, efficient iterative design, reduced errors, and optimized use of engineering talent.
- [How does Quilter work?](https://docs.quilter.ai/about-quilter/how-does-quilter-work.md): An overview of Quilter’s physics-driven approach to automated PCB layout, constraint handling, and validation.
- [What Quilter isn't](https://docs.quilter.ai/about-quilter/what-quilter-isnt.md): An explanation of Quilter’s role as a fully automated layout service, highlighting its workflow, scope, and limitations.
- [What Quilter does well](https://docs.quilter.ai/about-quilter/what-quilter-does-well.md): A concise summary of Quilter’s recommended applications and optimal design parameters.
- [FAQ](https://docs.quilter.ai/about-quilter/faq.md)


---

# 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.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.