# Contributing

Contributions are always welcome! When contributing to Structure we ask you to follow our code of conduct:

## Code of conduct

In short: *Be nice*. Pay attention to the fact that Structure is free software, don't be rude with the contributors or with people with questions and we'll be more than glad to help you. Destructive criticism and demanding will be ignored.

## Opening issues

When opening an issue be descriptive about the bug or the feature suggestion, don't simply paste the error message on the issue title or description. Also, **provide code to simulate the bug**, we need to know the exact circumstances in which the bug occurs. Again, follow our [code of conduct](/contributing.md#code-of-conduct).

## Pull requests

When opening a pull request to Structure, follow this steps:

1. Fork Structure;
2. Create a new branch for your changes;
3. Do your changes;
4. Write tests for your changes;
5. Check the coverage;
6. Open the pull request;
7. Write a complete description about the bug or the feature the pull request is about.

Be aware that we keep **100% of code coverage**, any change that makes the code coverage less than 100% covered will be requested to write more tests.


---

# Agent Instructions: 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:

```
GET https://structure.js.org/contributing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.