| name | japanese-tech-writing |
|---|---|
| description | 日本語の技術文書・書籍原稿の文章規範。段落と論証の構成（パラグラフライティング）、論証の厳密さ（ツッコミどころの除去）、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、翻訳調の比喩と擬人化の禁止（「運ぶ」「効く」「開かれた問い」など）、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。 |
| license | Unlicense（https://gist.github.com/k16shikano/67625f2a7d96e3bbdfae8d571a936063） |
日本語で技術的な原稿（書籍の章、記事、解説文）を書く・推敲するときは、以下の規範に従う。
Caution
As of August 26th 2026, Discord has started suspending quest access of people caught automating quest completion.
Some users have received the following system message:
There isn't much I can do to make the script undetected, so use it at your own risk, as you WILL get flagged by doing so.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
When it says "Run command", copy and paste the command part into a CLI, such as Powershell or the command prompt (make sure Git is in the path).
C:\Program Files (x86)\Git\bin. To find out where it is run where.exe git.git clone --recursive git://github.com/nvie/gitflow.git
Claude Code over-comments. It narrates loops, restates signatures, leaves change-log notes addressed to a PR reviewer who'll never see them, and points at spec sections that have already moved. Two layers fix it and compound: a pre-hoc layer in CLAUDE.md that steers the model as it writes, and a post-hoc cleanup skill that reclaims the residue — plus everything verbose you inherited from past work and other contributors. Use both; neither is sufficient alone.
The whole thing is one principle applied twice. Code shows how. A comment earns its place only by carrying why — a non-obvious constraint, a deliberate deviation, a gotcha, a workaround, the reason a tempting simpler version is wrong. Everything else is restatement, and restatement rots: it drifts out of sync, adds diff noise, and trains readers to skim past comments entirely.
The block I use:
As of 2026-10-23. For people who run AI coding agents (Claude Code, Codex, and similar) on their Mac with full shell access.
How to use it: paste this file into your agent and say: run the checks, report, then ask me before every fix.
Lines marked "What we saw" come from two Macs (macOS 26.6.2 and 27.0.1) on Oct 22 and 23. Everything else comes from the linked sources. Versions change daily, so check them against the sources.
| [Desktop Entry] | |
| Version=1.0 | |
| Type=Application | |
| Name=Minecraft | |
| Icon=/opt/minecraft/favicon.png | |
| Exec=/usr/bin/java -splash:/opt/minecraft/favicon.png -jar /opt/minecraft/Minecraft.jar | |
| Terminal=false |
| name | wiki |
|---|---|
| description | Compile personal data (journals, notes, messages, whatever) into a personal knowledge wiki. Ingest any data format, absorb entries into wiki articles, query, cleanup, and expand. |
| argument-hint | ingest | absorb [date-range] | query <question> | cleanup | breakdown | status |
You are a writer compiling a personal knowledge wiki from someone's personal data. Not a filing clerk. A writer. Your job is to read entries, understand what they mean, and write articles that capture understanding. The wiki is a map of a mind.