SuperAPI AI Directory
Partner中文AI newsFavorites
Skills@3182/zodiac-pastlife-myth

@3182/zodiac-pastlife-myth

Design & creation

View repository

Updated 10-16 08:24

About this skill

AI-Customized "Zodiac Past-Life Myth"

You need to turn the user's input (zodiac sign + birth date + 3 personality keywords) into a collectible destiny narrative work:

  • Past-life myth story (about 800 words, in Chinese)
  • Epic illustration (1 image)
  • Destiny prophecy short poem (4-8 lines)
  • One-page HTML myth scroll

Input rules (collect first)

Must include:

  1. Zodiac sign (e.g., Scorpio)
  2. Birth date (YYYY-MM-DD)
  3. 3 personality keywords (e.g., calm, stubborn, gentle)

Optional:

  • Gender/pronoun
  • Desired emotional main color (e.g., fated romance, restrained deep affection, passionate protection)
  • Taboo elements (e.g., no tragic ending)

If fields are missing, complete them first before generating.

Consistency check

  • If the "zodiac sign" and the result derived from "birth date" are clearly inconsistent, first confirm with one sentence:
    • "Do you want the zodiac sign you filled in to be authoritative, or the zodiac sign derived from your birthday to be authoritative?"
  • If the user does not reply, by default use the "zodiac sign explicitly filled in by the user" as authoritative.

Output structure (fixed)

1) Past-life myth story (about 800 words)

Style: Chinese mythic style + romantic sense of fate.

Four-part skeleton:

  1. Beginning of destiny(≈150 words)
    • Open with imagery such as the star river, the deity of fate, ancient halls, and spirit artifacts.
    • Translate the "zodiac traits" into a mythic identity (e.g., Scorpio → Oathkeeper of the Night Abyss).
  2. Past-life trial(≈250 words)
    • Design threefold trials or three oaths based on the 3 keywords.
    • Each keyword must be embodied in concrete behavior; do not write vague adjectives.
  3. Fated turning point(≈250 words)
    • Set up a conflict between "love and destiny" and give the cost of the choice.
    • Maintain a healing feeling: there may be regret, but do not write a despairing ending.
  4. Echo in this life(≈150 words)
    • Map the past-life imprint onto the user's personality and relationship patterns in this life.
    • The ending should feel gently watched over by fate.

Hard rules:

  • Must include actions corresponding to the 3 input keywords.
  • Must not be written as trivial zodiac horoscope content; no "today favorable/avoid".
  • Avoid modern internet memes and maintain classical lyricism.

2) Destiny prophecy short poem (4-8 lines)

  • Style leans toward old-style new poetry, with short lines and a strong sense of blank space.
  • Must echo the "core oath/token/astronomical sign" in the story.
  • The last line lands on a "blessing-like sense of destiny".

3) Epic illustration (1 image)

Generate the illustration only after the story is complete, ensuring the image is consistent with the plot.

Unified prompt framework (replace variables according to the story):

  • Subject: the user's past-life mythic identity + key token + zodiac symbol
  • Scene: Chinese mythic realm (heavenly palace, sacred mountain, sea of stars, ancient altar, etc.)
  • Atmosphere: romantic fate, epic, celestial, emotional, cinematic
  • Style anchors: epic Chinese mythology illustration, celestial romance, ornate costume, flowing silk, ancient palace ruins, star river, volumetric light, dramatic composition, ultra-detailed, painterly, no text

Suggested parameters:

  • model="nanopro"
  • aspect_ratio="landscape"
  • quality="high"
  • n=1

Must read the real image path from the tool result; guessing the path is prohibited.

Assemble into a mythological scroll

  1. Write the story and poem into JSON (schema see scripts/build_mythbook.py file header).
  2. Run: python3 skills/zodiac-pastlife-myth/scripts/build_mythbook.py <myth.json> <out.html>
  3. Output directory: output/zodiac-pastlife-myth/<name_or_sign>/

At minimum produce:

  • myth.json
  • mythbook.html
  • illustration.png

Delivery message to the user

When delivering, briefly explain:

  • Completed story + illustration + prophecy poem
  • Provide the full path output/.../mythbook.html
  • Ask whether public release is needed (if the user wants it public, then go through the release process)

Release (execute when the user requests "release")

  • This is a "skill release" rather than a project release: use the skillmarket release process.
  • Before releasing, confirm that the SKILL.md frontmatter contains name/version/author/tags。
  • Versions cannot be overwritten; if there are changes, the version number must be upgraded before releasing again.
  • Return the tag (e.g. @3182/zodiac-pastlife-myth@1.0.0) and the release link.

Quality self-check

  • Whether the user's zodiac sign, birthday, and 3 keywords are used exactly
  • Whether the story is about 800 words and clearly layered
  • Whether the prophecy poem is consistent with the story's imagery
  • Whether the illustration is Chinese mythology + a sense of romantic destiny
  • Whether the HTML can be opened and read directly
  • Whether the file path is complete and clickable