# Contributing to [PROJECT NAME]

Template: replace every bracketed placeholder before publishing. Use commands
and policies that are correct for this repository. Remove sections that do not apply.

## Objective and current priorities

[Describe the project's purpose and link to the current issue or priorities page.]

## Before starting

- Read the README and any relevant repository instructions.
- Check existing issues and pull requests for overlapping work.
- [Explain which tasks require a maintainer conversation before work begins.]
- Keep each contribution focused on one agreed objective.

## AI-assisted contributions

[State whether AI-assisted contributions are welcome, any task restrictions, and
what disclosure or attribution you expect.]

Contributors are responsible for understanding their changes, checking the work,
and following this project's licensing and contribution requirements.

## Local environment and verification

Supported environment: [runtime, tool versions, operating system considerations].

1. Setup: [actual install/setup command and required services].
2. Run locally: [actual command, if applicable].
3. Focused checks: [actual commands for the changed area].
4. Required checks: [actual test, lint, formatting, or build commands].

[Explain which checks require credentials or external services and how to report
a check that cannot run locally. Do not put secrets in this document.]

## Submit a contribution

[Describe the branch, issue, pull request, or other submission process.]

Include:

- The problem and related issue or objective.
- A concise explanation of the change.
- Verification performed, with results and limitations.
- Relevant documentation, screenshots, or reproducible evidence.
- [Any project-specific disclosure or attribution.]

## Review

[Name the review process and how contributors should handle feedback.]

Submitting a contribution does not guarantee acceptance. Maintainers decide what
to merge according to the project's current priorities and requirements.