# Keep a design preview beside useful feedback

Last updated: 2026-10-22

## Put the decision next to the preview

Open the design you are reviewing and the feedback that describes the requested change. Keep them adjacent on the strip. A visual reference belongs nearby when it informs the same decision; unrelated inspiration can wait farther away.

Choose window widths from the content. A responsive preview may need a specific viewport to reproduce a layout issue, while a comment list needs enough room to read a complete sentence. Do not change the preview width merely to make all frames look equal.

## Protect the test conditions

Before editing a visual issue, record the preview's viewport and zoom. If a window manager resize changes the responsive breakpoint, you may no longer be looking at the reported state. Give that preview a predictable size, or keep it floating when a test requires dimensions the managed layout would change.

Now read one comment, inspect the corresponding area, make a small change, and return to the comment. The arrangement succeeds when you can verify the requested behavior without repeatedly searching through unrelated windows. Use a stack for two references only if both remain large enough to inspect.

## Keep inspectors independent when necessary

A color picker, floating inspector or fixed-size utility may not behave like an ordinary resizable document. Test a floating rule instead of forcing it into a narrow shared slot. Check both an existing utility window and a newly opened one.

When the review ends, save the actual design files before changing the desk. A layout profile preserves configuration rather than a version history of the work. The [window rules guide](/en/guides/window-rules) explains exceptions; the [profiles and undo guide](/en/guides/profiles-and-undo) explains which layout changes can be reversed. Keep viewport verification separate from aesthetic preference so a comfortable desk does not invalidate the test.
