← Guanyin Oracle · 观音灵签CONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Guanyin Oracle · 观音灵签
Snapshot Sep 30, 2026 · 23:12 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Conduct a Chinese-first Guanyin oracle ritual using the bundled 100-sign corpus, cup confirmation, and a faithful English reading. Use when the user asks to draw a Guanyin sign, seek a Guanyin oracle, request 观音灵签, or asks for a Chinese spiritual reading.",
"included_files": [
{
"relative_path": "data/guanyin-signs.json",
"size_in_bytes": 36173
},
{
"relative_path": "scripts/cast-cup.mjs",
"size_in_bytes": 991
},
{
"relative_path": "scripts/draw-sign.mjs",
"size_in_bytes": 563
}
],
"name": "guanyin-oracle",
"skill_md_contents": "---\nname: guanyin-oracle\ndescription: Conduct a Chinese-first Guanyin oracle ritual using the bundled 100-sign corpus, cup confirmation, and a faithful English reading. Use when the user asks to draw a Guanyin sign, seek a Guanyin oracle, request 观音灵签, or asks for a Chinese spiritual reading.\n---\n\n# 观音灵签 · Guanyin Oracle\n\nConduct a respectful, bounded ritual for reflection. The original draw remains Chinese; every interpretation is written in Chinese first and followed immediately by a faithful English counterpart.\n\n## Interactive temple first\n\nWhen the `render_guanyin_temple` MCP tool is available, use it before any draw. Pass through the user's question, category, and selected mode when known. The resulting **观音殿 · Guanyin Temple** widget is the primary experience: the user sets their question, presses `合掌请签` once, then presses `掷筊定签` once. The full result appears immediately in the widget. A busy ritual action must be disabled, and duplicate calls must preserve the original sign and reading.\n\n- Do not imitate the widget's buttons or animated ritual in Markdown.\n- Do not run the legacy local scripts while the widget is available; they are the fallback for non-widget hosts only.\n- The widget returns its full detailed bilingual reading itself. Do not issue a second chat prompt, `ui/message`, model-context update, or Markdown retelling after the ritual.\n- The original sign poem and traditional note remain Chinese only. Translate the interpretation, not the source sign text.\n- If the MCP widget cannot render, explain that briefly and use the legacy local-script flow below rather than pretending the interactive surface appeared.\n\n## Core principles\n\n- Preserve the bundled sign text exactly. Never invent or alter a poem, traditional note, rank, palace, or keyword.\n- The sign is a reflective aid, not a factual prediction or professional decision system.\n- Keep the ritual Chinese-first: use `观音灵签`, `摇签`, and `掷筊` in the ritual itself. Do not translate the original poem or traditional note as part of the draw.\n- The **reading** is bilingual. English must convey the same judgment and caveats as the Chinese directly above it; it must not introduce a different interpretation.\n- Use a few concise ritual beats in chat to evoke the app's temple flow. Do not claim to display 3D animation, physical randomness, temple audio, or a live visual when those are unavailable.\n\n## Seamless result and sign card\n\n- The complete result must require only two symbolic ritual taps after the user has entered their question: draw, then confirm. In strict mode, the widget presents all three confirming cups together in that second tap; it does not create a redraw loop.\n- Never call `ui/message` or the built-in image-generation tool as part of this ritual. Both turn a private widget action into a separate host conversation or approval flow.\n- The widget renders the full reading locally and offers one optional `保存本签 JPEG` action. It creates an exact local JPEG card for the specific sign drawn, with the real Chinese poem, traditional note, and key Chinese guidance; saving is never automatic.\n- Do not claim that a hidden model or image-generation service was used. The sign data and reading rules are local to the plugin.\n\n## Before drawing\n\nAsk for one focused question and one category when either is missing. Available categories are:\n\n| 中文 | English |\n| --- | --- |\n| 事业 | Career |\n| 感情 | Love and relationships |\n| 家庭 | Family |\n| 学业 | Study |\n| 迁移 | Relocation |\n| 财务倾向 | Financial direction |\n| 健康 | Health |\n| 平安 | Peace and wellbeing |\n| 失物 | Lost items |\n| 一般问事 | General matter |\n\nDo not turn an unclear or multi-part question into a confident conclusion. Help the user reduce it to one decision or condition first. Default to `一般问事` only if they explicitly ask to draw without a category.\n\nAsk whether they want `一般模式:一圣杯` or `严肃模式:三圣杯(最多七次)` if they have not specified. Default to general mode after they provide their question.\n\n## Ritual execution\n\n1. Only when the interactive widget is unavailable, resolve this plugin's root from this file's location. Run `node <plugin-root>/scripts/draw-sign.mjs` and retain the returned JSON in the current ritual state.\n2. Give a brief Chinese ritual beat, for example: `请静一静,只问这一事。签筒已起。`\n3. Show the drawn sign in Chinese only: sign number, rank, palace, poem, traditional note, and keywords.\n4. Run `node <plugin-root>/scripts/cast-cup.mjs` for general mode. In serious mode run `node <plugin-root>/scripts/cast-cup.mjs --strict --attempt <n>`.\n5. In general mode, interpret only after a `圣杯`. For `笑杯` or `阴杯`, say that this sign is not confirmed and invite the user to return it and draw again; do not force a reading.\n6. In serious mode, keep the current attempt count and the number of `圣杯` obtained since the latest draw. Three `圣杯` are required. A `笑杯` or `阴杯` means the sign is not confirmed: ask the user to draw again, preserve the attempt count, and reset the current sign's confirmation count. The script transparently guarantees `圣杯` on attempts 5-7 so the ritual cannot run indefinitely.\n7. Never reuse a previous sign, cup, or random output as though it were a new draw. If the scripts cannot run, say so plainly instead of fabricating a ritual result.\n\n## Reading format after confirmation\n\nUse this exact order. Keep the original-sign block Chinese only; write each interpretation block in Chinese and then English. This is intentionally a substantial reading: each main prose section must add a different useful layer of interpretation rather than rephrasing the same point. Aim for 3–5 grounded sentences in Chinese for `签意总断`, `对应问事`, `事势层次`, `当前阻碍`, and `可行方向`, followed by an English rendering with the same substance.\n\n```markdown\n## 观音灵签 · Guanyin Oracle\n\n**第 N 签 · 签级 · 宫位**\n\n> 签诗:<original Chinese poem>\n>\n> 传统解曰:<original Chinese note>\n\n关键词:<original Chinese keywords>\n筊杯:<Chinese cup result and, in serious mode, confirmation count>\n\n### 问事落点\n<Chinese restatement of the real decision or condition being held; distinguish what is known from what the user has not supplied.>\n\n### Question held\n<Faithful English rendering.>\n\n### 签意总断\n<Chinese interpretation grounded in the poem, note, rank, palace, cup result, and user question.>\n\n### Overall reading\n<Faithful English rendering of the Chinese paragraph directly above.>\n\n### 对应问事\n<Chinese reading for the user's actual question.>\n\n### Reading for your question\n<Faithful English rendering.>\n\n### 事势层次\n<Chinese explanation of the sign's central tension: what it supports, what it makes conditional, the sequence it advises, and why it matters now.>\n\n### Deeper pattern\n<Faithful English rendering.>\n\n### 当前阻碍\n<Chinese>\n\n### Present obstacle\n<Faithful English rendering.>\n\n### 可行方向\n<Chinese>\n\n### Practical direction\n<Faithful English rendering.>\n\n### 七日建议\n1. <Chinese action>\n2. <Chinese action>\n3. <Chinese action>\n4. <Chinese action>\n\n### 7-day actions\n1. <Faithful English action>\n2. <Faithful English action>\n3. <Faithful English action>\n4. <Faithful English action>\n\n### 不宜 / Avoid\n- <Chinese caution> — <faithful English rendering>\n- <Chinese caution> — <faithful English rendering>\n\n### 复问时机\n<Chinese: name a real-world condition to reassess before drawing again; never give a magical deadline.>\n\n### When to revisit\n<Faithful English rendering.>\n\n### 依据 / Basis\n- <exact short phrase from the poem or traditional note> — <brief explanation>\n- <cup result> — <brief explanation>\n\n### 边界 / Boundary\n<Chinese boundary note>\n\n### Boundary\n<Faithful English rendering>\n```\n\nUse 1-2 exact short phrases from the poem or traditional note as evidence, plus the cup result. Do not create a new verse, historical source, deity quote, hidden fact, or unsupported real-world narrative. Be warm and temple-like, but not theatrical or mechanically \"AI\". Detailed means more specific and more useful—not more certain.\n\n## Safety boundaries\n\n- For health: discuss rest, seeking care, checks, and support only. Never diagnose, prescribe, interpret symptoms, or defer urgent care.\n- For financial questions: never name a security, amount, trade, or timing. Emphasize cash-flow review, decision conditions, and qualified advice.\n- For legal, pregnancy, safety, death, or other consequential decisions: do not offer a decisive outcome. State that the sign is reflective only and encourage the relevant professional or emergency support.\n- Do not encourage repeated draws for the same unchanged issue. Suggest waiting at least seven days or until the real-world conditions change.\n"
}SHA-256 of public snapshot: a4a3667e5e92dd878239f20d1bd5c36b0f49c955d7d5b2f919fc1b43a770219c