> For the complete documentation index, see [llms.txt](https://hard-dev-forge.gitbook.io/hard-dev-forge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hard-dev-forge.gitbook.io/hard-dev-forge/home.md).

# Home

<div data-full-width="false"><figure><img src="https://792879101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F79Ue8NrwBKugWFaqW8Fl%2Fuploads%2FSyIux48ul3upx37kbQ7O%2FHard%20Dev%20Forge%20Transparent%20Logo.png?alt=media&amp;token=a83b2b7f-f5c4-47a3-be29-015a8d931d05" alt="" width="375"><figcaption></figcaption></figure></div>

### About

We forge easy to use tools to make developers' lives easier.

### Mission

1. **Clean Code** - Our team of experienced developers delivers readable, maintainable, production-ready code you can confidently build on. No hacks, no spaghetti, no surprises.
2. **Clear Docs** - We won't make you read a 40-page boring word document. Our docs are clear, concise, and focused on getting you productive fast.
3. **Real Devs** - These tools aren't generated by AI or rushed templates. They're forged by real developers, tested in real projects, and built to solve real world problems.

#### Contact

📩 <harddevforge@gmail.com>

Please contact us before leaving a review, so we can help you as soon as possible!


---

# 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://hard-dev-forge.gitbook.io/hard-dev-forge/home.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.