What problem does it solve? Designing a "review before commit" screen for bulk data imports often leads to a two-pane pending/confirmed split that disorients users as rows jump between containers. This Skill provides a proven layout pattern — one table, error-grouping banner, cell-level tinting, sticky progress footer — drawn from mature import tools like Flatfile, OneSchema, and Airtable. ## Core Features & Use Cases - Anti-pattern detection: Identifies and rejects the two-pane pending/confirmed split layout that breaks scan order and forces horizontal scrolling. - Concrete layout pattern: Prescribes a single table with problem rows sorted first, clickable error-grouping filter chips, cell-level (not row-level) tinting, and distinct amber/red severity colors. - Safe bulk actions and progress: Requires bulk-fix buttons scoped and labeled to the active filter, plus a sticky footer with live ready-count and a commit action disabled until zero blocking rows remain. - Use Case: When building a bank-statement CSV import where users fix missing categories before committing, apply this pattern so reviewers filter by error type, fix groups of rows, and always see "23 of 30 ready" without scrolling. ## Quick Start Review my import preview screen design and check it against the bulk import review UX checklist before I build it.
