菜单
Analyze relationship compatibility between two people using synastry, composite, and Davison/midpoint charts. Use when someone asks about romantic compatibility, relationship dynamics, friendship chemistry, business partnership fit, or how two people's charts interact.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Your personal astrologer, powered by NASA JPL DE440 ephemeris data. Natal charts, transits, synastry, eclipses, moon phases, electional timing, Human Design, and chart wheel visualization — all interpreted conversationally.
Generate and interpret astrocartography (ACG / locational astrology) — planetary lines, parans, crossings, local space, and how moving to a different location changes a chart. Use when someone asks about astrocartography, ACG, the best place to live, what city is best for their career or love life, relocation, or planetary lines.
Calculate and interpret Chinese BaZi Four Pillars / Chinese zodiac and Vedic Jyotish charts including nakshatras, dashas, yogas, and ayanamsa selection. Use when someone asks about Eastern astrology systems, their Chinese zodiac animal, BaZi, sidereal/Vedic chart, nakshatra, or dasha.
Calculate and interpret Human Design maturation transits — Saturn Return, Uranus Opposition, Chiron Return, Jupiter Return, and Uranus Return. Use when someone asks about their HD life cycles, maturation points, midlife crisis transits, or the major developmental milestones of the Human Design system.
Generate and interpret Human Design bodygraph charts including type, strategy, authority, profile, incarnation cross, defined and undefined centers, gates, and channels. Use when someone asks about their Human Design, HD type, strategy and authority, or any Human Design concept.
Interpret a natal (birth) chart using OpenEphemeris. Use when someone asks about their birth chart, planetary placements, personality traits, life themes, the Big Three (Sun/Moon/Rising), houses, aspects, dignities, nodes, Chiron, or any astrological analysis based on birth data.
| name | compatibility-synastry |
| description | Analyze relationship compatibility between two people using synastry, composite, and Davison/midpoint charts. Use when someone asks about romantic compatibility, relationship dynamics, friendship chemistry, business partnership fit, or how two people's charts interact. |
| version | 1.0.0 |
| updated | "2026-05-23T00:00:00.000Z" |
Use this skill whenever someone asks how two people work together — romantically, in friendship, or in partnership. Three complementary tools:
| Tool | Question it answers |
|---|---|
| Synastry | "How do our energies interact?" (each person's planets aspecting the other's) |
| Composite | "What is the relationship itself like?" (a third chart for the bond) |
| Davison / Midpoint | "What's the time-space midpoint of our two charts?" (an alternative composite based on real averaged ephemeris time + location) |
Two complete subjects — for EACH person:
Any endpoint that takes a birth chart (natal, synastry, composite, transits, returns, progressions, Human Design, Vedic, ACG) MUST follow this sequence. Skipping any step produces a wrong chart — usually wrong by hours of arc.
If you don't already have precise lat/lon, call:
GET /location/autocomplete?query=<city, country>&limit=5
Confirm the right hit with the user if there's ambiguity (e.g. "Portland, OR" vs "Portland, ME"). Record the latitude and longitude of the chosen result.
Historical timezone rules matter. A city's UTC offset in 1962 may differ from today (DST rules, war time, jurisdiction changes). Always look up the timezone for the specific birth date.
POST /timezone/lookup
{ "latitude": <lat>, "longitude": <lon> }
Response gives an IANA timezone string like "America/Los_Angeles". The BirthLocation field below REQUIRES this — it is not optional.
The SubjectRequest schema requires birth_datetime, birth_location, and name. The IANA timezone goes into birth_location.timezone:
{
"subject": {
"name": "Subject",
"birth_datetime": { "iso": "1990-04-15T14:30:00" },
"birth_location": {
"latitude": 41.8781,
"longitude": -87.6298,
"timezone": "America/Chicago",
"city": "Chicago",
"country": "United States"
}
}
}
The iso field is the local civil time at the birth location. The API handles the conversion to UTC using the supplied IANA timezone. Do not pre-convert to UTC and do not pass an offset suffix on the iso string unless the user explicitly knows it.
The natal chart endpoint defaults to Placidus. Before computing, briefly ask:
"I'll use Placidus houses by default (the most common modern Western system). If you prefer a different system — Whole Sign (Hellenistic/traditional), Koch, Equal, Campanus, Regiomontanus, or Porphyry — just say so."
Once chosen, pass it through configuration.house_system on the request.
format=llm unless raw JSON is requestedThis reduces token usage by ~73% and gives you a readable, interpretable response. Add ?format=llm to the URL.
If the user doesn't know their birth time:
For Human Design, type/strategy/authority/profile depend on precise time — flag any time uncertainty and suggest the user rectify with a Human Design analyst or rectification service before relying on these results.
Run Steps 1–3 of the Standard Procedure for both people independently — geocode and timezone lookup are per-person.
POST /comparative/synastry?format=llm
Body:
{
"subject_a": { "name": "...", "birth_datetime": {...}, "birth_location": {...} },
"subject_b": { "name": "...", "birth_datetime": {...}, "birth_location": {...} },
"configuration": { "house_system": "placidus" }
}
POST /comparative/composite?format=llm
(same two-subject body shape)
POST /comparative/composite/midpoint?format=llm
POST /comparative/overlay?format=llm
— wheel rendering of one chart overlaid on the other.
Walk through these in order, leading with the most impactful.
The "Big Three to Big Three" check:
The romantic / sexual / desire layer:
Communication style and friendship layer:
These create the deepest binds — and the deepest difficulties:
Where each person's planets fall in the OTHER's houses tells you what life areas activate between you:
The composite is the relationship-as-a-being. Read it like a natal chart, but every placement describes the relationship, not either person:
After walking through the layers, give a short overall narrative:
User: "Are my partner and I compatible? I'm March 3, 1995, 7:22 AM Portland Oregon. They're July 12, 1988, around 3 PM in Brooklyn NY."
POST /comparative/synastry?format=llm with both subjectsPOST /comparative/composite?format=llm for the relationship-as-entity reading