// I select this block and type: "Add proper error handling and retry logic"
async function fetchUserData(userId: string) {
  const response = await fetch(`/api/users/${userId}`);
  return response.json();
}

// Cursor transforms it into something like:
async function fetchUserData(userId: string, retries = 3): Promise<User> {
  for (let attempt = 1; attempt <= retries; attempt++) {
    try {
      const response = await fetch(`/api/users/${userId}`);
      if (!response.ok) {
        throw new Error(`HTTP ${response.status}: ${response.statusText}`);
      }
      return await response.json();
    } catch (error) {
      if (attempt === retries) throw error;
      await new Promise(r => setTimeout(r, Math.pow(2, attempt) * 1000));
    }
  }
  throw new Error("Unreachable");
}

"Create a new feature for user preferences. Follow the patterns in @routes/settings.ts 
and @components/SettingsPanel.tsx. The preferences should include notification settings 
(email, push, in-app), theme (light/dark/system), and language. Use the existing 
@lib/db.ts patterns for database access."

# I write:
# Test: verify order total calculation with mixed currencies

# AI generates:
def test_order_total_mixed_currencies():
    order = Order(items=[
        Item(price=10.00, currency="USD"),
        Item(price=8.50, currency="EUR"),
        Item(price=1500, currency="JPY"),  # No decimal for yen
    ])
    with mock_exchange_rates({"EUR_USD": 1.08, "JPY_USD": 0.0067}):
        total = order.calculate_total(target_currency="USD")
        assert total == pytest.approx(29.23, abs=0.01)

## Project: Weel Dashboard
- TypeScript strict mode, no `any` types
- React Server Components by default, client components only when needed
- Use Tanstack Query for data fetching, not SWR or raw fetch
- Tailwind CSS with our design system tokens (see @styles/tokens.ts)
- Error boundaries at route level, toast notifications for recoverable errors
- All API routes use the middleware chain: auth -> validate -> rateLimit -> handler
- Database access through Drizzle ORM, never raw SQL
- Tests use Vitest + Testing Library, prefer integration over unit tests

"Generate a new API route for /api/preferences. Follow the exact same patterns 
as @routes/api/settings.ts — same error handling, same validation approach, 
same response format."