Choose the safest Composer start for a schema-touching change
Start a Composer run for risky multi-file work with an explicit plan and rollback path.
The change crosses data, API, and UI contracts. What should Jon ask Composer to do first? Ask for a plan with expected files, migration/rollback approach, checkpoint timing, and exact tests before any edit. Right. This uses Composer's agentic strength while bounding risk. The plan turns file editing, terminal checks, and checkpoints into a controlled workflow. Tell Composer to implement the field across the repo and summarize changes afterward. Too late. A summary after a broad edit does not prevent contract drift. The principle violated is planning before high-blast-radius edits. Only edit the admin filter first because it is the visible…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in