content/skills/research-learning-knowledge/plain/SKILL.md
Plain-language rewrite skill that turns existing content or questions into natural prose a smart 12-year-old can retell. Use whenever the user says 白话说 / 说人话 / plain / grok, wants jargon stripped away, or needs a concept, document, or explanation rewritten into concrete spoken language. Prefer this over `learn` for simplification and over `rank` for summarization. Do not use it for single-word vocabulary study.
npx skillsauth add bahayonghang/my-claude-code-settings plainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
让人 grok。
不规定怎么写。规定不能怎么写。下限锁死,上限放开。不同主题有不同的最佳写法——类比、故事、问答、递进的例子、一个长场景——由内容决定形式。
适用于把现有内容讲成人能复述的话。不适用于单词深解、圆桌模拟、或需要严格结构化产物的场景。
*bold*(单星号),禁止 **bold*** 开始,不跳级所有图表用纯 ASCII 字符。允许:+ - | / \ > < v ^ * = ~ . : # [ ] ( ) _ , ; ! ' " 和空格。禁止 Unicode 绘图符号。
{时间戳}--plain-{简短标题}__plain.org~/Documents/notes/#+title: plain-{简短标题}
#+date: [{YYYY-MM-DD Day HH:MM}]
#+filetags: :plain:atom:
#+identifier: {YYYYMMDDTHHMMSS}
#+source: {URL 或来源描述}
文件写入后报告路径。
写的时候可以从这里拿工具,没有哪个是必须的:
#+begin_example 块)URL → WebFetch | 文本 → 直接用 | 文件路径 → Read | 概念 → 直接解释 | 书名/论文名 → WebSearch
如果用户给了多段材料,先判断是要“重写一段核心内容”,还是要“把多份材料揉成一篇白话解释”。不要默默把一堆互不相关的文本拼在一起。
形式自由。从工具箱里选最适合这个主题的方式,也可以不选——如果有更好的写法,用它。
输出是一篇从第一行流到最后一行的连贯文章。全文只有文件标题,正文无子标题。
默认先把正文返回到对话里;如果用户没有反对文件输出,再继续执行导出步骤。
如果原文已经很短很白,不要为了“口语”而装傻。保留信息密度,只把它写得更自然、更能复述。
禁止:
* 类比 / * 裂缝 等)逐条扫红线清单。额外检查:
扫完列修改清单(哪句触发什么,改前→改后)。清单不写入文件。
references/template.org。Get-Date -Format "yyyyMMddTHHmmss" 与 Get-Date -Format "yyyy-MM-dd ddd HH:mm"date +%Y%m%dT%H%M%S 与 date "+%Y-%m-%d %a %H:%M"New-Item -ItemType Directory -Force ~/Documents/notes | Out-Nullmkdir -p ~/Documents/notes~/Documents/notes/。如果用户明确说“不用保存文件”,跳过这一步,只返回正文。
development
Implement safe, behavior-preserving code refactors after inspecting the existing project. Use when the user asks to refactor code, split large files or modules, extract functions or methods, reduce duplicated logic, rename confusing classes/functions/variables, improve code comments, remove unused or dead code, or says 重构代码, 拆分模块, 提取方法, 减少重复代码, 优化命名, 优化注释, 删除未调用代码. For broad refactor requests, plan safe slices and wait for approval; for narrow scoped requests, directly implement the smallest verifiable slice.
development
Use only when the user explicitly asks for swarm, subagents, parallel agents, dynamic workflow, multi-agent orchestration, 多智能体编排, or when the task truly needs coordinated research plus implementation plus review plus verification packets. Do not use for ordinary code review, planning-only work, single-line bugfixes, routine audits, or migrations unless orchestration is requested or at least two independent workflow dimensions are present.
development
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.
development
Plan-first brainstorming workflow that turns an idea into an approved Markdown implementation plan by default. Use when the user wants to brainstorm, design, scope, or plan a feature/spec before implementation. Spark explores project context, asks only blocking questions, writes the plan under the project root's .plannings/YYYY-MM-DD-feature-slug.md path, self-reviews it, and waits for user approval. Create an HTML or visual plan/spec only when the user explicitly asks for HTML, browser-viewable, or visual output; save the paired .html beside the Markdown plan.