content/skills/learning-skills/word/SKILL.md
Deep single-word English mastery skill. Unpacks one English word's semantic image, modern usage, confusion points, and memory hook. Use when the user wants to deeply understand one English word, asks for deeper meaning or usage rather than translation, or wants a memorable vocabulary breakdown. Prefer this over `plain` or `learn` for a single vocabulary item. Do not use it for phrases, sentence translation, or multiple words at once; route multi-word card workflows to `word-flow`.
npx skillsauth add bahayonghang/my-claude-code-settings wordInstall 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.
目标不是翻译,而是让用户真正掌握这个词的深层含义和用法。
一次只处理一个英文单词。若用户给的是短语、整句或多个单词:
word-flowlearn直接在对话中用 Markdown 输出。不要写本地文件。
## {Word} /{IPA}/ {中文短译}
温暖 + 时间 + 保护 = 孕育至少覆盖这些点:
用引用格式写一句中英双语收束句:
> "English sentence. 中文金句。"
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.