skills/w-update-wording-rule/SKILL.md
Add or update wording rules (表記ルール) in the w repo's vocabulary-rule.md files. Use when: (1) User says 'add wording rule', 'update wording rule', '表記ルール追加', (2) User wants to add a kanji/hiragana usage rule, (3) User provides a rule like 'X should be Y' with examples.
npx skillsauth add takazudo/claude-resources w-update-wording-ruleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Add a new wording rule to all 4 vocabulary-rule.md files in the w repo.
All 4 files must be updated identically:
$HOME/repos/w/cg/doc/docs/overview/vocabulary-rule.md$HOME/repos/w/esa/doc/docs/overview/vocabulary-rule.md$HOME/repos/w/message/doc/docs/overview/vocabulary-rule.md$HOME/repos/w/zpaper/doc/docs/overview/vocabulary-rule.mdRead the argument to understand the new rule. Expect format like:
ふうに should be 風に
そういうふうに → そういう風に
そういうふうな → そういう風な
The first line is the rule summary. Following lines are examples.
Read one of the target files to understand current structure and the last rule entry.
Compose a new rule section matching the existing format. Each rule section has:
### heading with the word pair (e.g., ### 「ふうに」と「風に」)<!-- ✅ Good --> and <!-- ❌ Bad --> examples**判断基準:** section with bullet points summarizing the decision criteriaAppend the new section to the end of each target file. Use the Edit tool on all 4 files.
Report what was added.
For a rule "ふうに should be 風に":
### 「風に」と「ふうに」
「風に」「風な」と漢字で表記する。「ふうに」「ふうな」とひらがなで書かない。
\`\`\`markdown
<!-- ✅ Good -->
そういう風に考えると、別の方法が良いかもしれません。
そういう風な書き方をする場合は注意が必要です。
<!-- ❌ Bad -->
そういうふうに考えると、別の方法が良いかもしれません。
そういうふうな書き方をする場合は注意が必要です。
\`\`\`
**判断基準:**
- 「〜風に」「〜風な」「〜風だ」→ 漢字「風」を使用
development
Link Claude Code skill names mentioned in a CodeGrid article (data/{series}/{n}.md) to the author's public claude-resources repo, pinned to the latest commit hash so links don't rot. Use when: (1) user says 'linkify cc resources', 'link the skills', 'link skill names', or invokes /dev-linkify-cc-resources; (2) editing a CodeGrid article that mentions `/commits`, `/pr-complete`, `/skill-creator` or other Claude Code skills and they should point to claude-resources. Only links skills that actually exist in the public repo; skips hypothetical examples and code blocks.
development
Second opinion from Claude Opus on a plan or approach. Use when: (1) Planning phase of /big-plan needs a higher-quality review than /codex-2nd / /gco-2nd, (2) User says 'opus 2nd' or 'opus opinion', (3) Wanting Anthropic's larger model to critique a plan. Spawns a general-purpose Agent with model: opus that reads the plan file and returns structured feedback. Anthropic quota — not free.
tools
AI-based testing via subagent + a per-task test-flow skill. Use when the user wants to verify something that mechanical assertions can't fully capture — image recognition, visual size/position comparison, animation smoothness, multi-step manual flows that need AI judgment. Triggers: 'AI-based test', 'AI test', 'visual verify', 'image recognition test', 'manual operation test', 'human-eye check', 'verify visually', 'compare screenshots', 'looks the same', 'looks correct'. The skill's job is to (1) author a focused test-flow skill that captures the exact procedure + verdict criteria, then (2) dispatch a verification subagent via the Agent tool that loads BOTH the test-flow skill AND a browser-driving skill (/verify-ui primary, /headless-browser fallback) so the subagent has clear context and consistent verdicts. NEVER uses `claude -p` — subagent dispatch goes through the Agent tool exclusively.
development
End-of-workflow audit of touched GitHub issues, PRs, and branches via a Sonnet subagent. Use when: (1) /big-plan, /x-as-pr, or /x-wt-teams finishes its main work and needs to verify every touched resource is in the right state (closed when done, kept when ongoing, deleted when dead), (2) User says 'cleanup resources', 'audit cleanup', or 'check what should be closed', (3) A long workflow ends and the manager wants a structured paper trail of what it closed/kept/deleted. Auto-execute by default — the Sonnet agent proposes, the manager (you) executes safe actions and prints a final report.