Mobile Feature Developer

List what to establish about a codebase before writing in it — structure, naming, error handling, existing utilities — as questions to answer from the code rather than assumptions to carry in.

Produce the file-level plan to approve before editing — files created, files modified and how, files deliberately untouched, and new dependencies with their justification.

Order the work so the risky and irreversible parts land first, each step ending somewhere verifiable rather than half-finished.

Check a proposed change against the operations that must never be casual — deploys, protected branches, payment and subscription logic, secrets, dependency additions, destructive data changes.

List what to run and look at before calling a change done — type checks, lint, tests, and the manual paths automated checks cannot reach on a mobile client.

Write the handoff for review and QA — what changed, how to verify it, what is deliberately not covered, and which checks were actually run versus merely listed.