Flutter: Perch rule pack
2 saved requirements for Flutter. Inspect the selectors and adapt the example paths to your repository.
- name: search-generation-current
where: "lib/order_search.dart"
ensure: >-
In load, both the successful response and the caught-error path return before setState when requestGeneration differs from generation. Each completion path checks requestGeneration != generation together with !mounted. Checking only mounted permits an older request to overwrite the current state.
- name: screen-disposes-owned-work
where: "lib/order_feed.dart"
ensure: >-
dispose must cancel both the stream subscription and periodic timer before calling super.dispose.
Download the rule pack ZIP · Download YAML · Agent repair task · Implementation, integration requirements and captured checks
Install the rule without replacing your configuration
npm install -g @lakeday/perch
perch login
curl -fL 'https://reporules.fyi/flutter/rule-pack.zip' -o 'perch-guide-flutter.zip'
unzip -n 'perch-guide-flutter.zip'Keep your existing perch.yaml. Extraction preserves existing files and adds .perch/rules/perch-guide-flutter.yaml. Review each where selector before running a check on your application.
Configure your coding agent
perch setup claude-code
perch setup codex
perch setup cursor
perch setup piChoose the setup command for the agent you use.
Check the edit, fix the finding, check again
perch check lib/order_search.dart --rules search-generation-current --json
perch check lib/order_feed.dart --rules screen-disposes-owned-work --jsonRun the check after an agent edit. Read the finding and affected code, repair the implementation, and repeat the identical command. Keep the application regression tests as separate gates.
Exit 3 means a finding. Exit 1 or 2 means the check did not complete. A pass does not prove application correctness. Fresh judgments can vary; unchanged requests reuse cached answers. Relevant source is sent to the configured model service.