> 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/fabricator-constraints.md). # Fabricator constraints Overview of Quilter’s fabrication rules, detailing how they define geometric constraints for manufacturability and ensure compliance with fabricator capabilities. ### Overview Fabricator constraints are a subset of the overall constraints that define the minimum geometric thresholds a fabricator can apply when manufacturing your circuit board. Specifically, Quilter's fabrication rule profiles include the following: * Minimum trace width * Minimum trace clearance * Minimum drill hole size * Minimum annular ring size * Minimum edge-to-copper clearance ### How Quilter uses fabrication rules These are the **absolute minimums** that your fabricator will allow. Any smaller dimension defined later, including by specifying a netwidth, will be ignored or will generate a DRC violation. ### How to specify If using your own stackup, these will be read from your ECAD files. When using a Quilter stackup, these will be part of that definition. In the Quilter app, you can double click a value to edit it. --- # 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/fabricator-constraints.md?ask=&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.