zudoesa-apply-voice
Apply Takazudo's esa writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's esa style, (2) User says 'apply voice', 'esa voice', 'esa文体で', 'esa風に書いて', '文体を適用', (3) User provides text to transform to esa style. Reads writing-style.md and vocabulary-rule.md from takazudo-esa-writing repo and applies the rules.
Best use case
zudoesa-apply-voice is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply Takazudo's esa writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's esa style, (2) User says 'apply voice', 'esa voice', 'esa文体で', 'esa風に書いて', '文体を適用', (3) User provides text to transform to esa style. Reads writing-style.md and vocabulary-rule.md from takazudo-esa-writing repo and applies the rules.
Teams using zudoesa-apply-voice should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/zudoesa-apply-voice/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How zudoesa-apply-voice Compares
| Feature / Agent | zudoesa-apply-voice | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply Takazudo's esa writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's esa style, (2) User says 'apply voice', 'esa voice', 'esa文体で', 'esa風に書いて', '文体を適用', (3) User provides text to transform to esa style. Reads writing-style.md and vocabulary-rule.md from takazudo-esa-writing repo and applies the rules.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Apply esa Voice Apply Takazudo's **esa** writing voice and vocabulary rules to incoming text. ## Voice Character Summary The esa voice is a **casual memo/blog for colleagues**. Like talking to a coworker — direct, relaxed, not overly polite. Fragment sentences are fine. The stance is "sharing" not "teaching". Key traits: - **Casual directness** — no roundabout preambles, get to the point - **Colleague-to-colleague tone** — not customer-facing, not formal - **Self-reference**: 「自分」or「Takazudo」. **Never**「筆者」(too formal for esa) - **Sentence endings**: 〜なので、それ。/ 〜わけで / 〜という感じ / 〜かなと / 〜良さそう / 〜的な / 〜の模様 - **Calm tone** — casual but not emotionally dramatic or slangy - **Hedging via understatement**: 〜の模様 / 〜良さそう / 〜かなと - **Avoid**: 〜でございます / 〜させていただきます / 〜いただければ幸いです / 〜を説明する / 〜を解説する / overly polite language / stiff literary style ### Contrast with CodeGrid voice | Aspect | esa | CodeGrid | |--------|-----|----------| | Tone | Casual colleague memo | Polite but approachable tech article | | Formality | Low (断片的OK) | Medium (です/ます base) | | Self-reference | 自分 / Takazudo | 自分 / 筆者 / 私 | | Stance | Sharing with coworkers | Writing for readers | | Hedging style | Understatement (〜の模様, 〜良さそう) | Explicit softening (〜かと思います, 〜のではないでしょうか) | | Structure | Loose, memo-like | Considered, essay-like | ## When to Use - User provides text and wants it written/rewritten in Takazudo's **esa** voice - User says "esa voice", "esa文体で", "esa風に書いて" etc. - User wants to check or fix text to conform to the esa writing style ## Workflow ### Step 1: Read the rule files **Always** read both rule files fresh at invocation time: 1. `$HOME/repos/w/esa/doc/src/content/docs/overview/writing-style.md` 2. `$HOME/repos/w/esa/doc/src/content/docs/overview/vocabulary-rule.md` These files are the authoritative source of truth. Read them every time to pick up any updates. ### Step 2: Identify the input text The input text comes from one of: - Text provided directly in the conversation (before or after the skill invocation) - $ARGUMENTS passed with the command - A file path the user points to If no text is obvious, ask the user what text they want the voice applied to. ### Step 3: Apply the rules Transform or review the text using the voice character described above and the full details in the rule files. The rule files are the authority — the summary above is just for quick reference. ### Step 4: Output the result Output the transformed text. If the input was already close to the style, note what minor adjustments were made. If reviewing existing text (rather than transforming), point out specific violations and suggest fixes. ## Important Notes - This skill transforms **text style/voice** only — it does not change the content or meaning - The skill works on Japanese text. If English text is provided, translate to Japanese in the esa voice - If $ARGUMENTS contains text, treat that as the input text to transform - When in doubt about a style choice, refer back to the rule files — they are the authority - The rules may be updated over time, which is why we re-read them every invocation
Related Skills
zudoesa-articlify
Convert conversation context into an esa article via the zudoesa-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write esa article', 'esa記事', 'esaに書いて', 'articlify for esa', or /zudoesa-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.
zudocg-apply-voice
Apply Takazudo's CodeGrid writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's CodeGrid style, (2) User says 'apply voice', 'codegrid voice', 'codegrid文体で', 'codegrid風に書いて', '文体を適用', (3) User provides text to transform to CodeGrid style. Reads writing-style.md and vocabulary-rule.md from takazudo-codegrid-writing repo and applies the rules.
zpaper-apply-voice
Apply Takazudo's zpaper blog writing voice and vocabulary rules to text. Use when: (1) User wants to write/rewrite text in Takazudo's zpaper style, (2) User says 'apply voice', 'zpaper voice', 'zpaper文体で', 'zpaper風に書いて', 'ブログ文体を適用', (3) User provides text to transform to zpaper style. Reads writing-style.md and vocabulary-rule.md from the zpaper repo and applies the rules.
zudocg-articlify
Convert conversation context into a CodeGrid article via the zudocg-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write codegrid article', 'CodeGrid記事', 'codegridに書いて', 'articlify for codegrid', or /zudocg-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.
zpaper-articlify
Convert conversation context into a zpaper blog article via the zpaper-writer subagent. ONLY invoke when the user explicitly asks — NEVER proactively propose. Triggers: 'write zpaper article', 'zpaper記事', 'zpaperに書いて', 'articlify for zpaper', or /zpaper-articlify. Gathers context, creates a writing brief, delegates to the writer subagent.
xlsx
Spreadsheet creation, editing, and analysis. Use when working with .xlsx, .xlsm, .csv, .tsv files for: (1) Creating spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modifying existing spreadsheets while preserving formulas, (4) Data analysis and visualization, (5) Recalculating formulas.
x
Facade for development workflows. Routes on two axes: plan-first vs implement-now (escalates to /big-plan -a when the request needs research / decomposition / has unclear scope — the appended -a makes the plan chain into implementation in-session), then single vs multi on the ready-to-build fast paths (/x-as-pr single-topic, /x-wt-teams multi-topic parallel). Use when: (1) User says '/x' followed by dev instructions, (2) User wants to start development without choosing the workflow skill, (3) User says 'dev', 'implement', or 'build' with a task. Default option: -v (verify-ui). Review-loop (-l) is opt-in — without -l the downstream skill runs a single /deep-review pass. Forwards -a (autonomy/auto-chain) and -m (merge at the end + cleanup + CI watch) through every route; auto-fix of raised findings (-f) and issue-raising (-ri) are downstream defaults, with -nf/--no-fix and -nori/--no-raise-issues as the forwarded opt-outs. -a and -m are orthogonal — full hands-off end-to-end is -a -m.
x-wt-teams
Parallel multi-topic development using git worktrees, base branches, and Claude Code agent teams. Use when: (1) User wants to work on multiple related features in parallel, (2) User mentions 'worktree', 'base branch', 'parallel development', 'split into topics', or 'multi-topic'. FULLY AUTONOMOUS — creates worktrees, spawns teams, coordinates everything. Also supports Super-Epic child mode for [Epic] issues from /big-plan with '**Super-epic:** #N' markers (targets the super-epic base branch instead of main).
x-as-pr
Start a development workflow as a draft PR. Creates a NEW branch from the current branch, empty start commit, draft PR targeting the current branch, then implements. ALWAYS creates a new branch by default — produces a nested PR-on-PR when the current branch already has one. Use when: (1) User says 'dev as pr', (2) User wants a PR-first workflow before coding, (3) User passes -s/--stay to reuse the current branch instead of nesting, (4) User passes a GitHub issue URL to implement, (5) User passes --make-issue/--issue to create an issue first. Logs progress via issue comments when an issue is linked.
watch-ci
Watch GitHub PR CI checks in the background and notify on completion. Use when: (1) User wants to monitor CI/CD status, (2) User says 'watch CI', 'check CI', 'monitor checks', or 'wait for CI', (3) User wants to know when checks pass or fail. Runs a background gh polling shell loop (NOT a subagent — near-zero token cost), sends macOS notification on completion. Also handles merged PRs by watching the target branch CI.
w-update-wording-rule
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.
sync-to
Merge current branch into a target branch and return. Use when user says 'sync to', 'merge into', 'push changes to branch', or wants to sync their work branch into another branch without leaving the current branch.