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

woc-write-game-tooltips

GitHub

用于撰写或审核游戏技能、天赋等提示文本，确保与代码逻辑一致，包含测试验证和合规检查。

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

Trigger Scenarios

需要编写新的游戏机制提示文本审查现有提示文本的准确性

Install

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

More Options

Non-standard path

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

Use without installing

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

指定 Agent (Claude Code)

npx skills add levy-street/world-of-claudecraft --skill woc-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": "woc-write-game-tooltips",
    "description": "Write or audit World of ClaudeCraft spell, talent, aura, item, and mechanic tooltips in plain English, with live damage, healing, timing, target, resource, and power-scaling accuracy. Use for every player tooltip change or tooltip clarity review."
}

Write game tooltips

Write tooltips from the live mechanic, not from existing prose.

Workflow

Read docs/design/tooltip-writing.md in full.
Inspect the content record, runtime handlers, resolved ability path, and focused tests.
Record the target, result, timing, values, scaling stat, triggers, caps, and consumption rules.
Rewrite the authoritative English source in short, direct sentences.
Use live resolved values when rank, gear, talents, or specialization can change a number.
Add or update a focused test that compares the tooltip with the combat result.
Run the relevant mechanic, tooltip, i18n, and type checks.

Rules

Do not claim scaling that the combat path does not use.
Name Attack Power, Ranged Attack Power, Spell Power, weapon damage, pet state, or flat damage correctly.
State every important trigger, cap, stack, target limit, reset, and resource change.
Explain named states in plain English.
Do not repeat metadata without a clear reason.
Edit English sources first. Do not hand-edit locale overlays or generated i18n output.

Stop and record a mismatch when the code and intended design disagree. Do not make the tooltip promise unfinished behavior.