AI Prompts

When using RoxyAPI:
- Base URL: https://roxyapi.com/api/v2
- Auth: X-API-Key header from env ROXY_API_KEY
- Never expose the API key in client-side code
- Use the @roxyapi/sdk for typed calls: npm install @roxyapi/sdk
- Reference docs: @Docs RoxyAPI
- All endpoints return clean JSON, errors return { error, code }
- Multi-language: add ?lang=xx (supported: tr, de, es, hi, pt, fr, ru)

## RoxyAPI
- Endpoint reference: https://roxyapi.com/llms.txt
- Base URL: https://roxyapi.com/api/v2
- Auth: X-API-Key header (env: ROXY_API_KEY)
- MCP server: already configured, tools auto-discovered
- Multi-language: add ?lang=xx (supported: tr, de, es, hi, pt, fr, ru)

npm install @roxyapi/sdk

When working with RoxyAPI:
- Base URL: https://roxyapi.com/api/v2
- Auth: X-API-Key header from env ROXY_API_KEY
- Endpoint reference: https://roxyapi.com/llms.txt
- SDK: npm install @roxyapi/sdk for typed calls

Read https://roxyapi.com/llms.txt for the full endpoint reference.
Use the RoxyAPI for all astrology/tarot/numerology data.
Base URL: https://roxyapi.com/api/v2
Auth: X-API-Key header, read from .env (server-side only, never expose to browser)
Build a daily tarot card page that calls POST /api/v2/tarot/daily and displays the card name, image, and meaning.

Read https://roxyapi.com/llms.txt for the full endpoint reference.
Use the RoxyAPI for all astrology/tarot/numerology data.
Base URL: https://roxyapi.com/api/v2
Auth: X-API-Key header, stored in Secrets (use an Edge Function to proxy calls, never expose the key in the frontend)
Build a zodiac compatibility checker that takes two zodiac signs and calls POST /api/v2/astrology/compatibility-score to show the result.

Read https://roxyapi.com/llms.txt for the full endpoint reference.
Use the RoxyAPI for all astrology/tarot/numerology data.
Base URL: https://roxyapi.com/api/v2
Auth: X-API-Key header, read from the ROXY_API_KEY secret (process.env.ROXY_API_KEY)
Build a numerology Life Path calculator that takes a birth date and calls POST /api/v2/numerology/life-path to display the result.

Read https://roxyapi.com/llms.txt for the full endpoint reference.
Use the RoxyAPI for all astrology/tarot/numerology data.
Base URL: https://roxyapi.com/api/v2
Auth: X-API-Key header, read from env ROXY_API_KEY in a server-side API route (never expose to the client)
Build a moon phase widget that calls GET /api/v2/astrology/moon-phase/current and displays the current phase, illumination, and next full moon date.

Build an AI-powered astrology chatbot using Next.js (TypeScript), Vercel AI SDK, and RoxyAPI MCP.

This uses MCP (Model Context Protocol) — the AI auto-discovers and calls RoxyAPI tools during conversation. No manual endpoint integration.

## Reference
- MCP setup: https://roxyapi.com/docs/mcp
- Working template to clone: https://github.com/RoxyAPI/astrology-ai-chatbot
- Endpoint reference: https://roxyapi.com/llms.txt (has MCP endpoint table with all product slugs)

## MCP endpoints
Fetch https://roxyapi.com/llms.txt — it has a table of all product slugs and MCP endpoints.
Protocol: Streamable HTTP (POST only, stateless). NOT SSE, NOT WebSocket.
Auth: pass ROXY_API_KEY as Bearer token or X-API-Key header in MCP transport config.

## How it works
1. Configure MCP client with product endpoints (e.g., https://roxyapi.com/mcp/tarot)
2. AI model receives tool definitions automatically from the MCP server
3. Users chat naturally: "Draw me 3 tarot cards" → AI calls POST /draw
4. Requires a model that supports tool calling (Gemini, Claude, GPT)

## Development rules
- TypeScript, Vercel AI SDK for chat UI + streaming
- Server-side MCP transport (key never reaches browser)
- Dark mode, responsive, message history
- System prompt: tell the AI it has real calculation tools, not to hallucinate readings

Build a complete tarot card reading app using Next.js (TypeScript) and the RoxyAPI Tarot API.

## BEFORE writing any code
1. Fetch https://roxyapi.com/llms.txt to understand all available endpoints
2. Run: npx openapi-typescript https://roxyapi.com/api/v2/tarot/openapi.json -o src/api/schema.ts
3. Install: npm install openapi-fetch
4. Use the generated types for ALL API calls — never guess field names, never use `any`

## API Details
- Base URL: https://roxyapi.com/api/v2/tarot
- Auth: X-API-Key header. Store as ROXY_API_KEY in .env (server-side only, NEVER expose to browser)
- Response format: clean JSON, no wrappers. Errors return { "error": "message" }
- API client setup: import createClient from 'openapi-fetch' and type { paths } from './schema'. Create client with baseUrl and X-API-Key header from env. Every call like api.POST('/draw', { body: { count: 3 } }) is fully typed from the generated schema.

## Available endpoints (all POST except cards)
- POST /daily — daily card with message
- POST /draw — draw N cards { count: number }, returns { seed, cards: [...] }
- POST /yes-no — yes/no oracle reading
- POST /spreads/three-card — past/present/future spread
- POST /spreads/celtic-cross — 10-card Celtic Cross spread with position meanings
- POST /spreads/love — relationship-focused spread
- POST /spreads/career — career guidance spread
- POST /spreads/custom — custom spread { positions: [{ name, interpretation }], spreadName?, question? }
- GET /cards — list all 78 cards, returns { total, cards: [...] }
- GET /cards/{id} — full card details by ID (e.g., fool, ace-of-cups)

## Pages to build
1. **Daily Card** — POST /daily. Show card image (imageUrl), name, keywords, meaning, dailyMessage. Handle reversed cards.
2. **Spreads** — dedicated page for each spread type. POST /spreads/three-card for quick readings, POST /spreads/celtic-cross for deep readings. Each card shows position name, card image, name, and interpretation for that position.
3. **Yes/No Oracle** — POST /yes-no. Show answer, card, interpretation (not "explanation" — the field is called `interpretation`).
4. **Card Browser** — GET /cards to list all 78 cards. GET /cards/{id} for details. Filter by arcana (major/minor), suit.
5. **Custom Spread** — POST /spreads/custom with { positions: [{ name: "Past", interpretation: "What led to now" }, ...] }. Let users define their own spread layouts.

## Development rules
- TypeScript strict mode, no `any` casts
- DRY — shared API client, shared card component, shared error handler
- All API calls through server actions or API routes (keep API key server-side)
- Add ?lang= support with language selector (en, tr, de, es, hi, pt, fr, ru)
- Dark mode (next-themes), mobile responsive, loading states
- Handle errors: 400, 401, 429 with user-friendly messages
- If ROXY_API_KEY missing, show setup guide linking to roxyapi.com/pricing
- Clean minimal UI — card images in grid, no purple gradients

Build a complete Western astrology app using Next.js (TypeScript) and the RoxyAPI Astrology API.

## BEFORE writing any code
1. Fetch https://roxyapi.com/llms.txt to understand all available endpoints
2. Run: npx openapi-typescript https://roxyapi.com/api/v2/astrology/openapi.json -o src/api/schema.ts
3. Install: npm install openapi-fetch
4. Use the generated types for ALL API calls — never guess field names

## API Details
- Base URL: https://roxyapi.com/api/v2/astrology
- Location API: https://roxyapi.com/api/v2/location/search?q={query}
- Auth: X-API-Key header, env ROXY_API_KEY (server-side only)
- Birth data format: { date: "YYYY-MM-DD", time: "HH:MM:SS", latitude: number, longitude: number, timezone: number (decimal hours, e.g. -5 for EST, 5.5 for IST) }
- OpenAPI spec (for type generation): https://roxyapi.com/api/v2/astrology/openapi.json

## Available endpoints (23 total)
Birth charts: POST /natal-chart, POST /planets, POST /houses, POST /aspects
Horoscopes: GET /horoscope/{sign}/daily, GET /horoscope/{sign}/weekly, GET /horoscope/{sign}/monthly, GET /horoscope/daily (all 12)
Compatibility: POST /compatibility-score, POST /synastry, POST /composite-chart
Returns: POST /solar-return, POST /lunar-return, POST /planetary-returns
Transits: POST /transits, POST /transit-aspects
Moon: GET /moon-phase/current, GET /moon-phase/upcoming, GET /moon-phase/calendar/{year}/{month}
Reference: GET /signs, GET /signs/{id}, GET /planet-meanings, GET /planet-meanings/{id}

## Pages to build
1. **Birth Chart** — POST /natal-chart. Show "big three" (Sun, Moon, Ascendant). Table of all 13 planets (Sun-Pluto + Chiron + Nodes) with sign, house, degree, retrograde. Show interpretation.summary and interpretation.detailed. Display aspects with strength and nature.
2. **Horoscopes** — GET /horoscope/{sign}/daily, /weekly, /monthly. Sign picker with tabs for daily/weekly/monthly. Show overview, love, career, health.
3. **Compatibility** — POST /compatibility-score. Overall score (0-100), category breakdowns, strengths, challenges.
4. **Synastry** — POST /synastry. Inter-chart aspects between two people with relationship context.
5. **Transits** — POST /transit-aspects. Current transiting planets aspecting natal chart with timing, impact, guidance.
6. **Moon Phases** — GET /moon-phase/current for today, GET /moon-phase/calendar/{year}/{month} for monthly calendar.
7. **Zodiac Reference** — GET /signs for all 12 signs, GET /planet-meanings for all planets. Detail pages with full profiles.

## City search
GET /api/v2/location/search?q=mumbai — returns cities with latitude, longitude, timezone. Proxy through API route. Debounce 300ms.

## Development rules
- TypeScript strict, no `any`
- DRY — shared birth data form (reuse for natal chart, compatibility, synastry, transits)
- Server actions for all API calls
- ?lang= support with selector (en, tr, de, es, hi, pt, fr, ru)
- Dark mode, responsive, loading states, error handling
- Setup guide if key missing

Build a complete numerology app using Next.js (TypeScript) and the RoxyAPI Numerology API.

## BEFORE writing any code
1. Fetch https://roxyapi.com/llms.txt to understand all available endpoints
2. Run: npx openapi-typescript https://roxyapi.com/api/v2/numerology/openapi.json -o src/api/schema.ts
3. Install: npm install openapi-fetch
4. Use the generated types for ALL API calls — never guess field names

## API Details
- Base URL: https://roxyapi.com/api/v2/numerology
- Auth: X-API-Key header, env ROXY_API_KEY (server-side only)
- OpenAPI spec (for type generation): https://roxyapi.com/api/v2/numerology/openapi.json
- IMPORTANT: All endpoints use separate numeric fields. POST /life-path uses { year, month, day }. POST /expression uses { fullName }. POST /chart uses { fullName, year, month, day }. POST /maturity uses { lifePath, expression } (pre-calculated numbers). POST /personal-year uses { month, day, year? } where year is the target year (defaults to current).

## Available endpoints (13 total)
Core numbers: POST /life-path, POST /expression, POST /soul-urge, POST /personality, POST /birth-day, POST /maturity
Full chart: POST /chart (all core numbers + karmic + personal year in one call)
Karmic: POST /karmic-debt, POST /karmic-lessons
Forecasts: POST /personal-year, POST /daily
Compatibility: POST /compatibility
Reference: GET /meanings/{number} (get meaning for number 1-33)

## Pages to build
1. **Life Path Calculator** — POST /life-path. Show number, title, description, strengths, challenges, career, relationships, spirituality. Show calculation steps.
2. **Full Chart** — POST /chart. Show ALL core numbers: Life Path, Expression, Soul Urge, Personality, Birth Day, Maturity. Show karmic lessons (missing letters), karmic debt (if any), Personal Year forecast. Display the summary narrative.
3. **Individual Calculators** — separate pages for POST /expression, POST /soul-urge, POST /personality, POST /birth-day, POST /maturity. Each returns the number, meaning, and calculation.
4. **Compatibility** — POST /compatibility with two names and birth dates.
5. **Daily Number** — POST /daily. Today's number with meaning and guidance.
6. **Personal Year** — POST /personal-year. Current year forecast with theme, opportunities, challenges.
7. **Number Reference** — pages for each number 1-9 + master 11, 22, 33 using GET /meanings/{number}.

## Development rules
- TypeScript strict, no `any`
- DRY — shared form for name + birth date (reuse everywhere)
- Server actions, ?lang= support, dark mode, responsive
- Loading states, error handling
- Setup guide if key missing
- Show calculation breakdowns (the API returns calculation steps)

Build a complete Vedic astrology (Jyotish) app using Next.js (TypeScript) and the RoxyAPI Vedic Astrology API.

## BEFORE writing any code
1. Fetch https://roxyapi.com/llms.txt to understand all available endpoints
2. Run: npx openapi-typescript https://roxyapi.com/api/v2/vedic-astrology/openapi.json -o src/api/schema.ts
3. Also generate location types: npx openapi-typescript https://roxyapi.com/api/v2/location/openapi.json -o src/api/location-schema.ts
4. Install: npm install openapi-fetch
5. Use the generated types for ALL API calls — never guess field names

## API Details
- Base URL: https://roxyapi.com/api/v2/vedic-astrology
- Location API: https://roxyapi.com/api/v2/location/search?q={query}
- Auth: X-API-Key header, env ROXY_API_KEY (server-side only)
- Birth data: { date: "YYYY-MM-DD", time: "HH:MM:SS", latitude: number, longitude: number, timezone: number (decimal hours, e.g. 5.5 for IST, -5 for EST) }
- OpenAPI spec (for type generation): https://roxyapi.com/api/v2/vedic-astrology/openapi.json

## Available endpoints (40+ total)
Charts: POST /birth-chart (returns planets with rashi, nakshatra, interpretations, combustion, planetaryWar), POST /navamsa, POST /divisional-chart (D2-D60)
Dasha: POST /dasha/current, POST /dasha/major, POST /dasha/sub/{mahadasha} (mahadasha = planet name: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu)
Doshas: POST /dosha/manglik, POST /dosha/kalsarpa, POST /dosha/sadhesati
Compatibility: POST /compatibility (36-point Ashtakoot Gun Milan)
Panchang: POST /panchang/basic, POST /panchang/detailed, POST /panchang/choghadiya, POST /panchang/hora
Strength: POST /shadbala (planetary strength), POST /ashtakavarga (point system)
Transits: POST /transit (gochar), POST /transit/monthly
Aspects: POST /aspects, POST /aspects/monthly, POST /aspects/lunar
KP System: POST /kp/chart, POST /kp/planets, POST /kp/cusps, POST /kp/ruling-planets, POST /kp/sublord-changes + more
Positions: POST /planetary-positions, POST /planetary-positions/monthly
Other: POST /upagraha, POST /parallels, POST /ecliptic-crossings
Reference: GET /yoga (300+ yogas), GET /rashis, GET /nakshatras

## Pages to build
1. **Birth Chart (Kundli)** — POST /birth-chart. Lagna, 9 planets with rashi, nakshatra, pada, house. Interpretations. Combustion and planetary war.
2. **Navamsa (D9)** — POST /navamsa. D9 chart with Vargottama planets highlighted.
3. **Divisional Charts** — POST /divisional-chart with { division: 2|3|4|7|9|10|12|16|20|24|27|30|40|60 }. Show any varga chart.
4. **Dasha** — POST /dasha/current + POST /dasha/major. Timeline of all Mahadasha periods. Expand to see Antardashas via POST /dasha/sub/{lord}.
5. **Doshas** — POST /dosha/manglik, /kalsarpa, /sadhesati. Status, severity, remedies.
6. **Compatibility (Gun Milan)** — POST /compatibility. 36-point score, 8 koota breakdown, dosha detection, recommendation.
7. **Panchang** — POST /panchang/detailed. Tithi, nakshatra, yoga, karana, sunrise/sunset, Rahu Kaal, Yamaganda, Gulika.
8. **Choghadiya + Hora** — POST /panchang/choghadiya + POST /panchang/hora. Day/night muhurta periods with planetary hours.
9. **Strength Analysis** — POST /shadbala for planetary strength (6 components). POST /ashtakavarga for BAV/SAV point system.
10. **Transits** — POST /transit for gochar analysis over natal chart. POST /transit/monthly for sign change calendar.

## City search
GET /api/v2/location/search?q=mumbai — proxy through API route.

## Development rules
- TypeScript strict, no `any`
- DRY — shared birth data form, shared planet display component
- Server actions, ?lang= (Hindi is critical — use hi)
- Dark mode, responsive, loading states, error handling
- Setup guide if key missing
- Use tabs — don't call all 40 endpoints on page load. Load birth chart first, lazy-load others on tab switch.

Build a dream journal app using Next.js (TypeScript) and the RoxyAPI Dreams API.

## BEFORE writing any code
1. Fetch https://roxyapi.com/llms.txt to understand all available endpoints
2. Run: npx openapi-typescript https://roxyapi.com/api/v2/dreams/openapi.json -o src/api/schema.ts
3. Install: npm install openapi-fetch
4. Use the generated types for ALL API calls — never guess field names

## API Details
- Base URL: https://roxyapi.com/api/v2/dreams
- Auth: X-API-Key header, env ROXY_API_KEY (server-side only)

## Available endpoints
- GET /symbols — list all symbols (supports ?search=query for filtering)
- GET /symbols/{id} — full symbol details by ID
- GET /symbols/letters — browse symbols alphabetically
- GET /symbols/random — random symbol
- POST /daily — daily symbol with interpretation

## Pages to build
1. **Dream Entry** — text area to describe dream, button to search for symbols mentioned.
2. **Symbol Search** — GET /symbols?search={query}. Debounced input (300ms). Show matching symbols from 2,000+ dictionary.
3. **Symbol Detail** — GET /symbols/{id}. Full meaning, category, related symbols.
4. **Browse A-Z** — GET /symbols/letters. Alphabetical symbol directory.
5. **Daily Symbol** — POST /daily. Today's symbol with meaning.
6. **Random Discovery** — GET /symbols/random. Show a random symbol for exploration.
7. **Dream Log** — save dreams to localStorage with date, description, matched symbols. Track recurring symbols.

## Development rules
- TypeScript strict, no `any`
- Server actions for API calls, localStorage for dream storage
- ?lang= support, dark mode, responsive
- Debounced search, loading states, error handling
- Setup guide if key missing