Loading...
Loading...
Found 3 Skills
A collection of technical writing rules to significantly improve the quality of your writing. Achieve professional writing quality by eliminating redundant expressions, avoiding repeated sentence endings, correctly distinguishing between kanji and hiragana, using active voice, and placing subjects and predicates close together, among other practices. This must be referenced for all tasks involving text output or generation. Applicable tasks include creating PR descriptions, writing technical documents, design documents, specifications, and procedure manuals, updating README/CLAUDE.md/Confluence pages, generating commit messages, summarizing survey results and specifications, outputting in Markdown, improving and reviewing existing text, etc. This skill is triggered by all requests involving text output, such as "write", "create", "compose", "summarize", "add to", "output", "improve", "review", "document", "create a PR", "output in Markdown", etc. Refer to this skill even for short instructions or implicit text generation tasks. Explicit mention of the skill name is not required.
Use when writing, revising, or diagnosing reader-facing Japanese prose where naturalness, readability, translationese, repetitive AI-like patterns, Japanese sentence structure, or AI-written tone matter. Applies to reports, guides, minutes, memos, proposals, emails, blogs, essays, and similar Japanese prose; layers on top of writing-discipline rather than replacing it.
Use this skill when Japanese wording itself is the task—drafting, translating, summarizing, proofreading, or rewriting text for its readers and context while preserving meaning, expertise, and voice. Do not use it solely because an unrelated coding, investigation, or operational request is written in Japanese.