SkillVaultskills Browse all 500 skills

Architecture · Version 1.0.0 · Reviewed 2026-08-02

Pagination Strategy Advisor

Make a defensible decision about strategy selection and cursor design with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Chooses between offset, cursor, and keyset pagination based on stability, depth, and sort requirements.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Strategy selection
  • Cursor design
  • Deep page performance

How Pagination Strategy Advisor works

You provide

Requirements, constraints, and the current topology

It inspects

Critical path and failure boundaries for strategy selection

It decides

A cursor design decision with consequences recorded

You verify

Rollout stages with the signal that gates each one

What it checks first

Pagination Strategy Advisor chooses between offset, cursor, and keyset pagination based on stability, depth, and sort requirements. Use it when the work involves Strategy selection, Cursor design, Deep page performance.

  1. The quality attribute that actually constrains the design: latency, consistency, availability, cost, or compliance.
  2. The critical path and the number of network hops on it.
  3. Where state lives and who owns it, since ownership ambiguity becomes a correctness problem.
  4. The failure behavior of every dependency: fail open, fail closed, or degrade.

Failure modes it recognizes

  • Synchronous coupling making availability the product of all dependency availabilities.
  • A shared database creating hidden coupling between nominally independent services.
  • A component with no clear owner, so its failure has no defined response.
  • Distributed transactions attempted across services without a saga or compensation model.

Answers it will reject

  • Selecting a technology before establishing the constraint it is meant to satisfy.
  • Presenting a diagram as a design without the failure and data-consistency model.
  • Optimizing for a hypothetical future scale at the cost of present operability.

Decision rules it applies

  • Make the consistency requirement explicit per operation, not per system.
  • Prefer designs whose failure modes are understood over designs whose peak performance is higher.
  • Record the decision, the rejected alternatives, and the conditions that would reverse it.

Evidence it asks for

  • Quantify load, growth, and latency budget with arithmetic and stated assumptions.
  • Define the rollout stages and the signal that gates each one.
  • Name the reversal path for the decision.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to strategy selection.
  2. Trace concrete failure or abuse paths for cursor design; do not report checklist items without a mechanism.
  3. Prioritize deep page performance findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Strategy selection assessment
  • Cursor design decision and action plan
  • Deep page performance verification checklist

Evidence requirements

  • Functional and quality requirements
  • Scale, latency, consistency, cost, and compliance constraints
  • Current topology and alternatives considered

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Our list endpoint slows dramatically past page 200 and users report seeing duplicate items while scrolling.

Expected output

Both symptoms come from offset pagination: the database materializes and discards every skipped row, and concurrent inserts shift the window between requests. Keyset pagination on a stable composite sort key removes both at once...

Boundaries and compatibility

Ideal for

  • Strategy selection: produce a decision or artifact grounded in supplied evidence.
  • Cursor design: produce a decision or artifact grounded in supplied evidence.
  • Deep page performance: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Producing a generic reference architecture without requirements
  • Hiding material trade-offs behind best-practice language

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.