Structural changes in the current repo

The current Backbone template gives a concrete meaning to “structural change.” It is not just editing a React file.

A real feature may touch:

  • route registration in App.tsx;
  • a page folder under client/src/pages/;
  • static/dynamic prop types;
  • Zustand state;
  • design-system primitives;
  • ConnectRPC client calls;
  • Rust server modules;
  • SQL migrations;
  • Gherkin scenarios and Playwright tests.

Backspine’s job is to make that structure explicit enough that the agent can modify it without turning the repo into a pile of local improvisations.

[USER: write — the interface for reviewing agent-generated code should show what changed at the architecture/structural level first, with the ability to zoom into a specific implementation. Not a flat wall of diff text.]

Referenced from: backspine hot take — don’t read agent text