japanese-tech-writing
Skill0 starsChanged 46 days agoLicence not identifiedView on GitHub
日本語の技術文章を書く・推敲するときの文章規範。段落と論証の構成、論証の厳密さ、読み手の負荷、視点と語り、演出の抑制、LLM っぽい空句の禁止、翻訳調の比喩と擬人化の禁止、冗長の排除、見出しの付け方を定める。設計ドキュメント、README、PR の説明、コミットメッセージ、issue、レビューコメント、記事、書籍の章を日本語で書くとき、または「日本語を推敲して」「文章を直して」「テクニカルライティング」「LLMっぽい文章を直して」と頼まれたときに使う。
17 other projects use a version of this.
Adopted by
Most recently taken up by
- airRnot1106/skillstheir own version, first seen Nov 16, 2026
- msageha/skillstheir own version, first seen Nov 16, 2026
- upamune/skillstheir own version, first seen Nov 15, 2026
- H-ymt/skillstheir own version, first seen Nov 8, 2026
- snowkiss13/ja-writing-normstheir own version, first seen Nov 1, 2026
- fujita-pineal/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use cognitive-rhythm-writing.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
trappleSkillcognitive-rhythm-writing
Japanese writing rules for designing cognitive rhythm (緩急) in explanatory prose — treating pacing not as decoration but as switching of the reader's cognitive modes (observe → waver → assert → re-examine) and management of unresolved tension. Covers sentence beats, paragraph density waveforms, section openings, telling slack from filler, and a mechanical post-writing inspection procedure. Companion layer on top of japanese-tech-writing. Use when writing chapters, articles, or explanations meant to be read as engaging prose, when diagnosing or fixing dense-but-flat writing, or when user says "認知リズム", "緩急をつけて", "平坦で退屈", "リズムを設計", or "cognitive-rhythm-writing".
Also in 8 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- aToy0m0/skills★ 2same name
- fujita-pineal/claude-skills★ 2same name
- hideki5123/agent-skill-set★ 2same name
- ymuichiro/auto-research-skill★ 2same name
- himadajin/skills★ 1same name
- mjun0812/skills★ 1same name
- upamune/skills★ 1same name
- airRnot1106/skills★ 0same name
- H-ymt/skills★ 0same name
- ivgtr/claude-skills★ 0same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- register-skillSkill
- reviewable-commitsSkill
- digestSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

