iOS simulators MCP

<!-- SPDX-FileCopyrightText: 2024 Industria de Diseño Textil S.A. INDITEX SPDX-License-Identifier: CC-BY-SA-4.0 --> # Contributing Thank you for your interest in contributing to this project! We value and appreciate any contributions you can make. To maintain a collaborative and respectful environment, please consider the following guidelines when contributing to this project. ## Prerequisites - Before starting to contribute to the code, you must first sign the [Contributor License Agreement (CLA)](https://github.com/InditexTech/foss/blob/main/documents/ITX_OSS_CLA.pdf). ## How to Contribute 1. Open an issue to discuss and gather feedback on the feature or fix you wish to address. 2. Fork the repository and clone it to your local machine. 3. Create a new branch to work on your contribution: `git checkout -b your-branch-name`. 4. Make the necessary changes in your local branch. 5. Ensure that your code follows the established project style and formatting guidelines. 6. Perform testing to ensure your changes do not introduce errors. 7. Make clear and descriptive commits that explain your changes. 8. Push your branch to the remote repository: `git push origin your-branch-name`. 9. Open a pull request describing your changes and linking the corresponding issue. 10. Await comments and discussions on your pull request. Make any necessary modifications based on the received feedback. 11. Once your pull request is approved, your contribution will be merged into the main branch. ## Contribution Guidelines - All contributors are expected to follow the project's [code of conduct](CODE_of_CONDUCT.md). Please be respectful and considerate towards other contributors. - Before starting work on a new feature or fix, check existing [issues](../../issues) and [pull requests](../../pulls) to avoid duplications and unnecessary discussions. - If you wish to work on an existing issue, comment on the issue to inform other contributors that you are working on it. This will help coordinate efforts and prevent conflicts. - It is always advisable to discuss and gather feedback from the community before making significant changes to the project's structure or architecture. - Ensure a clean and organized commit history. Divide your changes into logical and descriptive commits. We recommend to use the [Conventional Commits Specification](https://www.conventionalcommits.org/en/v1.0.0/) - Document any new changes or features you add. This will help other contributors and project users understand your work and its purpose. - Be sure to link the corresponding issue in your pull request to maintain proper tracking of contributions. - Remember to add license and copyright information following the [REUSE Specification](https://reuse.software/spec/#copyright-and-licensing-information).