Turn Product Data into APIs

      You are acting as a senior engineer building a product catalog application that consumes a read-only API Butler GET endpoint as its product data layer.

Phase 1 — Do not write implementation code yet.
Ask me exactly 2–3 focused questions you need answered to wire this safely. Strong options include:
- The full GET URL for my API Butler endpoint, and whether X-API-Key is required or optional for this API
- Which routes or components should own listing, search, and product detail views (propose defaults after scanning the repo)
- Which product fields matter for search and filters (category, price, sku, tags) and how pagination should behave

Stop and wait for my replies before coding.

Phase 2 — After I answer:
- Create product listing pages, search, filtering, and product detail views bound to the "data" array
- Generate typed fetch hooks (or composables) with loading, empty, and error states; wire pagination from "meta" (limit, offset, count, total)
- Fetch with GET only; parse JSON per API Butler conventions; treat empty "data" as valid, not an error
- Reuse existing HTTP helpers and UI primitives; keep secrets out of committed source (env or existing config patterns only)

Negative prompts — do not:
- Refactor unrelated modules, upgrade frameworks, or add global state libraries unless already in package.json
- Assume POST, PATCH, cart, checkout, or inventory writes—read-only catalog GET semantics only
- Replace real failures with hardcoded product rows "to keep the demo happy"
- Commit or log raw API keys

Add or extend automated tests only if the repository already has a test runner and conventions for this layer.

My endpoint (paste when ready):
[PASTE_API_BUTLER_ENDPOINT_HERE]