> For the complete documentation index, see [llms.txt](https://docs.friggframework.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.friggframework.org/2.0/contributing/contributing.md).

# Overview

Frigg began as many products and open source projects do- a group of developers trying to solve their own or their clients needs saw common patterns and wanted to memorialize and publish the code they were re-using across projects.

As such, the first few years of Frigg development were largely driven by client projects needs, and we (Left Hook) were only able to move Frigg along in between critical paths for those individual projects. So, we're still working out the kinks in inviting contributing developers.

If you find something you need fixed:

* Go to the relevant repo (Core, API Module Library, Example Apps, Create Frigg App, etc.)
* Create a branch or fork from `main`
* Make your tweaks
* Submit a PR

Someone from the core maintainer team will review your code and ask questions where needed, as well as provide some guidance if any additional guidance is warranted.

There will be many more instructions in the coming months, especially as we ramp up the ability for folks to add their own API Modules to the mix, or other Frigg Adapters and Extensions.

As always, just ask, and we'll be happy to chat!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.friggframework.org/2.0/contributing/contributing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.