- Review the root
README.mdfirst for product context and local run instructions. - Check for existing automation, deployment, and workflow files before adding new ones.
- Keep source changes inside the repo's existing app, package, or service structure.
- Prefer root-level documentation updates only when clarifying setup, architecture, or contributor workflow.
- Use the repo's existing package manager and task runner.
- Prefer small, reviewable changes over broad refactors.
- Preserve current file naming, formatting, and framework conventions.
- Run the lightest relevant verification step available for the repo.
- If the repo exposes lint, type-check, or test commands, prefer those before broader builds.
- Update documentation when behavior, setup, or commands change.
- Avoid destructive rewrites of unrelated files.
- Keep automation and local model tooling additive unless the repo already has a stronger pattern.
- Summarize user-visible changes, validation performed, and any required config changes.