Notes · Audit

1. I run the prototype end to end and read every route before changing a line.
2. Mocked APIs, hard-coded data and copy-pasted logic go on the risk list, ranked by what breaks first.
3. Nothing is rewritten yet; the audit decides what is worth keeping.

Notes · Architect

1. Feature modules with clear boundaries, each owning its data, UI and tests.
2. One data model, and one way to fetch, cache and change it.
3. A few conventions, written down, so people and AI agents write code that fits.

Notes · Refactor

1. Behaviour is preserved through every step. Users never notice the rebuild.
2. Small pull requests, each one reviewed and each one leaving the app shippable.
3. AI agents draft the mechanical changes; a human approves every one.

Notes · Harden

1. Tests pin down the behaviour that matters before anyone changes it again.
2. Every screen gets its loading, empty and error states.
3. Accessibility and performance are checked in CI, not after launch.

Notes · Ship

1. Every change ships through a reviewed pull request, with CI and a preview deploy.
2. A handover: architecture notes, decision records and a walkthrough with the team.
3. A well-designed codebase stays maintainable: new features land in days, not rewrites.