What problem does it solve? Collections that grow without bound (battles, bids, friends, gifts) break fixed-size UI components: a For over the whole list renders too much, and a fixed grid silently drops entries past its last slot. This Skill enforces a single pagination pattern so every player-controlled collection is paged, never drawn whole. ## Core Features & Use Cases - createPager pattern: Uses createPager(items, size, unit?) from src/components/styled/pager.tsx to own the page signal, slice, arrow controls, and the clamp that pulls the page back when the list shrinks. - Standard page sizes: LIST_PAGE (20) for text rows, BOX_SIZE (30) for the six-by-five pokemon box, and GRID_SIZE for the item tray inside ItemGrid. - Grid furniture: Routes pokemon squares through CatchGrid (search, box paging, empty states over CatchBox) and items through ItemGrid, never handing a raw CatchBox an unpaged list. - Use Case: When building a friends list or auction bid history in this SolidStart app, wrap the rows in createPager(() => rows(), LIST_PAGE), render paged.shown(), and place paged.controls() after the list. ## Quick Start Ask the AI to render any growing collection in this SolidJS app through createPager with the correct page size constant instead of a bare For loop.