AI Prompt Reference
Log in
Back to library
DevelopmentGPT-5ArchitectureDataPerformance

API Pagination Design

Design stable performant pagination, sorting, and cursors.

API Pagination Design

Prompt

# Role
You are a senior software engineering consultant.

# Task
Generate a professional, directly usable prompt output for "API Pagination Design". Theme: api pagination. Goal: Design stable performant pagination, sorting, and cursors.

# Inputs
Ask me for background, audience, product/project, assets, constraints, success criteria, language, and channel. Prioritize provided facts and do not invent missing details.

# Output Format
1. 问题诊断和假设
2. 分步骤方案
3. 代码/配置/命令建议
4. 验证测试方法
5. 风险、回滚和监控

# Quality Bar
Specific and actionable. Natural and credible. Separate facts, assumptions, and inference. Ask clarifying questions if needed. End with a concise copy-ready version.

# Tracking
Template slug: api-pagination-design

Curated by the editorial team · Updated 06/30/2026 · Model: GPT-5

Usage guide

How to use this prompt

This template is designed for development tasks. Replace the sample details with real constraints before running it in GPT-5.

  1. Step 1

    State the stack, runtime, inputs, outputs, and existing constraints.

  2. Step 2

    Ask for the approach and risks before requesting the smallest verifiable change.

  3. Step 3

    Run tests, type checks, and critical scenarios locally before merging.

Details to replace or add

Specific inputs produce more useful results. Do not submit passwords, private information, or confidential business data.

  • Language, framework, and versions
  • Current code and error output
  • Expected inputs and outputs
  • Compatibility and performance constraints
  • Acceptance test cases

Output checklist

  • The code runs on the specified versions
  • Edge cases and errors are handled
  • Existing project patterns are reused
  • Tests cover critical behavior
  • No new security or performance risk appears

Common adjustments

Provide the directory structure and interfaces when the answer drifts from the project.

Limit files and request staged changes when the proposal is too broad.

Ask for runnable test commands and expected output when verification is unclear.

This prompt separates Development, Architecture, Data, Performance requirements into context, constraints, and output format. Keep the objective fixed and revise only the conditions that failed before rewriting the whole template.

Related prompts

Explore more templates in Development.