- Home
- Skills
- APIs & Backend
- Api Pagination Contract Repairs
More screenshots
Works with the AI tools you already use
Api Pagination Contract Repairs
Repair API pagination contract drift in a repo using Cursor.
$6.99
Api Pagination Contract Repairs
Example session with this skill installed
We switched our customer list API to cursor pagination, but the React table is still sending page numbers and our MSW mocks are breaking. Repair the contract drift in the repo.
- Read your context and instructions
- Compiled the api pagination contract
1. Pagination Contract Decision
Decision: PAGINATION CONTRACT DRIFT FOUND
The route handler uses nextCursor, but useCustomers.ts and CustomerTable.tsx still track pageNumber.
4. Drift Findings
- Request: UI sends
page(Expected:cursor) - Response: UI expects
totalPages(Actual:hasMore) - Mocks: MSW returns offset metadata (Stale)
5. Patch Plan
- Update
customerClient.tsto use cursor params. - Update
useCustomers.tsto handle cursor state. - Align
openapi.yamland MSW handlers. - Add traversal tests to
customer.test.ts.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
API pagination contracts often drift between the backend and frontend. You migrated from offset to cursor pagination, but your UI still expects page numbers, your OpenAPI docs are stale, and your tests are failing or hiding duplicate row bugs.
What it does
- Scans route handlers, controllers, and schemas to identify the canonical pagination contract.
- Detects drift across GraphQL schemas, TypeScript types, API clients, and frontend hooks.
- Identifies risks like missing next tokens, stale total-count assumptions, and duplicate-row bugs.
- Prepares safe repository patches for mocks, fixtures, UI components, and documentation.
- Generates guard tests for first page, end-of-list, and empty result edge cases.
Frameworks & tools
Works with REST, GraphQL, OpenAPI, Apollo, React Query, SWR, MSW, Zod, and Playwright.
Why this beats prompting it yourself
Manually tracing pagination drift across types, mocks, and UI logic is tedious and error-prone. This skill uses a structured register to ensure every layer of your stack—from the route validator to the Storybook story—stays in sync with the canonical contract.
Use cases
- Fixing infinite scroll bugs where rows are duplicated or skipped.
- Aligning frontend hooks and UI components after an offset-to-cursor migration.
- Updating stale MSW handlers and JSON fixtures to match new API response shapes.
- Generating comprehensive pagination tests that cover traversal and boundary conditions.
Known limitations
Does not call live APIs or query production databases. Operations are limited to repository files and user-supplied context.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 1 month ago
- Passed all security checks, Safe to install