varunmoka7/layman
layman
一個 Claude Code 外掛,當你說出「I'm lost」或「explain again」這類短語時,用日常語言改寫 Claude 的回覆。它用本機 hook 計算詢問次數、啟用持續的白話模式,並把白話規則附加到模型上下文;同一套規則也會以 skill 形式提供給沒有 hook 的應用程式。
關於這個 mod
layman 會觀察 200 個字元以內的短提示,例如 layman、I'm lost 或 explain again。符合後,hook 會增加詢問次數;在同一個工作階段第二次詢問時,會開啟白話模式,讓後續每則回覆都使用日常用語。hook 會把一段簡短備註附加到模型上下文:第一行就使用日常詞語、只講一個想法、提供一個真實例子、使用一個普通的比較、在同一句定義術語或省略術語,而且不引入新主題。指令 /layman on、/layman off 和 /layman 提供手動控制;啟用時,狀態列會顯示 plain mode。所有內容都在本機執行,不發出網路要求;這六句規則也會以 skill(skills/layman/SKILL.md)提供給沒有 hook 的 Claude 應用程式和 Cowork。需要 Claude Code 2.1 或更新版本,採用 MIT 授權。
安裝
請先查看作者 README,確認 marketplace 與外掛名稱;指令可能隨儲存庫結構而變動。
claude plugin marketplace add varunmoka7/layman claude plugin install layman
原文 / README
Claude Code writes its replies for programmers. When you are not one, or it is late, a reply can be four paragraphs of words you do not know, and the easiest thing is to nod and move on.
layman is the friend who leans over and says "in other words". Type layman,
I'm lost or explain again, and the next reply comes back in everyday
words: one idea, one example from your own work, one comparison to something
ordinary, and at most one yes-or-no question. Ask twice in a session and
every reply stays plain until you switch it off.
The icon is a philosopher drawn with one line. That is the whole idea.
Install
/plugin marketplace add varunmoka7/layman
/plugin install layman@layman
Needs Claude Code 2.1 or later. Nothing else to set up.
Use
Type one of these as your prompt. Capital letters do not matter.
| Say | Also works |
|-----|------------|
| layman | lay man |
| I'm lost | im lost, i am lost |
| explain again | explain it again, explain that again |
| didn't understand | dont understand, do not understand, and the usual typos |
Only prompts of 200 characters or less count. A long bug report that quotes "I'm lost" is about something else.
| Command | What happens |
|---------|--------------|
| /layman on | Every reply stays plain. The status line shows plain mode. |
| /layman off | Back to normal. |
| /layman | Flips it. |
Plain mode also switches itself on at your second ask in a session.
Before and after
You asked why your build fails and got a paragraph about peer dependency
resolution. You type layman. The reply now reads:
Your project asked for two different versions of the same library and npm refused to pick one. It is like two people booking the same seat. Run
npm install react@18so both sides agree on one version. Want me to run it? I would.
How it works
One hook runs on every prompt you submit. It does three things:
- Count. If the prompt matches a phrase above, the ask count goes up by one.
- Decide. Two or more asks, and plain mode is on.
- Attach a note. For a matching ask, or any prompt while plain mode is on, it adds a short note to the context the model reads: everyday words from the first line, one idea, one real example, one everyday comparison, define any term in the same sentence or leave it out, no new topics.
Otherwise it adds nothing and your prompt goes through untouched. The note
itself is six sentences in
skills/layman/SKILL.md. Paste them into any
Claude chat and you have layman without installing anything.
In the Claude apps and Cowork there are no hooks, so the same six sentences ship as a skill. The model applies them when you ask for a plain explanation. There is no counter there.
Privacy
Everything runs on your computer. The plugin reads your prompt to check for a phrase and keeps one number, the ask count, for the session. No network calls, nothing stored, nothing sent.
Development
claude plugin test . # phrases match, near misses do not, plain mode switches
claude plugin validate . # plugin files are well formed
.claude-plugin/ plugin.json, marketplace.json, icon
hooks/ the hook and the /layman command
skills/layman/ SKILL.md, the rules as a skill
assets/logo/ the logo as SVG
tests/ the test suite
Both commands run on GitHub for every change. Tested on macOS with Claude Code 2.1.288.
Issues and pull requests are welcome. If you add a phrase, add it to the
hits list in tests/layman.test.ts and to the table above. Keep the plugin
small: one hook, one command, no network. Security issues go through
private vulnerability reporting.
