Use when: any task involves Flutter UI, UX, animation, motion, redesign, image-to-code, or mobile visual implementation quality.
Use when: planning or implementing Flutter local database, cache, offline-read, local datasources, repository cache orchestration, stale data handling, and deterministic tests.
Use when: adding or extending Flutter integration/E2E tests for Beacon with fake backend, ProviderScope overrides, and reusable test robots.
Use when: selecting Flutter test levels, planning unit/widget/integration coverage, and creating verification checklists for risky or cross-layer changes.
Use when: starting a task and loading Beacon source-of-truth context before writing code.
Use when: documenting architecture decisions, tradeoffs, impacts, and rollback guidance after important changes.
Use when: integrating or modifying backend APIs, endpoint contracts, request/response mapping, and business error-code handling in Beacon.
Use when: reproducing and fixing runtime, logic, routing, or state bugs with a root-cause-first workflow.