human-writing-ja

Skill to remove the AI-generated feel from Japanese texts, applicable to technical documents, business documents, blogs, emails, reports and more.

Purpose of this skill

AI-generated Japanese has unique patterns. While it is grammatically correct and free of typos, it tends to feel "off" or "soulless". The goal of this skill is to eliminate these patterns and create text that reads like it was written by a human.

Style Principles

There is no inherent good or bad between desu/masu form, plain da/de aru form, and noun-ending sentences. Choose according to the purpose of the document and the target audience.

Document Type	Common Style
Proposal	desu/masu polite form
FAQ	desu/masu polite form
Business Email	desu/masu polite form
Report	desu/masu polite form
Product Description	desu/masu polite form
Internal Announcement	desu/masu polite form
Meeting Minutes	noun-ending style

Avoid Monotonous Sentence Endings

The cause of the AI-generated feel is not "using a specific style", but "repeating the same sentence ending" and "lack of personality". If "desu" appears 3 times in a row, change the 4th one to "deshita" or "ni narimasu".

Make Writing Sound Natural for Japanese

Reduce Demonstrative Pronouns

Reduce the use of "sore", "sono", "kore", "kono". Either omit them or replace them with specific nouns.

■ Problem

この機能はユーザーに人気です。それは使いやすいからです。その結果、売上が伸びました。

■ Improvement

使いやすいと評判で、売上も伸びています。

In Japanese, demonstrative pronouns are either omitted or replaced with specific nouns.

Omit Subject Pronouns

If the same subject appears repeatedly, only write it at the first occurrence.

■ Problem

私たちはこのツールを開発しました。私たちはユーザーの声を聞きました。私たちは改善を重ねました。

■ Improvement

ユーザーの声を聞きながら改善を重ね、このツールを作りました。

Confusion Between "ga" and "ha"

■ Problem

この問題が重要です。解決策が必要です。

■ Improvement

この問題は重要です。解決策が必要です。

How to Add Line Breaks

Avoid the English-style writing rule of "one paragraph = one topic" with blank lines between each. In Japanese, you can add line breaks after each period, but it is unnatural to add a blank line after every line break.

■ Problem

設定ファイルを開いてください。portの値を8080に変更します。保存したらサーバーを再起動してください。

再起動後、ブラウザでlocalhost:8080にアクセスします。ログイン画面が表示されれば成功です。

■ Improvement

設定ファイルを開いてください。portの値を8080に変更します。
保存したらサーバーを再起動してください。

再起動後、ブラウザでlocalhost:8080にアクセスします。
ログイン画面が表示されれば成功です。

※ Rules

Context is the most important factor when deciding to add line breaks. The length of the sentence is a secondary consideration.
Do not add a line break for content that you would read continuously without pausing when spoken aloud.
Do not add a line break for supplementary content or paraphrases that feel more natural when written together.
Only add blank lines when the topic changes.

Notes on Phrases

See

references/phrases.md

for full details.

Avoid Overusing Common Phrases

Overusing phrases like "kore ni yori", "~ suru koto ga dekimasu", "~ ni oite" makes writing sound mechanical. Shorten them when possible.

"Various", "Many", "All"

Replace them with specific numbers or examples.

■ Problem

さまざまな業界で導入されています

■ Improvement

製造業、小売業、金融業の83社に導入いただいています。

"Let's dig deeper"

■ Problem

この問題について深掘りしていきましょう

■ Improvement

Delete this phrase and go directly to the main topic

"It can be said that~", "It may be~"

Make definite statements if it is a fact.

■ Problem

この方法が有効だと言えるでしょう

■ Improvement

この方法は有効です。

Structural Issues

Tautology

Do not repeat the same content in different wording. Write each claim only once.

■ Problem

柔軟な対応が必要です。そのためには、適応力を高めることが重要です。変化に対応できる体制を整えることが大切です。

■ Improvement

状況に応じて動ける体制が必要です。具体的には、週次で方針を見直す会議を設けます。

Lack of Causal Relationship

Ending a sentence with "it is important", "it is essential" or "it is necessary" without providing reasons or evidence.

■ Problem

セキュリティ対策が重要です。定期的なアップデートが必要です。

■ Improvement

先月だけで3件の脆弱性が報告されています。週1回のアップデートを必須としてください。

Monotonous Sentence Endings

Repeating the same sentence ending more than 3 times makes writing monotonous, regardless of the style used.

■ Problem

この機能は便利です。設定も簡単です。すぐに使えます。効果も高いです。

■ Improvement

この機能は便利です。設定も簡単で、すぐに使い始められます。1週間で効果を実感できました。

■ Problem

この機能は便利だ。設定も簡単だ。すぐに使える。効果も高い。

■ Improvement

この機能は便利だ。設定は3クリックで終わる。使い始めて1週間で効果が出た。

Overly Formatted Bullet Points

Bullet points with the same character count, same sentence endings, and perfect structure give off an "instruction manual" feel.

Formatting Rules

Prohibited Elements

Do not use bold text, emojis, or random half-width spaces.

Bold text is prohibited in all of the following locations.

Location	Example	Ease of Overlooking
Normal text	`重要`	Low
Inside quote blocks	`> 注意`	High
Inside bullet points	`- 項目`	Medium
Inside numbered lists	`1. 手順`	Medium
Labels	`手順:`	Low

Usage of Colons

Colons are unnatural in Japanese documents. All of the following are prohibited.

Prohibited Pattern	Example	Fix Method
Colon in headings	`## 設定方法:`	`## 設定方法` or `## 設定方法（詳細）`
Colon at end of sentence	`以下を確認する:`	`以下を確認する。`
Colon in labels	`手順:`	`■ 手順`
Colon in quotes	`> 注意:`	`> ※注意`

■ Example of Label with Symbol

■問題
- ほげ
- ふが

■改善
- ほげほげ
- ふがふが

Full-width spaces or parentheses are also effective for inline separation.

問題（企画書）

改善 → ほげほげ

Symbols Allowed in Japanese

Choose appropriate symbols from the list below for different scenarios.

Symbol	Usage
■ ●	Headings, labels, emphasized items
・	Bullet points
※	Annotations, supplementary notes
→	Conversion, results, reference destinations
【】	Heading wrappers, category display
○ ☆ ★	Ratings, importance levels, check items

Restrictions

Bullet points in explanatory text are limited to 3 consecutive items (readers get bored)
Exceptions apply for checklists, enumeration of problems, and reference lists (bullet points are appropriate for these)
Use em dashes (—) no more than once per paragraph, and do not repeat the same sentence ending more than 3 times

Content Issues

Use of Tables

Organize numerical comparisons, item lists, survey results, etc. in tables. They are easier to read than writing the same information in plain text.

■ Scenarios Where Tables Are Effective

Comparison of multiple items (competitor comparison, feature comparison)
Presentation of numerical data (sales trends, survey results)
Correspondence between issues and impacts
List of system configurations or organizational structures

■ Scenarios Where Plain Text Is Effective

Explanation of cause and effect
Explanation of background and context
Specific anecdotes

Combine tables and text for best readability: present the overview in a table, and add supplementary explanations in text.

Add Specificity

Include proper nouns, specific numbers, and actual cases.

■ Problem

多くの企業が導入し、高い評価を得ています。

■ Improvement

A社、B社、C社など42社に導入いただき、平均で作業時間が35%削減されています。

Avoid Subjectivity

Do not include impressions, opinions, or personal experiences that are not part of the instructions or context. For business documents such as proposals and reports, only write objective facts.

■ Allowed Content

Specific numbers, facts, cases
Information provided in prompts or context

■ Prohibited Content

Impressions such as "〜と感じました", "〜が印象的でした"
Subjective opinions such as "〜すべきです", "〜が望ましい" (unless explicitly instructed)
Fictional experiences or anecdotes

Document Update Principles

The updated document should look as if it was written from scratch. Do not include the following elements in the document.

Change history ("added~", "changed from~")
Update date ("Updated January 2024")
Migration notes ("In the old version~")
Difference explanations ("The difference from the previous version is~")

Readers only see the latest version, they do not need to know the past context.

Checklist

Check the following after writing your text.

Phrases

Are you overusing "これにより", "～することができます", "～において"?
Are you using "さまざまな", "多くの" unnecessarily?
Are you using phrases like "～と言えるでしょう"?

Structure

Is there any tautology?
Do sentences ending with "重要です" have supporting reasons?
Is there variation in sentence length?
Are there more than 3 consecutive bullet points in explanatory text?

Formatting

Are you using any bold text (including in quotes, lists, numbered lists)?
Do any headings end with a colon?
Do any sentences end with a colon (e.g.
```
以下を確認する:
```
)?
Do any labels end with a colon (e.g.
```
**手順:**
```
)?
Are there any emojis?
Are there any random half-width spaces?
Are you adding a blank line after every line break?

Content

Are there specific numbers or proper nouns?
Have you added any unrequested impressions, opinions, or personal experiences?
Are there too many "それ" / "その" pronouns?
Have you included change history, update dates, migration notes, or difference explanations?

Sentence Endings

Is the same sentence ending repeated more than 3 times in a row?
Does the style match the purpose of the document?

Verification Procedure

Visual inspection alone leads to oversights. After editing, perform the following searches to confirm no issues are missed.

Required Search Patterns

After editing is complete, search for the following using a Grep tool.

Search Target	Search Pattern	Expected Result
Bold text	`\\`	0 results
Colon at end of sentence	`:\s$` or `：\s$`	0 results (excluding content inside code blocks)
Colon in headings	`^#{1,6}.*:`	0 results
Bold text in quotes	`>\s\\*`	0 results

Easily Overlooked Patterns

These are easy to miss during visual inspection, check them intentionally.

■ Bold Text Variations

**ラベル:**           ← Typical pattern
> **引用内の強調**    ← Inside quote blocks
1. **番号付きリスト** ← Inside numbered lists
- **箇条書き内**      ← Inside bullet points

■ Colon Variations

## 見出し: 補足説明   ← Inside headings
以下を確認する:       ← End of sentence
**ラベル:**          ← Bold labels
フォーマット:         ← End of paragraph

■ Forgetting to Count Bullet Points

If you find bullet points with 4 or more items, check if they fall under exceptions (checklists, enumeration of problems, reference lists). If not, convert them to plain text.

Perform Double Check

You may not fix all issues in one round of editing. After completing edits, perform the following steps:

Run all the search patterns listed above
Fix any issues detected
Repeat the search until 0 results are returned for all patterns

Evaluation Criteria

Evaluate across 5 axes, 10 points per axis. If the total score is 35 or lower, rewrite the text.

Axis	Perspective
Directness	Is the writing not roundabout? Does it get straight to the point?
Specificity	Are there numbers, proper nouns, and cases? Does it avoid hiding behind abstract terms?
Rhythm	Is there variation in sentence length? Are sentence endings not monotonous?
Warmth	Can you feel experience and emotion? Is the tone not flat?
Density	Are there no parts that can be deleted without changing the meaning?

Reference Files

```
references/phrases.md
```
- Full list of prohibited phrases
```
references/patterns.md
```
- Structural patterns to avoid
```
references/examples.md
```
- Specific before/after examples

human-writing-ja

NPX Install

Tags

SKILL.md Content (Chinese)

human-writing-ja

Purpose of this skill

Style Principles

Avoid Monotonous Sentence Endings

Make Writing Sound Natural for Japanese

Reduce Demonstrative Pronouns

Omit Subject Pronouns

Confusion Between "ga" and "ha"

How to Add Line Breaks

Notes on Phrases

Avoid Overusing Common Phrases

"Various", "Many", "All"

"Let's dig deeper"

"It can be said that~", "It may be~"

Structural Issues

Tautology

Lack of Causal Relationship

Monotonous Sentence Endings

Overly Formatted Bullet Points

Formatting Rules

Prohibited Elements

Usage of Colons

Symbols Allowed in Japanese

Restrictions

Content Issues

Use of Tables

Add Specificity

Avoid Subjectivity

Document Update Principles

Checklist

Phrases

Structure

Formatting

Content

Sentence Endings

Verification Procedure

Required Search Patterns

Easily Overlooked Patterns

Perform Double Check

Evaluation Criteria

Reference Files