coding-edit

To fix visual drift without broad rewrites, apply surgical edits to existing components in your src/ directory. This approach enforces minimal changes and hard boundaries to correct misalignment while preserving public interfaces and routing.

No, you cannot use this to add new routes or wire backends. It enforces safe boundaries by prohibiting the creation of new pages, focusing strictly on in-place tweaks and drift correction for existing UI elements.

The best way to prevent regressions during surgical frontend edits is using a validation-first workflow. Automatically run typecheck, lint, and targeted UI verifications after patching existing components to ensure behavior alignment.

Yes, this UI edit workflow supports modifying existing pages in your current repository. It targets existing components or routes within src/ to apply surgical tweaks, alignment corrections, and behavior mismatch fixes.

You should avoid surgical edits when your frontend task requires creating new pages, wiring backends, or broad architectural rewrites. This method is strictly designed for minimal, in-place patches to correct existing UI behavior.

Surgical UI editing in frontend code maintenance is the process of making minimal, in-place patches to existing components. It targets visual drift, misalignment, or behavior mismatches in src/ without creating new routes or performing broad rewrites.