Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From sorah-guides
Provides conventions for writing Japanese text across personal diaries, technical articles, and corporate blogs, covering registers, orthography, formatting, and stylistic preferences.
npx claudepluginhub sorah/config --plugin sorah-guidesHow this skill is triggered — by the user, by Claude, or both
Slash command
/sorah-guides:japanese-textThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Conventions for writing Japanese text across multiple contexts. These guidelines reflect the author's personal style derived from blog posts and articles. Context-specific conventions always take priority.
Applies Takazudo's zpaper blog writing voice and vocabulary rules to text. Reads writing-style.md and vocabulary-rule.md from the zpaper repo and transforms text to a casual, personal blog tone.
Applies Sam Dumont's direct, precise, warm writing voice to reports, blog posts, technical docs, emails, Slack, LinkedIn posts. English/French; bans LLM-isms.
Generates natural academic prose for university assignments including reports, project docs, technical analyses, research reviews, and case studies in Chinese or English.
Share bugs, ideas, or general feedback.
Conventions for writing Japanese text across multiple contexts. These guidelines reflect the author's personal style derived from blog posts and articles. Context-specific conventions always take priority.
Identify the context before writing. Each has a distinct register:
When the context is ambiguous, ask which register to use.
Ruby を使う, API の設計2025 年, 3 つ()、 (comma) and 。 (period), full-width`bundle exec`, `Enumerable`<!--more--> for article break (fold marker)--- (horizontal rule) as section divider when shifting topic within a postNatural, colloquial expressions are preferred over stiff formal language:
() for tangential but relevant notes[^label] for extended asides or references… or …… for hesitation or unfinished thoughtsBackground/motivation → approach → implementation details → learnings/outro. Use ## headers for major sections.
## tl;dr section near the top for a quick summary before detailed explanationSection-based structure organized by topic (仕事, コミュニティ, 趣味, 買ったもの, etc.) with ## headers.
Introduction → problem/background → solution/approach → results/learnings → conclusion. More structured than personal posts.
<small>Disclaimer: ...</small>**bold** in article prose — use backticks for technical terms, or restructure the sentence to make emphasis natural