takazudo/w-update-wording-rule
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.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources w-update-wording-ruleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 10, 2026, 5:53 AM233.8s1 file scanned
SKILL.md
- name:
- w-update-wording-rule
- description:
- 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.
- user-invocable:
- true
- argument-hint:
- rule description (e.g., ふうに should be 風に)
Update Wording Rule
Add a new wording rule to all 4 vocabulary-rule.md files in the w repo.
Target Files
All 4 files must be updated identically:
$HOME/repos/w/cg/doc/src/content/docs/overview/vocabulary-rule.md$HOME/repos/w/esa/doc/src/content/docs/overview/vocabulary-rule.md$HOME/repos/w/message/doc/src/content/docs/overview/vocabulary-rule.md$HOME/repos/w/zpaper/doc/src/content/docs/overview/vocabulary-rule.md
The
cg,esa, andzpaperpaths follow thedoc/src/content/docs/overview/layout used by the apply-voice skills and writer agents (the sites migrated to the Astro/zudo-doc layout). Thew/messagerepo's layout could not be verified from this environment — it is assumed to have migrated to the same layout, so confirm itsvocabulary-rule.mdpath before appending.
Process
-
Read 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.,### 「ふうに」と「風に」)- One-sentence explanation of when to use which form
- Markdown code block with
<!-- ✅ Good -->and<!-- ❌ Bad -->examples **判断基準:**section with bullet points summarizing the decision criteria
-
Append the new section to the end of each target file. Use the Edit tool on all 4 files.
-
Report what was added.
Example Output Section
For a rule "ふうに should be 風に":
### 「風に」と「ふうに」
「風に」「風な」と漢字で表記する。「ふうに」「ふうな」とひらがなで書かない。
\`\`\`markdown
<!-- ✅ Good -->
そういう風に考えると、別の方法が良いかもしれません。
そういう風な書き方をする場合は注意が必要です。
<!-- ❌ Bad -->
そういうふうに考えると、別の方法が良いかもしれません。
そういうふうな書き方をする場合は注意が必要です。
\`\`\`
**判断基準:**
- 「〜風に」「〜風な」「〜風だ」→ 漢字「風」を使用
Important
- Keep the existing frontmatter and content intact
- The new rule is appended at the end of the file
- All 4 files must have identical content after the update
- Write the explanation and examples in Japanese
- If the user provides examples, use them. If not, generate appropriate ones
Related Skills
takazudo/finalize-codex-work
tools
VerifiedTrustedCommunity
Acceptance gate for a branch produced by an OpenAI Codex CLI run — usually Codex implementing a /big-plan epic that was handed off to it. Codex reports the work 'done' (or the user flags it WIP with corrections); this skill confirms the branch actually fulfils the original spec, fixes what falls short, and routes larger discoveries into GitHub issues. Use when: (1) User says '/finalize-codex-work', 'finalize codex work', 'confirm the codex work', 'check the codex branch', or 'codex said it's done', (2) A branch is the result of a Codex CLI session and needs verification against its spec issue/PR, (3) After assigning a /big-plan epic to Codex CLI. Pass -m/--merge to run /pr-complete -c at the end.
11SKILL.mdUpdated Jul 10, 2026
takazudo/fig-url-refer
tools
VerifiedTrustedCommunity
Read a Figma design node directly from a share URL via the Figma REST API — no Dev Mode subscription, no MCP, no desktop app. Renders the node to PNG and dumps its full style/layout JSON so the design can be described, compared, or implemented. Use whenever the user gives a Figma design URL (figma.com/design/... or /file/...) and wants to see, read, inspect, reference, or implement that node — including `/fig-url-refer <url>`. This is the URL-based counterpart to `/figrefer` (which needs a Dev-plan desktop MCP); prefer this one when the input is a URL rather than a live desktop selection.
11SKILL.mdUpdated Jul 10, 2026
takazudo/dev-codex-sync-settings-from-claude
tools
VerifiedTrustedCommunity
Sync the user's Claude Code workflow skills into the OpenAI Codex CLI settings repo ($HOME/.codex) as Codex-native ports, fix the Codex .gitignore for new local state, then commit and push. Use when: (1) user says '/dev-codex-sync-settings-from-claude', 'sync codex settings', 'sync claude skills to codex', 'port skills to codex', or 'update codex from claude'; (2) after updating ~/.claude workflow skills (big-plan, x, x-as-pr, x-wt-teams) and Codex should catch up; (3) the $HOME/.codex repo has drifted behind $HOME/.claude. The ports are condensed Codex-native REWRITES, never file copies.
11SKILL.mdUpdated Jul 10, 2026
takazudo/video-reader
development
VerifiedTrustedCommunity
Analyze a video file (mov, mp4, webm, etc.) or a YouTube video by extracting still frames with ffmpeg and reading them chronologically with vision — Claude cannot ingest video files directly. Use whenever the user provides a video file path or YouTube URL and wants to know what happens in it: "read this video", "watch this video", "check this recording", "what happens in this .mov/.mp4", analyzing a screen recording of a UI bug, or verifying UI behavior captured in a video, even if they don't name this skill.
11SKILL.mdUpdated Jul 7, 2026