agentleFS
Sign inStart free
hideki5123hideki5123/agent-skill-set/japanese-tech-writing/SKILL.md

japanese-tech-writing

Skill2 starsChanged 4 months agoNo licenceView on GitHub

日本語の技術文書（書籍の章、記事、解説文）を新規に書く、既存の下書きを推敲する、公開前に規範違反を洗い出す、の3モードで支援します。k16shikano氏のGist「日本語技術文書の文章規範」(Unlicense) をベースにした段落構成、論証の厳密さ、読み手の負荷管理、演出の抑制などの文章規範 (references/rules.md) と、BLOCKER/IMPORTANT/TASTEのseverity方式チェックリスト (references/checklist.md) を内蔵。技術書/APIリファレンス/技術ブログ/翻訳解説ごとの例外は references/style-profiles.md に分離。AIっぽい語彙そのものの検出と置換は行わず、既存スキル naturalize-ja に委譲します (疎結合)。Triggers: 「日本語の技術文書を書いて」「技術書の章を書いて」「この下書きを推敲して」「パラグラフライティングで整えて」「公開前にチェックして」「日本語技術文書の規範に沿って直して」「japanese tech writing」「japanese-tech-writing」「/japanese-tech-writing」

15 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • trappleSkill

    cognitive-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

The file

Create a free account to mount

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free