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.
