Improve architecture Features pile up, and an app that was easy to change gets hard to change. A check-in catches that early: survey, propose, let the user pick, then refactor in small steps that keep behavior the same. The target shape for apps that grow is in architecture.md. When to run Any one signal is enough: - The end of a milestone (the skill calls this skill there). - Before a big feature. Ask: "What change to the code would make this feature easy?" - A Swift file over 600 lines (act at 1,000), a type over 400 lines, or "unable to type-check this expression". - One feature touched mo…