An Android engineering role for native modules, bridge adapters, Android user interfaces, Gradle setup, platform tests, and builds. Android is Google's mobile operating system; a bridge adapter connects Android code with another runtime such as Flutter.
A runtime UI verification agent for apps using Marionette, a tool for connecting to and controlling an app during development. It follows an already approved behavior specification and writes a run report.
A planning agent that turns product requirements, design, protocols, and code evidence into an ordered technical plan and task cards. It stops before writing application code.
An audit and optimization agent for application assets such as images, fonts, icons, animations, and other packaged resources. It checks their usage, format, size, duplication, licensing, and effect on the built app.
An integration role for defining the contract between Flutter, Android, and iOS parts of an application. It specifies the messages, data fields, errors, versions, and lifecycle rules those parts use to communicate.
A read-only code review role for Flutter, Dart, native-platform, bridge, integration, and quality-gate changes. It checks correctness, architecture, resource lifetimes, and missing tests.
A read-only review role for shared capability and wire contracts, documentation, plans, task cards, and their verification evidence. A wire contract is the structured format used when separate parts of a system exchange data.
A read-only review role for the coding-agent system around commands, agents, skills, tasks, validators, test fixtures, evidence, and archived reports. A fixture is a prepared test case, while evidence is the recorded output proving a check ran.
An independent security reviewer for specified tasks and code changes. It examines trust boundaries, sensitive data, external input, dependencies, and changes to an agent's capabilities, then reports evidence-based findings.
An independent auditor that compares a structured UI behavior specification with the production implementation. It marks each step, assertion, and teardown as covered, missing, or wrong using concrete file-and-line evidence.
An implementation role that carries out one existing task card, including the requested code, tests, and validation. It is intended for Flutter, Dart, Android, iOS, bridge, and related project work within the task's stated scope.