We welcome contributions! Please follow these guidelines to help maintain quality and consistency.
- Be respectful and professional.
- Avoid duplicate PRs; check the issue tracker first.
- Fork the Repository: Clone it to your local machine.
- Create a Branch: Use a descriptive name like
feat/new-themeorfix/paddle-collision. - Write Code: Follow existing conventions and ensure clean, maintainable architecture.
- Write Tests: Add unit tests for logic and end-to-end tests for UI changes.
- Update Docs: Modify the user manual or README if necessary.
- Submit a Pull Request: Provide a clear summary of your changes and cross-reference relevant issues.
- Style: Use TypeScript and React hooks.
- Testing: Maintain at least 80% coverage for new features.
- Documentation: All new features must include functional analysis and technical documentation.
If you have suggestions or find a bug, please open an issue on the GitHub repository.