chore(docs): add pr template, coc, and contributing guide

Author: SMAKSS

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,56 @@
+# Code of Conduct
+
+## 1. Purpose
+
+A primary goal of @smakss/random-array-element is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe, and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
+
+This Code of Conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
+
+## 2. Open [Source/Culture/Tech] Citizenship
+
+A supplemental goal of this Code of Conduct is to increase open [source/culture/tech] citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
+
+## 3. Expected Behavior
+
+The following behaviors are expected and requested of all community members:
+
+- Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+- Exercise consideration and respect in your speech and actions.
+- Attempt collaboration before conflict.
+- Refrain from demeaning, discriminatory, or harassing behavior and speech.
+- Be mindful of your surroundings and of your fellow participants.
+- Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+
+## 4. Unacceptable Behavior
+
+The following behaviors are considered harassment and are unacceptable within our community:
+
+- Violence, threats of violence, or violent language directed against another person.
+- Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
+- Posting or displaying sexually explicit or violent material.
+- Posting or threatening to post other people's personally identifying information ("doxing").
+- Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+- Inappropriate photography or recording.
+- Unwelcome sexual attention. This includes, but is not limited to: inappropriate touching, groping, and unwarranted comments.
+- Advocating for, or encouraging, any of the above behavior.
+- Stalking or following.
+
+## 5. Consequences of Unacceptable Behavior
+
+Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated. Anyone asked to stop unacceptable behavior is expected to comply immediately.
+
+If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning.
+
+## 6. Reporting Guidelines
+
+If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. @SMAKSS.
+
+Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe.
+
+## 7. Addressing Grievances
+
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the project team with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
+
+## 8. Scope
+
+We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues–online and in-person–as well as in all one-on-one communications pertaining to community business.

.github/CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Contributing to @smakss/random-array-element
+
+First and foremost, thank you for considering contributing to @smakss/random-array-element! Your efforts help make this project better for everyone.
+
+## Getting Started
+
+- Please first discuss the change you wish to make via issue, email, or any other method with the maintainers of this repository before making a change.
+- Ensure that your contribution is in line with the project's coding and documentation standards.
+
+## Pull Request Process
+
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
+2. Update the `README.md` or relevant documentation with details of changes, including:
+   - New environment variables
+   - New database migrations
+   - Any other relevant information
+3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. Ensure your PR has a single purpose. If it addresses more than one issue or introduces more than one feature, split them into separate PRs.
+5. Describe your PR thoroughly. Explain the purpose of your PR, how you approached the problem, and include any relevant information or screenshots for context.
+
+## Coding Standards
+
+- Follow [Javascript specific conventions](https://google.github.io/styleguide/jsguide.html) and @smakss/random-array-element's established coding style.
+- Write tests for any new functionality.
+- Comment your code where necessary.
+
+## Reporting Issues
+
+- Use the provided issue templates if applicable.
+- Be as descriptive as possible. Attach screenshots, logs, or any other relevant information.
+- Check existing issues before submitting a new one to avoid duplicates.
+
+## Code of Conduct
+
+Please refer to our [Code of Conduct](CODE_OF_CONDUCT.md) to understand what kind of behavior is expected within our community.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,48 @@
+<!--
+  ☝️How to write a compelling PR title for @smakss/random-array-element:
+  - Prefix it with [feature], [bugfix], [chore] or other relevant tags (if applicable)
+  - Start with a verb, for example: add, delete, improve, fix…
+  - Specify the main change or improvement, e.g., "add sensitivity adjustment for scroll detection"
+  - Prefix with [WIP] if it's a work in progress
+-->
+
+# WHY is this change introduced?
+
+Resolves #0000 <!-- link to issue or task card if one exists -->
+
+<!--
+  Share context about the problem or feature request.
+  Why is this change beneficial for the users of this hook?
+-->
+
+## WHAT does this PR introduce or fix?
+
+<!--
+  Detailed summary of changes. Indicate if it introduces a new feature, fixes a bug, or makes improvements.
+  Before/after code snippets or explanations are recommended for critical changes.
+-->
+
+### QA Checklist
+
+**Note**: Ensure thorough testing, especially considering interactions with other hooks or components.
+
+- [ ] I have tested this change on multiple React versions
+- [ ] I have verified compatibility with different React setups (e.g., Create React App, Next.js, etc.)
+- [ ] I have added/updated relevant tests, if applicable
+- [ ] I have updated the `README.md` and related documentation, if necessary
+
+### Dependency-specific Checklist
+
+- [ ] Dependencies introduced are lightweight and well-maintained
+- [ ] No known vulnerabilities exist with the introduced dependencies
+
+### Usage-specific Checklist
+
+- [ ] The hook's API remains consistent and user-friendly
+- [ ] Any new features have been documented with clear examples
+
+### Release Notes
+
+**Note**: once this PR is merged, a new release or update might be required for the users.
+
+- Main changes or updates introduced in this release.

Readme.md

@@ -63,3 +63,11 @@ chooser();
 // Result: Foo
 // It will only repeats, once all items within the array are exhausted.
 ```
+
+## Contributing
+
+Interested in making contributions to this project? Please see [CONTRIBUTING.md](https://github.com/SMAKSS/random-array-element/blob/master/.github/CONTRIBUTING.md) for guidelines and details.
+
+## Code of Conduct
+
+We value and prioritize the well-being of all our contributors and users. To ensure that this project remains a welcoming space for everyone, please refer to our [Code of Conduct](https://github.com/SMAKSS/random-array-element/blob/master/.github/CODE_OF_CONDUCT.md).