Agent Skills › levy-street/world-of-claudecraft › write-game-tooltips

write-game-tooltips

GitHub

用于撰写或审核游戏技能、物品等提示文本，确保内容清晰准确并与代码逻辑一致。适用于新增、修改、审计或发现模糊的提示文本场景。

.claude/skills/write-game-tooltips/SKILL.md levy-street/world-of-claudecraft

触发场景

新增玩家可见的提示文本修改现有提示文本审计提示文本准确性发现提示文本表述模糊

安装

npx skills add levy-street/world-of-claudecraft --skill write-game-tooltips -g -y

更多选项

非标准路径

npx skills add https://github.com/levy-street/world-of-claudecraft/tree/main/.claude/skills/write-game-tooltips -g -y

不安装直接使用

npx skills use levy-street/world-of-claudecraft@write-game-tooltips

指定 Agent (Claude Code)

npx skills add levy-street/world-of-claudecraft --skill write-game-tooltips -a claude-code -g -y

安装 repo 全部 skill

npx skills add levy-street/world-of-claudecraft --all -g -y

预览 repo 内 skill

npx skills add levy-street/world-of-claudecraft --list

SKILL.md

Frontmatter

{
    "name": "write-game-tooltips",
    "description": "Write or review World of ClaudeCraft spell, talent, aura, item, and mechanic tooltips in plain English. Use whenever player-facing tooltip text is added, changed, audited, or found to be vague, especially when damage, healing, duration, stacks, targets, resources, or Attack Power and Spell Power scaling must match live code.",
    "user-invocable": true
}

Write game tooltips

Make every tooltip clear enough to understand in one read and exact enough to test.

Required workflow

Read docs/design/tooltip-writing.md in full.
Read the live content definition and every runtime handler for the effect.
List the action, target, values, timing, scaling stat, triggers, caps, and consumption rules.
Write the English source in the order the player experiences it.
Use resolved values for anything changed by rank, gear, talents, or specialization.
Add or update a focused test that compares the tooltip with the combat result.
Run the relevant tooltip, mechanic, i18n, and type checks.

Hard rules

Never infer mechanics from the old description.
Never claim an effect scales until the live combat path proves it.
Never hide a trigger, cap, target limit, stack rule, cooldown reset, or resource change.
Never repeat metadata already shown above the description unless the repetition prevents a real misunderstanding.
Never hand-edit non-English locale overlays or generated i18n files.
Never use flavor text in place of an exact rule.

Write the English pass first. Locale work follows the repository release workflow.