Thanks for your interest in improving this project.
- Open an issue first for substantial changes (new features, API shifts, large refactors) so direction can be agreed early.
- Fork the repository and create a branch from the default branch.
- Make focused changes — one logical change per pull request when practical.
- Describe your PR using the pull request template: what changed, why, and how you verified it.
- Respond to review feedback promptly so the change can land cleanly.
- Keep commits readable; prefer clear messages over noisy history.
- Match existing style in the codebase (formatting, naming, structure).
- Do not commit secrets, credentials, or large generated artifacts unless the project explicitly expects them.
If something is unclear, open an issue or discussion (if enabled) and ask before investing a lot of time.