# Agent contribution guide for [PROJECT NAME]

Template: adapt this file to the repository and chosen agent client. Replace every
bracketed placeholder. Link it from the README and confirm how your client reads
repository instructions; file support and precedence depend on the client.

## Objective

[Explain what the project does and where its current priorities are documented.]

## Read first

- README.md for project context.
- CONTRIBUTING.md for setup, checks, contribution policy, and review.
- [Relevant architecture or area-specific instructions.]

## Repository map

- [Path]: [purpose].
- [Path]: [purpose].
- [Path]: [tests or verification relevant to common tasks].

## Working on a task

- Confirm the user's objective and authorized scope.
- Check for existing issues, pull requests, or relevant decisions before starting.
- Inspect the code and guidance for the area being changed.
- Keep the change focused on the agreed completion condition.
- [List changes that require maintainer coordination, such as migrations or APIs.]
- [Explain any generated files or directories with special editing procedures.]
- Ask a focused question when a required decision cannot be inferred from the
  current project guidance and implementation.

## Verification

Follow the actual commands in CONTRIBUTING.md and any area-specific guidance.
Report which checks ran, their outcomes, and which checks could not run and why.
Do not describe unrun checks as passing.

## Handoff and review

Summarize the problem, changes, verification, and remaining uncertainty. Follow
the repository's submission process. Maintainers decide what to accept.

These instructions explain the project workflow. They do not provide credentials,
grant additional access, or expand the user's authorization.