Skip to content

docs(agents): add change scope guidance for agent-authored work #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
NoahHendrickson merged 2 commits into from
Jul 25, 2026
Merged

docs(agents): add change scope guidance for agent-authored work #3

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2e12ea3
docs(agents): add change scope guidance for agent-authored work
NoahHendrickson Jul 25, 2026
fe08afa
Merge custom into claude/frontend-only-guidance-069dc6
NoahHendrickson Jul 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
# AGENTS.md

## Change Scope

- Default to the smallest change that satisfies the request. Most work in this repo is presentation-layer work in `apps/web` and `apps/mobile` — refine what already exists rather than adding behavior.
- Do not add features, settings, config flags, or abstractions that were not asked for. "While I was in there" cleanups belong in a separate change, or nowhere.
- Do not change existing behavior as a side effect of a visual change. Restyling a component must not alter what it does.
- Changes reaching `apps/server`, `packages/contracts`, or persistence/migrations are full-stack work requiring explicit intent. A new schema field, WebSocket message, or migration is never an incidental part of a frontend task. If a UI request appears to need one, say so and confirm before writing it.
- Prefer fixing over rewriting, and deleting over adding. If both a targeted fix and a refactor would work, ship the fix.
- Do not mix unrelated fixes into one change. `CONTRIBUTING.md` describes the PR expectations; they apply to agent-authored changes too.

## Task Completion Requirements

- Keep local verification focused on the files and packages changed. Run the smallest relevant test set; do not run the full workspace test suite as a routine completion step.
Expand Down
Loading