What to Do When Cursor Leaves Code Unfinished

1// Example of a typical mid-stall output:
2
3async function fetchUserOrders(userId: string): Promise<Order[]> {
4  try {
5    const response = await fetch(`${API_BASE}/users/${userId}/orders`, {
6      headers: {
7        Authorization: `Bearer ${getAuthToken()}`,
8        'Content-Type': 'application/json',
9      },
10    });
11    // <-- Cursor stopped here. Error handling, JSON parsing, and return are missing.
12  }
13}

1Complete this function body.
2The try block needs:
31. A check for response.ok — if false, throw new ApiError(response.status, await response.text())
42. Parse the JSON response as Order[]
53. Return the parsed array
6The catch block needs:
7- Re-throw ApiError instances unchanged
8- Wrap other errors in new ApiError(500, error.message)
9Add the ApiError class import at the top of the file if it does not exist.

1# Turn 1 — types only
2Generate TypeScript interfaces for the Stripe API integration at src/types/stripe.ts.
3Only types — no functions. Include: StripeCustomer, StripeSubscription, StripeInvoice, StripeError.
4
5# Turn 2 — client class
6Using @file src/types/stripe.ts, generate the StripeClient class at src/services/stripe-client.ts.
7Only include: constructor (takes apiKey: string), fetchCustomer(id: string), and listSubscriptions(customerId: string).
8Do NOT include error handling yet — just the happy path.
9
10# Turn 3 — error handling
11Using @file src/services/stripe-client.ts, add try/catch error handling to each method.
12Map Stripe API error responses (status 402, 422, 429) to typed StripeError objects.

1# api-integration-context.md
2# Include this with @file when working on the payment integration
3
4## Stripe API endpoints used
5- GET /v1/customers/{id}
6- GET /v1/customers/{id}/subscriptions
7- POST /v1/payment_intents
8- POST /v1/subscriptions
9
10## Shared types (already defined in src/types/stripe.ts)
11- StripeCustomer, StripeSubscription, StripeInvoice, StripeError
12
13## Error codes to handle
14- 402: payment required
15- 422: validation failed (parse error body)
16- 429: rate limited (retry after header)
17- 500: Stripe internal (retry up to 3 times)

1# .cursorrules
2
3## API Integration Style
4- When generating API client code, always create types/interfaces first, then the client class, then error handling.
5- Generate one class or module per prompt — do not generate a full integration in a single request.
6- All API responses must be typed. NEVER use 'any' for API response shapes.
7- All fetch calls must include a response.ok check and throw a typed error if false.
8- Use AbortController for fetch calls that may time out. Pass signal to fetch options.
9- Retry logic must be extracted into a separate retryWithBackoff utility function, not inlined.