Review tiles: “tile four” must bind to exact pixels and a design version—otherwise engineering and QA argue over different screenshots
`reference-tile-split` breaks long screenshots into citeable panels for Jira, Lark, or Notion (“see r2c4”). Too-small tiles lose context; too-large tiles defeat precision. Dark UI pasted into bright docs loses contrast; design iterations orphan old ticket ids if hashes are not updated. Ship a low-res overview with grid lines and numbers alongside individual tiles; filenames should carry Figma file keys or commit ids. Tickets should link both the ZIP and the master asset, not scattered email attachments.
`reference-tile-split`: choose row-major or column-major once, slice, and ship an indexed overview cover
- Before review, align everyone on whether `r1c1` is top-left zero-based or one-based and ban verbal “middle-left tile” references. If the screen has multiple thematic regions, coarse-block them before fine grids so one ticket does not span unrelated UI.
- After slicing, generate a low-res montage with red grid lines and labels inside the ZIP; individual filenames must mirror those labels. Redact sensitive chrome before cutting so tiny tiles cannot leak more context than intended.
- Ticket templates should require `asset_version`, `split_rows/cols`, `tile_id`, and a cloud ZIP link; closing a bug should attach a fix screenshot tied to the same `tile_id`. When design revs, freeze old tickets against historical versions—never recycle old ids on new pixels.
Review tiling FAQ: coordinate ambiguity, missing context, version drift, doc contrast
Tickets say “row two column three” but engineering fixes the wrong module—how do we kill ambiguity when monitors differ?
Ship a labeled overview PNG (`r2c3` boxes) and require tickets to cite that id only—no relative gestures. On video calls, match zoom levels before debating tile numbers.
Crops are tight for bug focus but developers claim missing environment—how tight is too tight?
Pair the target tile with a 10–20% contextual ring or add a half-scale full-screen inset with arrows. For data tables include headers and filter chips, not only the offending cell.
Figma v47 moves pixels under the same tile id—how do reopened tickets avoid false closes?
Embed `figma_file_key`, `node_id`, or Git LFS hashes in filenames; add a gate that compares exported checksums to the ticket before closure. Historical tickets stay pinned to old bundles instead of silently mapping forward.
Dark-mode UI PNGs paste into white docs as black blobs—what besides the splitter fixes readability?
Deliver light-mat variants or mandate gray code-block backgrounds in the template. Print a monochrome proof to ensure 1px rules survive; never assume everyone has color printers.
Twenty-email threads to find the final ZIP—what beats everyone keeping a random desktop copy?
Use read-only cloud paths like `review/2026-0510-featureX/tiles_v2.zip`, email links plus checksums only, and forbid anonymous `final_final.zip` attachments. Lost assets become a process failure, not QA’s job to re-slice.