[nachocoll]

The multi-file coherence problem that matrixgard points to is the central unsolved challenge in vibe coding platforms. Single-file generation is impressive; maintaining coherent state across a growing project as it diverges from the original context is where most tools break down.

Your approach of reasoning over the existing codebase rather than regenerating is the right architectural instinct. The question is how well you can maintain that context as the project grows in complexity — especially with state management, where the implicit coupling between components tends to multiply.

On the mobile-first question: I think it makes sense for a certain class of projects (simple CRUD tools, internal utilities, one-off automation). For anything with real architectural complexity, you still need the full feedback loop of running locally, testing against real edge cases, and iterating with the kind of depth you can only get at a desktop. That's not a knock on the concept — it's a scope definition.

The Agile Vibe Coding Manifesto (https://agilevibecoding.org) has a principle that feels relevant here: "Code structure reflects the domain — organized around domain concepts rather than technical convenience." Building that structural clarity from a mobile prompt session is the hardest part to get right.