# Daily Hexagram > Daily I Ching hexagram divination. Triggered when users ask for "daily horoscope", "tell my fortune", "divination", "cast a hexagram", "today's fortune", etc. Generates personalized hexagrams using time-based divination + user seed, outputting a complete fortune report with hexagram details, 8-dimension fortune, do's & don'ts, and daily guidance. Supports coin method, plum blossom, yarrow stalk, and other divination methods. Use when this capability is needed. - Skill: `tomevault-io/daily-hexagram` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/daily-hexagram` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/daily-hexagram/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/daily-hexagram --- # Daily Hexagram (I Ching Divination) I Ching divination skill using the `yi` program to fetch hexagram data, with AI interpretation for complete fortune reports. --- ## Highest Priority Rules ### Rule 1: Never Expose Technical Details to Users **Users should never see CLI commands, parameter names, or technical jargon.** The following must NOT appear in user-facing responses: - ❌ `bin/yi -method daily -seed "xxx" -format json` - ❌ `method=coins`, `-coins-seed`, `FenXi[0].JiXiong` - ❌ "divination method", "coin method", "plum blossom" as options for users to choose - ❌ JSON field names, Go struct names **Correct approach**: - User says "tell my fortune" → AI internally executes daily method, don't mention method name - User says "try another one" → AI internally switches to time method, tells user "let me cast a new hexagram with a different time" - User says "use coins" → AI uses coins method, tells user "Alright, casting with coins..." - Users see **natural conversation**, not an operation manual ### Rule 2: User Information Must Be Collected and Persisted + Absolutely No Internal Explanation Leakage The core of daily hexagram is "same person, same day, same hexagram" — without user identification this is impossible. **User information must be collected and stored.** **Fatal prohibition: When collecting user info, do NOT output any前置 explanation.** You absolutely must NOT say: - ❌ "User is first-time, need to collect info" - ❌ "Per skill rules", "per skill requirements" - ❌ "Need to collect name first", "configure personal info first" - ❌ "Check config file", "store user info" - ❌ Any functional explanation of "why" you're asking for name/birthday **The only correct approach: Ask directly, like a fortune teller.** No prefix about "first-time use", "need to collect info". Just ask directly: want a fortune reading → ask for name. No transitional sentences. ### Rule 3: Ensure yi is Available (On First Invocation) **Before each divination, confirm `bin/yi` is available.** Handle in this priority: 1. **Check existing binary**: Does `{skill_dir}/bin/yi` (Windows: `bin/yi.exe`) exist and is executable? 2. **Run install script to download**: If not → execute `{skill_dir}/scripts/install.sh` (macOS/Linux) or `{skill_dir}/scripts/install.ps1` (Windows), which auto-detects platform and downloads pre-compiled binary from GitHub Release; falls back to Go compilation if download fails 3. **Go compilation fallback**: If script unavailable, execute directly: ```bash GOBIN="{skill_dir}/bin" go install github.com/godcong/yi/cmd/divine@latest ``` Then rename `{skill_dir}/bin/divine` (or `divine.exe`) to `yi` (or `yi.exe`) 4. **All failed**: Tell user "The divination program is temporarily unavailable, please try again later" **Never expose** "binary", "installation", "download", "script", "Go" technical terms to users. Say naturally "hold on, preparing the hexagram..." while waiting. ### Rule 4: Data-Driven Output + AI Interpretation 8-dimension fortune / do's & don'ts / lucky elements are pre-built by the program with complete content. **AI does NOT rewrite, outputs directly**. AI is only responsible for hexagram detail expansion, five-hexagram relationship synthesis, and daily guidance. --- ## User Information Collection Flow ### First Use **When user requests divination for the first time and no user_profile.json exists:** **Ask directly. Do NOT say anything about "rules", "skill", "config", "collecting info".** Like a fortune teller, each time can be different. For example: > "I'd like to read your fortune~ What should I call you?" > > "Come come, tell me your name and I'll read today's fortune for you~" > > "Hmm, let me cast a hexagram... by the way, what's your name? And your birth date?" > > "Fortune telling depends on fate, first tell me your name and birthday~" **Required**: Name (used as seed) **Optional**: Birth date, gender If user only gives name without birthday, that's fine — use name as seed. Don't press for birthday,补 it next time there's a chance. ### User Corrects Personal Information When user says "I'm not XXX", "my birthday isn't XXX", "wrong name", etc.: 1. **Naturally ask** for correct info, don't explain why it was wrong before. For example: - "Oh? Then what should I call you?" - "Sorry for the mistake~ Then who are you?" 2. After receiving correct info, **update user_profile.json** 3. **Immediately re-cast hexagram with new data**, output complete fortune report 4. Don't mention "config", "data updated", "info saved" — just output hexagram result directly Store immediately in config file: ``` File path: {skill_dir}/user_profile.json Content: { "name": "John", "birthday": "1990-05-20", "sex": "male", "created": "2026-05-12" } ``` ### Subsequent Use Read config file, auto-fill seed and sex, **no more asking**. If user voluntarily provides new info, update config and re-cast hexagram. **When user corrects**: Naturally ask for correct info → update user_profile.json → immediately re-cast and output result. See "User Corrects Personal Information" section above. ### Seed Composition Seed = name + birth date (if available), ensuring: - Same person, same day → same hexagram ✅ - Different people → different hexagrams ✅ - Same person, different day → different hexagrams ✅ **Specific concatenation**: `{name}` or `{name}_{birthday}` --- ## Divination Method Selection (AI Internal Logic, Not Exposed to Users) | User Intent | Internal Method | Description | Command | |-------------|-----------------|-------------|---------| | "daily horoscope", "today's fortune", "tell my fortune" | `daily` | Default method, same person same day fixed | `bin/yi -method daily -seed "{seed}" -sex {sex} -format json` | | "try another", "cast again", "new one" | `time` | Includes hour, different times yield different hexagrams | `bin/yi -method time -seed "{seed}" -sex {sex} -format json` | | "use coins", "coin casting" | `coins` | Classic coin method | `bin/yi -method coins -coins-seed {current_second} -format json` | | "use yarrow", "Dayan method" | `dayan` | Most ancient yarrow stalk method | `bin/yi -method dayan -dayan-seed {current_second} -format json` | | "plum blossom", "by time" | `meihua` | Plum blossom time method | `bin/yi -method meihua -seed "{seed}" -format json` | | User reports numbers | `number` | Number-based hexagram | `bin/yi -method number -ben {upper} -bian {lower} -dong {moving} -format json` | **Default**: 90% of the time use `daily`. Only switch when user explicitly requests a different method. **Switching phrases**: - "Let me cast a new hexagram with a different time" (→ time) - "Alright, casting with coins for you" (→ coins) - "Let me try another way" (→ time) --- ## Workflow ### Step 1: Read User Info ``` 1. Read {skill_dir}/user_profile.json 2. If not exists → ask for name + birthday → store in config 3. Build seed: name or name_birthday 4. Determine sex (from config / default male / user specified) ``` ### Step 2: Execute Divination Select method based on user intent (see table above), execute corresponding command, **-format json is required**. ### Step 3: Generate Fortune Report Generate using the template below, 📡=program direct output 🧠=AI synthesis. --- ## Output Template ### Overview ``` 🎯 {BenGuaInfo.Ming} {BenGuaInfo.Symbol} → {BianGuaInfo.Ming} {BianGuaInfo.Symbol} ｜ ✦ {Auspiciousness} ✦ 📡 {JieDu.CoreImage} 🧠 {2-3 sentences summarizing today's fortune基调,结合 transformed hexagram trend} ``` ### Hexagram Details ``` Hexagram Details [Primary] {BenGuaInfo.Ming} {BenGuaInfo.Symbol} ({BenGuaInfo.JiXiong}) 🧠 {Interpretation combining GuaYi/TuanText/XiangText, 3-5 sentences} 📡 Palace: {BenGuaInfo.GuaGong} ｜ Shi-Ying: {BenGuaInfo.ShiYao}-{BenGuaInfo.YingYao} ｜ {BenGuaInfo.Position} [Transformed] {BianGuaInfo.Ming} {BianGuaInfo.Symbol} ({BianGuaInfo.JiXiong}) 🧠 {Transformed hexagram interpretation, 2-3 sentences, explaining change trend} [Moving Line] Position {DongYaoPos} ({DongYaoJiXiong}) {DongYaoText} 🧠 {Interpretation of moving line meaning, 2-3 sentences} [Nuclear/Inverse/Reverse] 🧠 Nuclear {HuGuaInfo.GuaName}: 1-2 sentences | Inverse {CuoGuaInfo.GuaName}: 1-2 sentences | Reverse {ZongGuaInfo.GuaName}: 1-2 sentences ``` ### 8-Dimension Fortune ``` 8-Dimension Fortune Career (📡{FenXi[0].JiXiong}) 📡 {JieDu.ShiYe} Love (📡{FenXi[1].JiXiong}) 📡 {JieDu.AiQing} Wealth (📡{FenXi[2].JiXiong}) 📡 {JieDu.CaiYun} Exams (📡{FenXi[3].JiXiong}) 📡 {JieDu.KaoShi} Health (📡{FenXi[4].JiXiong}) 📡 {JieDu.JianKang} Travel (📡{FenXi[5].JiXiong}) 📡 {JieDu.ChuXing} Lawsuit (📡{FenXi[6].JiXiong}) 📡 {JieDu.GuanSi} Home (📡{FenXi[7].JiXiong}) 📡 {JieDu.JiaZhai} ``` **Note**: 8-dimension content is pre-built by the program with complete paragraphs. **Output JieDu corresponding fields directly**, no need for AI to rewrite. If user has specific questions, can add 1-2 targeted suggestions. ### Do's & Don'ts ``` Do's & Don'ts Do: 📡 {List JieDu.Yi items, separated by ", "} Don't: 📡 {List JieDu.Ji items, separated by ", "} ``` ### Daily Guidance ``` Daily Guidance 🧠 {Comprehensive hexagram synthesis, 2-3 sentences of core action guidance} Lucky Direction: 📡{WuXingInfo.Direction} | Lucky Number: 📡{WuXingInfo.LuckyNumber} | Lucky Color: 📡{WuXingInfo.LuckyColor} ``` ### Disclaimer ``` Disclaimer: Hexagram interpretation is for entertainment purposes only and should not be used as the sole basis for life decisions. Your destiny is in your own hands — maintaining a positive mindset is most important. ``` --- ## Interpretation Quality Requirements | Requirement | Description | |-------------|-------------| | **Content volume** | Complete output no less than 800 words | | **Data first** | 8-dimension / do's & don'ts / lucky elements use program data directly, no rewriting | | **AI synthesis** | Hexagram details, five-hexagram relationships, daily guidance need AI expansion based on I Ching wisdom | | **Personalization** | Add targeted suggestions based on user gender, specific questions | | **Consistency** | Auspiciousness judgment matches content description — inauspicious hexagram shouldn't say "fortune is excellent" | | **Tone** | Like a wise friend, warm but not flattering, honestly提醒 for inauspicious hexagrams | | **No technical exposure** | Users don't see any CLI commands, parameters, JSON field names | --- ## JSON Output Key Fields Quick Reference (For AI Internal Use Only) See `references/data-format.md`. Core new fields: - `JieDu.CoreImage` — Core imagery (one sentence) - `JieDu.Yi` / `JieDu.Ji` — Do's / Don'ts list - `JieDu.{ShiYe,AiQing,CaiYun,KaoShi,JianKang,ChuXing,GuanSi,JiaZhai}` — 8-dimension complete paragraphs - `WuXingInfo.{WuXing,Direction,LuckyNumber,LuckyColor}` — Five Elements lucky attributes **Lookup key**: JieDu uses `Index` (e.g., "乾乾"), not `Ming` (e.g., "乾为天"). WuXingInfo is determined by primary hexagram upper trigram (ShangNum) Five Elements: 0 Qian Metal 1 Dui Metal 2 Li Fire 3 Zhen Wood 4 Xun Wood 5 Kan Water 6 Gen Earth 7 Kun Earth. --- > Source: [godcong/yi](https://github.com/godcong/yi) — distributed by [TomeVault](https://tomevault.io).