What problem does it solve? List and table views that render unbounded collections without pagination ship slow and degrade as data grows, and retrofitting pagination after release is costly. This Skill ensures every list view is built or reviewed with pagination from the start. ## Core Features & Use Cases - Existing component reuse: Points to the project's existing pagination components — ZardPaginationComponent (app-pagination) for Angular apps and ph-pagination from @arayaroma/photon for Lit/web-component apps — so you copy the established pattern instead of inventing a new API. - Server-side vs client-side guidance: Directs server-side pagination for unbounded DB-backed lists (transactions, bills, backups) and simple client-side slicing only for inherently small, bounded lists. - Convention matching: Enforces the codebase's existing page-size convention (e.g. pageSize = 20 with computed pageCount and paged signals) rather than arbitrary per-view numbers. - Use Case: When building a new transactions page in an Angular app, the Skill flags the missing pagination, points to the app-pagination component used in sibling pages like debts, and provides the exact slicing pattern to apply. ## Quick Start Ask the assistant to review the list view you just built and add pagination following the project's existing pagination component and page-size conventions.
