japanese-tech-writing
Skill0 starsChanged 3 months agoNo licenceView on GitHub
日本語の技術文書・書籍原稿の文章規範。整形（一文一行、引用ブロック、脚注、コラム記法）、段落と論証の構成（パラグラフライティング）、論証の厳密さ（ツッコミどころの除去）、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。
15 other projects use a version of this, 12 of them edited.
Adopted by
Most recently taken up by
- msageha/skillsedited, first seen Nov 8, 2026
- H-ymt/skillsedited, first seen Nov 8, 2026
- snowkiss13/ja-writing-normsedited, first seen Nov 1, 2026
- fujita-pineal/claude-skillsedited, first seen Nov 1, 2026
- ymuichiro/auto-research-skilledited, first seen Oct 15, 2026
- tsubasaogawa/skillsedited, first seen Oct 13, 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 versions15 projects use a version of this.
Word for word · 1
- aToy0m0/skills★ 2100% same
Edited · 12
- fujita-pineal/claude-skills★ 269% same
- ymuichiro/auto-research-skill★ 274% same
- himadajin/skills★ 166% same
- mjun0812/skills★ 189% same
- H-ymt/skills★ 099% same
- ivgtr/claude-skills★ 0100% same
- krkrkrr/skills★ 099% same
- ktateishi/skills★ 065% same
- msageha/skills★ 095% same
- snowkiss13/ja-writing-norms★ 097% same
2 more not listed
Wrote their own version · 2
- hideki5123/agent-skill-set★ 2same name
- takatoku23/my-ai-skill★ 0same name
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 repository7 other files it gives its agents.
- agent-logSkill
- deep-understandingSkill
- git-commit-messageSkill
- git-pr-draftSkill
- git-pr-reviewSkill
- grill-meSkill
- technical-writing-revisionSkill
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.