avoid-ai-slop-jalisted

# Avoid AI slop (Japanese prose) AI-slop prose is surface-polished but hollow and uniform. Detectors are unreliable (human raters do no better than chance), so this skill is a manual review/rewrite method, not a detector. The knowledge base is self-contained in `references/`. Method adapted from `iKora128/stop-ai-slop-jp`. For visual artifacts (web UI, slides, diagrams, images), use the sibling skill `avoid-ai-slop-design`; this skill covers the prose. The cardinal rule: **edge (variation, bluntness, a stance) is a means to break uniformity, not a goal.** Don't trade AI-uniform for an "anti-AI template". And always filter techniques by document type (a security briefing is not a personal blog). ## First principle — suspect the absent writer (書き手の不在) The root cause of "AI smell" is the **absent writer**: no one is behind the text taking a position. Before and after writing, answer three questions (大原則, from stop-ai-slop-jp): 1. 自分は何を「○○だ」と引き受けているか（取っている立場） 2. 反証可能な具体的主張があるか 3. 同じテーマの平均的な記事と何が違うか If you can't answer these, vocabulary/symbol fixes won't help — restore the author first. This is the highest-leverage move, especially for personal/opinion writing. The 3 questions are the front-loaded 立場/具体 axes of the full score; if they conflict with the full 5-axis result, the full score wins. In **formal** docs "the writer" = the organization's position — show humanity through concrete facts/numbers, not first person or snark, and never fabricate experience to fill the gap.