feat: repo setup

.eslintignore

@@ -0,0 +1,2 @@
+**/*.js
+tests/testUtils/types.d.ts

.eslintrc

@@ -0,0 +1,3 @@
+{
+  "extends": ["@favware"]
+}

.github/CODEOWNERS

@@ -0,0 +1,5 @@
+# Kyra
+/ @kyranet
+
+# Favna
+/ @favna

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at kyradiscord@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/CONTRIBUTING.md

@@ -0,0 +1,20 @@
+# Contributing
+
+**The issue tracker is only for issue reporting or proposals/suggestions. If you have a question, you can find us in our [Discord Server]**.
+
+To contribute to this repository, feel free to create a new fork of the repository and
+submit a pull request. We highly suggest [ESLint] to be installed
+in your text editor or IDE of your choice to ensure builds from GitHub Actions do not fail.
+
+1. Fork, clone, and select the **master** branch.
+2. Create a new branch in your fork.
+3. Make your changes.
+4. Ensure your linting and tests pass by running `yarn test && yarn lint`
+5. Commit your changes, and push them.
+6. Submit a Pull Request [here]!
+
+<!-- Link Dump -->
+
+[Discord Server]: https://join.skyra.pw
+[here]: https://github.com/skyra-project/skyra/pulls
+[ESLint]: https://eslint.org/

.github/FUNDING.yml

@@ -0,0 +1,12 @@
+# These are supported funding model platforms
+
+github: [kyranet, favna]
+patreon: kyranet
+open_collective: # Replace with a single Open Collective username
+ko_fi: kyranet
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: ["https://donate.skyra.pw/paypal", "https://donate.favware.tech/paypal"]

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,26 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'bug: '
+labels: 'Bug: Unverified'
+assignees: ''
+
+---
+
+**Describe the bug**
+<!-- A clear and concise description of what the bug is. -->
+
+**To Reproduce**
+<!-- Steps to reproduce the behavior: -->
+1. Write '...'
+2. Click on '...'
+3. See error
+
+**Expected behavior**
+<!-- A clear and concise description of what you expected to happen. -->
+
+**Screenshots**
+<!-- If applicable, add screenshots to help explain your problem. -->
+
+**Additional context**
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'request: '
+labels: 'Meta: Feature'
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+**Describe the solution you'd like**
+<!-- A clear and concise description of what you want to happen. -->
+
+**Describe alternatives you've considered**
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+**Additional context**
+<!-- Add any other context or screenshots about the feature request here. -->

.github/SECURITY.md

@@ -0,0 +1,16 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.x     | :white_check_mark: |
+
+## Reporting a Vulnerability
+
+If you find a vulnerability in Saelem's codebase please report it immedetially.
+If you deem the vulnerability exploitable by Skyra's users in any shape or form please join the Discord server at https://join.skyra.pw and then DM either @kyranet (kyra#0001) or @favna (Favna#0001).
+In case the vulnerability is not exploitable by Skyra's users you are free to either:
+
+- Use the GitHub issue tracker to report the issue
+- or join the Discord server through https://join.skyra.pw and use the "#feedback" channel.

.github/labels.yml

@@ -0,0 +1,147 @@
+- name: 'Meta: Examples'
+  description: Issues and PRs related to examples.
+  color: ffff00
+- name: 'Meta: Documentation'
+  description: Issues and PRs related to documentation.
+  color: ffff00
+- name: 'Meta: Github'
+  description: Issues and PRs related to GitHub.
+  color: ffff00
+- name: 'Meta: Refactor'
+  description: Issues and PRs related to refactors.
+  color: ffff00
+- name: 'Meta: Error Handling'
+  description: Issues and PRs related to error handling.
+  color: ffff00
+- name: 'Meta: Feature'
+  description: Issues and PRs related to new features.
+  color: ffff00
+- name: 'Meta: Cleanup'
+  description: Issues and PRs related to code cleanup.
+  color: ffff00
+- name: 'Meta: Dependencies'
+  description: Issues and PRs related to dependencies.
+  color: ffff00
+- name: 'Meta: Bike-Shedding'
+  description: Issues and PRs that nit pick
+  color: f9253a
+- name: 'Bug: Unverified'
+  description: Issues that report unverified bugs. Pending for inspection.
+  color: f9d0c4
+- name: 'Meta: BugFix'
+  description: PRs that fix bugs or issues.
+  color: 4cce4a
+- name: 'Bug: Fixed'
+  description: Issues that report bugs and have been fixed.
+  color: 00fa9a
+- name: 'Event: Hacktoberfest'
+  description: Issues and PRs related to Hacktoberfest.
+  color: FF4500
+- name: 'Bug: Pending Response'
+  description: Issues that report bugs and are pending of a response from the author.
+  color: f9d0c4
+- name: 'Bug: Cannot Reproduce'
+  description: Issues that report bugs that cannot be reproduced.
+  color: f9d0c4
+- name: 'Bug: Fixed in master'
+  description: Issues that report bugs from stable, but that are fixed in master.
+  color: B3E88C
+- name: 'Bug: Confirmed'
+  description: Issues that report confirmed bugs.
+  color: f9d0c4
+- name: 'Bug: Already Fixed'
+  description: Issues that report already fixed bugs.
+  color: B3E88C
+- name: 'Type: Maintenance'
+  description: Issues and PRs related to the maintenance of a module.
+  color: 1d76db
+- name: 'Type: Caching'
+  description: Issues and PRs related to caching.
+  color: 1d76db
+- name: 'Type: Proposal'
+  description: Issues that request a new feature or a change in the api's interface.
+  color: ffffff
+- name: 'Type: Performance'
+  description: Issues and PRs related to the performance of the api's interface.
+  color: 1d76db
+- name: 'Type: Enhancement'
+  description: Issues and PRs related to feature enhancement.
+  color: 1d76db
+- name: 'Status: WIP'
+  description: Issues and PRs that are still a work in progress.
+  color: b60205
+- name: 'Type: Consistency'
+  description: Issues and PRs related to code consistency.
+  color: 1d76db
+- name: 'Status: Needs Testing'
+  description: PRs that need testing from the author or volunteers.
+  color: d93f0b
+- name: 'Status: Stalled'
+  description: Issues and PRs that are being set aside for now for rethinking
+  color: fbca04
+- name: 'Status: Ready To Merge'
+  description: PRs that are ready to merge.
+  color: 05F541
+- name: 'Status: Review Ready'
+  description: PRs that are ready for author review.
+  color: 05F541
+- name: 'Status: Needs Typings'
+  description: PRs that need typings
+  color: d4c5f9
+- name: 'Status: Needs Docs'
+  description: PRs that need documentation
+  color: d4c5f9
+- name: 'Status: Help Wanted'
+  description: Issues that need assistance from volunteers or PRs that need help to proceed.
+  color: 128A0C
+- name: 'Status: Invalid'
+  description: Issues that will not be fixed or PRs that will not merge, e.g. due to backwards compatibility.
+  color: 671df0
+- name: 'Status: Duplicate'
+  description: Issues/PRs that are duplicated.
+  color: d93f0b
+- name: 'Status: Denied'
+  description: Issues or PRs that have been denied by the team.
+  color: bc1202
+- name: 'Status: Changes Requested'
+  description: PRs that have requested changes.
+  color: d93f0b
+- name: 'Status: Blocked'
+  description: PRs that are blocked by other issues/PRs.
+  color: d81a0d
+- name: 'SEM: Patch'
+  description: PRs that contain bugfixes and should be released in the next patch version.
+  color: 66d8eb
+- name: 'SEM: N/A'
+  description: PRs that only contain documentation changes and do not change the api's interface.
+  color: a7f9f3
+- name: 'SEM: Major'
+  description: PRs that contain breaking changes and should be released in the next major version.
+  color: 9a35be
+- name: 'SEM: Minor'
+  description: PRs that contain new features and should be released in the next minor version.
+  color: d38dfa
+- name: 'Priority: Low'
+  description: Issues that must be fixed or PRs that must be finished and merged with low priority.
+  color: 0e8a16
+- name: 'Priority: Medium'
+  description: Issues that must be fixed or PRs that must be finished and merged with medium priority.
+  color: fbca04
+- name: 'Priority: High'
+  description: Issues that must be fixed or PRs that must be finished and merged with high priority.
+  color: d93f0b
+- name: 'Priority: Critical'
+  description: Issues that must be fixed or PRs that must be finished and merged with maximum priority.
+  color: b60205
+- name: 'Type: Typo'
+  description: Issues and PRs related to typos in the documentation or code.
+  color: c5def5
+- name: 'Type: Question'
+  description: Issues that do not belong to the Issue Tracker and should be asked in the official Discord Server.
+  color: cc317c
+- name: 'Type: Dependencies'
+  description: Pull requests that update a dependency file
+  color: 0025ff
+- name: 'Type: Security'
+  description: Pull requests that address a security vulnerability
+  color: ee0701