Rust_Julia_FFI_Flutter_Template

Change-aware quality pass: diff scope, readability, function size and control flow, comments where non-obvious, and alignment with project linting. Use before merge or with handoff when the user wants industry-style maintainability beyond what tests assert.

Review code changes for correctness, security, project conventions, and maintainability. Use when reviewing a diff, before commit, or when the user asks for a code review.

Receiving-agent protocol. Boots a new agent into the minimum correct context (select + isolate) and produces a clear next-step plan without guessing.

Define and maintain lightweight evaluations (acceptance criteria, regression checks, golden tests) so "green" is objective and repeatable.

Validates a game or interactive product for playability, clarity, feedback, and scale-readiness. Use at milestones, before large scope changes, or when the user asks if the product feels ready or is ready to scale.

Short-lived feature branches; TDD + lint + merge-ready command as exit criteria before commit; push and merge to main (or user-directed flow). Do not default to asking the user to open a PR. Use when implementing a feature or non-trivial fix, when the user asks for branch/git workflow, or after substantial edits that should not stay uncommitted.

Operating model for disciplined agent work: stay on scope, avoid guessing, decompose work into verifiable chunks, and keep context lean and durable.

Evidence-driven debugging/incident workflow: reproduce, isolate, minimize, fix, verify, and prevent regressions.

Project management and governance. Use when planning sprints, making scope decisions, enforcing quality gates, or identifying risks.

Establish lightweight release discipline: definition of merge-ready, versioning/changelog habits, and safe rollout/rollback practices.

Maintain a lightweight risk register (top risks, triggers, mitigations, rollback) to prevent scope drift and improve decision quality.

Lightweight security review for agent work: secrets hygiene, safe logging, least privilege, and threat-model-lite checks.

Leaving-agent protocol. Produces a compressed, decision-first handoff that preserves intent and next steps while stripping execution noise.

Assess and prioritize technical debt (code, architecture, tests, docs, performance). Use when planning refactors, sprint planning, or evaluating codebase health.

Technical leadership: turn plans into sequenced work, clarify definition of done, surface risks and dependencies, align tests and CI with scope, and coordinate cross-cutting changes (storage, messaging, APIs). Use when the user asks for a tech lead, implementation plan, story breakdown, risk assessment before a large change, or merge ordering across epics.

Creates and edits project documentation for both public and internal audiences. Use when writing or updating README.md, AGENT_HANDOFF (or AGENTS.md), CONTRIBUTING, or internal docs (e.g. PM_PLAN, DEV_GUIDE, TEST_TDD, DESIGN_SYSTEM). Covers structure, tone, and what to include for each doc type.

Black-box tests, test-first for core logic, and continuous test runs. Use when adding or changing tests or app logic. Run flutter test after changes; keep suite green.

UI/UX review and alignment. Use when writing or reviewing screens, animations, haptics, layout, or design tokens; or when adding/changing UX to match project requirements and accessibility.

Match UI graphics to reference examples (examples/ screenshots and specs). Use when drawing or changing visuals so the result matches the examples without back-and-forth.