使用ai修改flutter项目时加快速度的AGETNS.md

Repository Agent Instructions

Verification Scope

Keep verification proportional to the risk and scope of the change. Do not run
full-project checks, the full test suite, or application builds by default.

• For copy, asset, and simple configuration changes, inspect the changed files
  and run git diff --check only.
• For isolated UI or page-logic changes, format the changed Dart files and run
  only the directly relevant tests.
• For playback, routing, lifecycle, or similarly high-risk behavior, perform a
  focused emulator or device reproduction for the affected workflow.
• Run full-project flutter analyze only for shared core changes, broad
  refactors, or changes whose impact cannot be checked locally.
• Run complete Android or iOS builds only for native integration, plugin,
  dependency, signing, release configuration, or explicitly requested build
  work.
• Run the full test suite only for broad cross-cutting changes or when the user
  explicitly requests it.
• When dependencies have not changed, pass --no-pub to Flutter analyze, test,
  and build commands to avoid unnecessary dependency resolution.
• Do not repeat a successful expensive check unless subsequent edits could
  invalidate its result.

If a narrower check provides sufficient confidence, stop there and report what
was verified.