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

# Contribution Guidelines

Please note that this project is released with a [Contributor Code of Conduct](/awesome/web3/awesome-web3/code_of_conduct.md). By participating in this project you agree to abide by its terms.

Thanks for Looking to contribute to this repo. We are happy to see your interest for crafting a great Pull Request for this project.

***

## Guidelines

* Continue to follow the alphabetical ordering that is in place per section.
* Add one link per Pull Request.
* Make sure the PR title is in the format of `Add repository-name` *for e.g.*: `Add awesome-python`
* Use a short descriptive commit message. *for e.g.*: ❌Update README.md ✔Add Git to the CheatSheets
* Search previous Pull Requests or Issues before making a new one, as yours may be a duplicate.
* Don't mention "Awesome" in the repository name while adding a link in the README, if you are adding an awesome repository . *for e.g.*: ❌Awesome-Python ✔Python

## Pull Request Pro Tips

* [Fork](http://guides.github.com/activities/forking/) the repository and [clone](https://help.github.com/articles/cloning-a-repository/) it locally.
* Contribute in the style of the project as outlined above. This makes it easier to understand and maintain in the future.
* Please make sure you [squash](https://dev.to/pb/git-squash-simplified-3ba1) all commits into a single commit before opening a pull request. If your pull request requires changes upon review, please be sure to squash all additional commits as well.

> Thanks you so much for reading the contributing guide. Looking forward to review a great PR from you.


---

# 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.tenten.co/awesome/web3/awesome-web3/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.