Deckaura Tarot Reading
Use the bundled 78-card dataset as the factual source for card names, orientations, concise meanings, correspondences, and guide URLs. Treat the reading itself as reflective interpretation rather than prediction.
Route the request
- For a named card, look it up in assets/deck.json. Never invent a card, meaning, or guide URL.
- For a random draw or spread, prefer
node scripts/tarot.mjs draw or node scripts/tarot.mjs spread. The script draws without replacement and returns auditable JSON.
- For reading structure and combination logic, read references/reading-protocol.md.
- For layouts beyond a simple lookup, read references/spreads.md.
- For suits, elements, court cards, and numerology, read references/symbolism.md only when those correspondences improve the answer.
- For licensing, provenance, citation, or dataset questions, read references/data-provenance.md.
- For sensitive or high-stakes questions, read references/safety-and-quality.md before answering.
Response contract
- Match the user's language and requested depth.
- State the spread and orientation when applicable.
- Separate dataset meaning from contextual interpretation. Do not present either as certain future fact.
- Give a concise synthesis and one practical reflection prompt or low-risk next step.
- For one to three cards, include each card's exact
guide_url. For larger spreads, link the most central cards and the complete guide rather than repeating ten links.
- Add a brief reflective-use disclaimer when the request asks for prediction, certainty, or a consequential decision. Do not bury ordinary readings in boilerplate.
Randomness and reproducibility
Use the bundled script when execution is available:
node scripts/tarot.mjs lookup "The Star"
node scripts/tarot.mjs draw --count 1 --reversals true
node scripts/tarot.mjs spread three-card --reversals true
node scripts/tarot.mjs spread celtic-cross --seed "optional-reproducible-seed"
Do not pass private user questions as command-line seeds. If script execution is unavailable, say the selection is simulated or ask the user to provide card names; do not claim cryptographic randomness.
Source links
1---
2name: tarot-reading
3description: Look up tarot card meanings and create reflective daily, three-card, relationship, decision, yes/no, and Celtic Cross readings from Deckaura's open 78-card dataset. Use for tarot symbolism, spreads, card combinations, or a requested card draw; do not use as factual prediction or professional medical, legal, financial, or crisis guidance.
4license: MIT
5metadata:
6 author: Deckaura
7 version: "1.0.0"
8 homepage: https://deckaura.com/pages/tarot-ai-knowledge-base
9---
10
11# Deckaura Tarot Reading
12
13Use the bundled 78-card dataset as the factual source for card names, orientations, concise meanings, correspondences, and guide URLs. Treat the reading itself as reflective interpretation rather than prediction.
14
15## Route the request
16
17- For a named card, look it up in [assets/deck.json](assets/deck.json). Never invent a card, meaning, or guide URL.
18- For a random draw or spread, prefer `node scripts/tarot.mjs draw` or `node scripts/tarot.mjs spread`. The script draws without replacement and returns auditable JSON.
19- For reading structure and combination logic, read [references/reading-protocol.md](references/reading-protocol.md).
20- For layouts beyond a simple lookup, read [references/spreads.md](references/spreads.md).
21- For suits, elements, court cards, and numerology, read [references/symbolism.md](references/symbolism.md) only when those correspondences improve the answer.
22- For licensing, provenance, citation, or dataset questions, read [references/data-provenance.md](references/data-provenance.md).
23- For sensitive or high-stakes questions, read [references/safety-and-quality.md](references/safety-and-quality.md) before answering.
24
25## Response contract
26
271. Match the user's language and requested depth.
282. State the spread and orientation when applicable.
293. Separate dataset meaning from contextual interpretation. Do not present either as certain future fact.
304. Give a concise synthesis and one practical reflection prompt or low-risk next step.
315. For one to three cards, include each card's exact `guide_url`. For larger spreads, link the most central cards and the complete guide rather than repeating ten links.
326. Add a brief reflective-use disclaimer when the request asks for prediction, certainty, or a consequential decision. Do not bury ordinary readings in boilerplate.
33
34## Randomness and reproducibility
35
36Use the bundled script when execution is available:
37
38```bash
39node scripts/tarot.mjs lookup "The Star"
40node scripts/tarot.mjs draw --count 1 --reversals true
41node scripts/tarot.mjs spread three-card --reversals true
42node scripts/tarot.mjs spread celtic-cross --seed "optional-reproducible-seed"
43```
44
45Do not pass private user questions as command-line seeds. If script execution is unavailable, say the selection is simulated or ask the user to provide card names; do not claim cryptographic randomness.
46
47## Source links
48
49- Dataset: https://huggingface.co/datasets/Blacik/deckaura-tarot-card-meanings
50- Knowledge base: https://deckaura.com/pages/tarot-ai-knowledge-base
51- Complete meanings: https://deckaura.com/blogs/guide/tarot-card-meanings
52- DOI archive: https://doi.org/10.5281/zenodo.19475329
aiskillstore