CONTRIBUTING.md

Contributing Guidelines

Thank you for your interest in contributing to the TRAE Rules Project!

How to Contribute

• Open an issue with a clear description of the problem or proposal.
• For pull requests, include a concise summary of changes and rationale.
• Keep the style consistent with existing files and update documentation when needed.

Code & Docs

• Prefer small, atomic changes with clear commit messages.
• Follow the project’s rules documented in .trae/rules/.
• Use SAVEAGG to record session progress when relevant.
• Use DOCUPDATE for technical documentation changes (APIs, CLI, architecture).

Testing & Validation

• If you use TRAE commands during your work, consider saving a validation session with SAVETEST.
• Use LOADTEST to review validation history and TESTREPORT to compile a final report.

Do Not Include

• Sensitive files or credentials (e.g., .env).
• Unnecessary OS-specific files (e.g., .DS_Store).
• Large build artifacts or dependencies (node_modules/).

Licensing

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

Project Structure (high-level)

• README_IT.md / README_EN.md: project overview and usage.
• .trae/: rules, examples, and utilities for TRAE Workflow.
• UPDATE_PR.md: session updates history (generated by SAVEAGG).
• STRUTTURA_PROGETTO.md: technical docs (updated by DOCUPDATE).

We appreciate your contributions—thank you!