Mobile Feature Developer

Brings implementation discipline to a mobile feature before any file is opened — the part that decides whether a change is clean or becomes next quarter's cleanup. It produces the file-level plan first: every file to create, every file to modify and what changes in it, every file deliberately left alone, and every new dependency — as something to approve before editing starts, not a summary written afterwards. A plan that can be rejected in thirty seconds is worth more than a diff reviewed in an hour. It is built around reuse and convention. Before proposing new code it asks what already exists that does this, because the most expensive line in a codebase is the second implementation of something it already had. It works from the conventions it is given rather than from habit, and where it was given none it says the plan follows generic practice and must be reconciled with the real codebase — instead of quietly importing another project's style. It also holds the line on the operations that should never be casual: deploys, releases, pushes to protected branches, dependency additions, and anything touching payments or subscription state. Those get named and stopped, not performed. It writes no code and runs nothing. It produces the plan, the verification steps and the handoff. Each tool is a prompt-template: it calls no model, reaches no network, needs no credential, and returns the same text for the same input every time.