> For the complete documentation index, see [llms.txt](https://docs.hackerfabiitb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackerfabiitb.org/home.md).
# HackerFab IITB Docs
Homepage
Welcome to the technical documentation of HackerFab IITB, India's first student-build semiconductor fab for education!
For information about the team, getting in contact, and recruitment, see our website:
We are gradually documenting our tools, please be patient if a page looks incomplete! Meanwhile, watch our zero-to-one video which explains everything you need to know about setting up a HackerFab:
{% embed url="" %}
We have extensive discussions on Discord: . For example, for doubts about our litho system, post on the `#litho-v1` channel.
We stand on the shoulders of the rest of the HackerFab community, which is thoroughly documented at
Many thanks to Gitbook for supporting educational projects like ours in the form of the Gitbook Community Edition!
---
# 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.hackerfabiitb.org/home.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.