Let the preview use awkward data
A component preview should include data that makes the layout inconvenient. Short names and matching thumbnails are useful for checking spacing, but they leave many ordinary failures invisible until someone uses the finished screen.
Consider a hypothetical file picker. Its preview shows 6 files named after cities, each with a thumbnail and a short description. Every row fits. Replace one filename with a long export name, remove another thumbnail, and give a third file a description that wraps onto 4 lines. The same component now has to make decisions the original preview never asked of it.
If filenames are truncated, the user still needs enough information to distinguish similar files. Two exports might share their first 60 characters and differ only in a date at the end. Showing the beginning of both names with an ellipsis can make the choice impossible. Keeping the extension and the distinguishing suffix visible may help. The full name should also be available without requiring a mouse hover.
I would keep a small set of awkward examples beside the component: similar names, missing optional fields, very long values, and text in a different writing direction. Each example should have a purpose. A long filename tests identification. Missing metadata tests whether the row still makes sense. A narrow viewport tests which information the layout gives up first.
These examples can become review fixtures. When changing the file picker, open the same set and try to choose a particular file using only the keyboard. Ask someone reviewing it to identify the two nearly identical exports. A screenshot can show whether text overlaps. Trying to select the right file reveals whether the information needed to make that choice survived.