Browse Problems
Discover prompting challenges and the community's best solutions.
Generate retry logic with exponential backoff for flaky APIs
Third-party API fails randomly. Need retry logic: 1st retry after 1s, 2nd after 2s, 3rd after 4s, then give up. Include: max retries, timeout, which errors to retry, which to fail immediately.
Exponential Backoff Retry Generator
Example output
Detect breaking changes in API responses before deploying
You changed the API response structure. Will it break existing clients? Need to compare old vs new response schemas and flag: 'Removed field "user.email" - BREAKING CHANGE'.
API Breaking Change Detector
Example output
Generate OpenAPI specs from existing API code automatically
You built an API without docs. Now you need OpenAPI/Swagger specs. Need to scan the code and generate: endpoints, parameters, request/response schemas, auth requirements.
Code-to-OpenAPI Generator
Example output
Convert Postman collections to integration tests automatically
You have 50 API requests in Postman. Need to turn them into automated tests with assertions: 'POST /users should return 201', 'GET /users/:id should include email field', etc.
Postman-to-Test Converter
Example output
Generate API error messages that developers can actually debug
Generic 'Invalid request' doesn't help. Need: 'Field "email" is required but missing' or 'Amount must be positive integer, got -500'. Error messages should tell developers exactly what to fix.
Actionable API Error Generator
Example output
Detect API rate limit patterns before hitting the limit
Stripe allows 100 requests/second. You're at 87/second and climbing. Need to predict: 'At current rate, you'll hit the limit in 3 minutes' and throttle proactively.
Rate Limit Predictor
Example output
Generate SQL queries from natural language that won't cause N+1 problems
User asks: 'Show me all customers and their orders'. Naive query causes N+1. Need prompts that generate: proper JOINs, eager loading, and explain the performance implications.
hxfg
Example output
Validate webhook payloads before processing to prevent bad data
Stripe sends a webhook. Before processing, need to verify: signature is valid, required fields exist, amounts are reasonable, timestamp is recent. One bad webhook can corrupt your database.
Webhook Payload Validator
Example output