Contributing to Celerix Toolbox

First off, thank you for taking the time to contribute! It is people like you who make Celerix a better tool for everyone.

As a privacy-first, high-performance project, we have a few specific guidelines to ensure the application remains lean, fast, and secure.

🛡️ Our Privacy Manifesto

Before contributing, please remember:

No Telemetry: We do not accept features that require tracking, analytics, or external data collection.
Local First: Features should work offline whenever possible. If a tool requires internet access (e.g., a Brewster/API tester), it must be opt-in and transparent.
Data Sovereignty: User data must stay on the user's machine.

To maintain our "Performance Engineering" pillar, we follow these rules:

Rust Backend: Keep the backend logic lean. Avoid heavy crates if a lighter alternative exists.
Vue Frontend: Follow the Composition API pattern. Ensure components are highly performant and don't cause unnecessary re-renders.
Auditability: Write clean, documented code. Since we are privacy-focused, users must be able to easily audit what the code is doing with their data.

We love new "Tools" for the toolbox!
Open an issue with the tag enhancement to discuss the logic before you start coding.
Ask yourself: "Does this tool respect the privacy-first mission?"

Fork the repo and create your branch from main.
Lint your code: Run cargo fmt and npm run lint.
Rust Checks: Ensure cargo clippy doesn't report any warnings.
Description: Explain what your PR does and why it's a good fit for the toolbox.

By contributing to Celerix Toolbox, you agree that your contributions will be licensed under the MIT License.

Thank you for helping us build software that respects users!