content/skills/research-learning-knowledge/word-flow/SKILL.md
Word-to-card workflow skill that runs `word` first and then `card -i` for one or more explicit English words. Use when the user wants both deep word analysis and a visual card, says 词卡 / word card / word flow, or provides a clear list of English vocabulary items to turn into cards. Do not use it for raw dictionary lookup, generic English sentences, or ambiguous word targets; if the target list is unclear, ask for the exact words.
npx skillsauth add bahayonghang/my-claude-code-settings word-flowInstall 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.
一条命令完成:解词 -> 铸卡。支持多词,但只处理明确指定的目标词。
这个 workflow 明确依赖两个 skill:
wordcard -i如果 card 不可用,不要假装完成卡片生成。此时仍可先完成 word 分析,并向用户明确说明卡片阶段被阻塞。
直接传入一个或多个英文单词,空格分隔。
/word-flow Obstacle
/word-flow Serendipity Resilience Entropy
只接受“明确指定”的目标词:
/word-flow 后直接跟着的词不要把一整句英文里的所有 token 都当成目标词。若候选词不明确,先让用户给出准确词表。
收集后做两件事:
对每个单词,严格保持 word -> card -i 的顺序。
步骤 A — 解词(word)
word步骤 B — 铸信息图(card -i)
card -iword 阶段失败:跳过该词的卡片阶段,记录失败原因,继续处理其他词card -i 阶段失败:不要伪造路径;明确报告失败原因,继续处理其他词最后输出每个单词的完成情况和卡片路径,例如:
Word Flow Complete
- Obstacle: ~/Downloads/Obstacle.png
- Serendipity: ~/Downloads/Serendipity.png
- Entropy: card generation failed (dependency unavailable)
word 与 card -i,不是旧命名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.
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.