/imessage-nine-grid-hypercard
Create narrow iMessage/PTT Border-Light HyperCard style nine-grid cards in Chinese or mixed Chinese-English. Use when the user says "iMessage 九宮 HyperCard", "iMessage 九宮", "做成 iMessage 九宮", "用 iMessage 九宮 HyperCard 整理", asks for a phone-readable short card with Context below, or
$ npx -y skills add twhsi/skills --skill imessage-nine-grid-hypercard --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/imessage-nine-grid-hypercard
Context preview
The summary Claude sees to decide when to auto-load this skill.
Create narrow iMessage/PTT Border-Light HyperCard style nine-grid cards in Chinese or mixed Chinese-English. Use when the user says "iMessage 九宮 HyperCard", "iMessage 九宮", "做成 iMessage 九宮", "用 iMessage 九宮 HyperCard 整理", asks for a phone-readable short card with Context below, or
SKILL.md
imessage-nine-grid-hypercard.SKILL.mdname: imessage-nine-grid-hypercard
description: Create narrow iMessage/PTT Border-Light HyperCard style nine-grid cards in Chinese or mixed Chinese-English. Use when the user says "iMessage 九宮 HyperCard", "iMessage 九宮", "做成 iMessage 九宮", "用 iMessage 九宮 HyperCard 整理", asks for a phone-readable short card with Context below, or wants Mandala/九宮/HyperCard content formatted for blue-bubble/iMessage sharing with long links, paths, and rules moved out of the card.
iMessage 九宮 HyperCard
Overview
Turn notes, plans, links, system status, or Mandala-style content into an iMessage-ready short card. Keep the phone card narrow and readable; put long data in a separate Context block after the card.
Output Workflow
1. Extract the central topic and up to eight surrounding nodes. 2. Write a short header/status section for the iMessage card. 3. Write a compact "phone-readable" summary section. 4. Write the nine-grid section in three row groups separated only by blank lines. 5. Move long URLs, file paths, detailed rules, full explanations, and overflow data into `Context` after the card.
When responding in chat, put the card in a plaintext fenced block so spacing survives. When sending through an actual messaging tool, send raw text without the fence.
Hard Rules
- Use this exact 18-stroke horizontal border unit: `──────────────────`.
- Use only these frame lines:
- `╭──────────────────╮`
- `├──────────────────┤`
- `╰──────────────────╯`
- Do not use left or right vertical borders on content lines.
- Indent every content line with two spaces.
- Use frame dividers only between the main short-card sections.
- Inside the nine-grid section, separate the three row groups with blank lines only.
- Never insert a bare `──────────────────` line inside the card.
- Keep each card line phone-readable. If a line becomes long, shorten it or move details to Context.
- Use `◎` for the center when a Mandala center is needed.
- Use circled numerals `①` to `⑧` for surrounding nodes when helpful.
- Output the finished card first. Put `Context` after it only when there is extra data.
Card Template
Use this structure as the default shape, adapting labels and details to the user's content:
╭──────────────────╮
HERMÈS/iMessage
永錫.OS ONLINE
{status}
{action}
├──────────────────┤
{short title}
+{short subtitle}
手機版:短卡在上
長資料:下放Context
[[①{node}]] 代表
Context有完整資料
├──────────────────┤
①{A} ②{B} ③{C}
{A note} {B note} {C note}
④{D} ◎ ⑤{E}
{D note} {center note} {E note}
⑥{F} ⑦{G} ⑧{H}
{F note} {G note} {H note}
╰──────────────────╯Context Block
Use Context for data that would make the card heavy:
Context
① {A}: {full detail, path, link, or rule}
② {B}: {full detail}
③ {C}: {full detail}
④ {D}: {full detail}
⑤ {E}: {full detail}
⑥ {F}: {full detail}
⑦ {G}: {full detail}
⑧ {H}: {full detail}Skip empty Context entries. If all information fits cleanly in the card and the user did not request Context, omit the Context block.
Style
Prefer warm, concise Chinese. Mixed Chinese-English labels are fine when they match the source material, such as `TARS`, `Codex`, `Hermes`, `Context`, `Apple`, or `iMessage`. Keep the card practical and copyable rather than decorative.
Read more
name: imessage-nine-grid-hypercard description: Create narrow iMessage/PTT Border-Light HyperCard style nine-grid cards in Chinese or mixed Chinese-English. Use when the user says "iMessage 九宮 HyperCard", "iMessage 九宮", "做成 iMessage 九宮", "用 iMessage 九宮 HyperCard 整理", asks for a phone-readable short card with Context below, or wants Mandala/九宮/HyperCard content formatted for blue-bubble/iMessage sharing with long links, paths, and rules moved out of the card.
iMessage 九宮 HyperCard
Overview
Turn notes, plans, links, system status, or Mandala-style content into an iMessage-ready short card. Keep the phone card narrow and readable; put long data in a separate Context block after the card.
Output Workflow
1. Extract the central topic and up to eight surrounding nodes. 2. Write a short header/status section for the iMessage card. 3. Write a compact "phone-readable" summary section. 4. Write the nine-grid section in three row groups separated only by blank lines. 5. Move long URLs, file paths, detailed rules, full explanations, and overflow data into `Context` after the card.
When responding in chat, put the card in a plaintext fenced block so spacing survives. When sending through an actual messaging tool, send raw text without the fence.
Hard Rules
- Use this exact 18-stroke horizontal border unit: `──────────────────`.
- Use only these frame lines:
- `╭──────────────────╮`
- `├──────────────────┤`
- `╰──────────────────╯`
- Do not use left or right vertical borders on content lines.
- Indent every content line with two spaces.
- Use frame dividers only between the main short-card sections.
- Inside the nine-grid section, separate the three row groups with blank lines only.
- Never insert a bare `──────────────────` line inside the card.
- Keep each card line phone-readable. If a line becomes long, shorten it or move details to Context.
- Use `◎` for the center when a Mandala center is needed.
- Use circled numerals `①` to `⑧` for surrounding nodes when helpful.
- Output the finished card first. Put `Context` after it only when there is extra data.
Card Template
Use this structure as the default shape, adapting labels and details to the user's content:
╭──────────────────╮
HERMÈS/iMessage
永錫.OS ONLINE
{status}
{action}
├──────────────────┤
{short title}
+{short subtitle}
手機版:短卡在上
長資料:下放Context
[[①{node}]] 代表
Context有完整資料
├──────────────────┤
①{A} ②{B} ③{C}
{A note} {B note} {C note}
④{D} ◎ ⑤{E}
{D note} {center note} {E note}
⑥{F} ⑦{G} ⑧{H}
{F note} {G note} {H note}
╰──────────────────╯Context Block
Use Context for data that would make the card heavy:
Context
① {A}: {full detail, path, link, or rule}
② {B}: {full detail}
③ {C}: {full detail}
④ {D}: {full detail}
⑤ {E}: {full detail}
⑥ {F}: {full detail}
⑦ {G}: {full detail}
⑧ {H}: {full detail}Skip empty Context entries. If all information fits cleanly in the card and the user did not request Context, omit the Context block.
Style
Prefer warm, concise Chinese. Mixed Chinese-English labels are fine when they match the source material, such as `TARS`, `Codex`, `Hermes`, `Context`, `Apple`, or `iMessage`. Keep the card practical and copyable rather than decorative.
Three Kings 2.2: compress with iMandalArt, address with BIRD, and publish with an A4 eight-page booklet. iMandalArt, FIRE semantic analysis, planning, and publishing workflows for Claude Code, Codex, and mainstream LLM agents.
Repo: twhsi/skills
Other skills on twhsi-skills.
- /a4-eight-page-booklet
Use A4 Eight Page Booklet 2.2 to create, write, repair, impose, and validate a printable A4 one-sheet eight-page mini book or zine from text, notes, images, BIRD Graph JSON, iMandalArt/九宮, FIRE, outlines, templates, or PDFs. Use whenever the user says A4八頁小書, 八頁小書, 八頁小冊, 八格小書,
Open skill - /auto-luhmann-numberer
Assign, validate, normalize, and explain Luhmann/Zettelkasten-style project-note codes for Chinese book manuscripts, Obsidian Markdown folders, Mandala-Grid section files, HyperCard Markdown stacks, and project-note JSON to EPUB workflows. Use when Codex needs to scan folders
Open skill - /concise-key-points
Compress answers to the highest practical information density with minimal wording while preserving essential meaning. Use when the user asks for 言簡意賅, 講重點, Concise, 精簡回答, 簡潔回答, 只講重點, 直接回答, brief, TL;DR, or otherwise requests a concise key-points response.
Open skill - /epub-hypercard-obsidian
Convert EPUB card books into Obsidian-ready HyperCard Markdown folders and portable zip files. Use when Codex needs to turn an EPUB with XHTML chapters, table-of-contents cards, keyword index cards, backlinks, Luhmann/Zettelkasten numbers, or cross-links into one Markdown file
Open skill - /fantastical-calendar
Create Fantastical calendar events and reminders from Codex on macOS. Use when the user asks Codex to add, schedule, parse, preview, or send a meeting, appointment, task, reminder, time block, daily plan item, 行事曆, 日曆, 會議, 待辦, or 提醒 into Fantastical.
Open skill - /fire-analysis-card
Analyze Chinese notes, articles, manuscripts, and digital card-box material with FIRE 2.0: Full-D numbering, Index keyword webs, Route thinking paths, and Evolution over time. Use when Codex needs to prepare material for semantic search, turn temporary notes into permanent or
Open skill

