content/skills/learning-skills/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.
一条命令完成:解词 -> 铸信息图。支持多词,但只处理明确指定的目标词。
直接传入一个或多个英文单词,空格分隔。
/word-flow Obstacle
/word-flow Serendipity Resilience Entropy
只接受“明确指定”的目标词:
/word-flow 后直接跟着的词不要把一整句英文里的所有 token 都当成目标词。若候选词不明确,先让用户给出准确词表。
收集后做两件事:
对每个单词,严格串行执行两步:
步骤 A — 解词(word):
调用 Skill tool 执行 word,传入该单词。把 Markdown 解析结果留在对话中。
步骤 B — 铸信息图(card -i):
以步骤 A 的完整解析内容为输入,调用 Skill tool 执行 card -i。生成 PNG 文件到 ~/Downloads/。
word -> card -i 的顺序。最后输出每个单词的完成情况和 PNG 路径,例如:
Word Flow Complete
- Obstacle: ~/Downloads/Obstacle.png
- Serendipity: ~/Downloads/Serendipity.png
word 与 card -i,不是旧的 ljg-* 名称。development
Turn vague or complex Codex tasks into strong `/goal` commands with outcome, verification, constraints, boundaries, iteration policy, completion evidence, and pause/block conditions. Use when the user asks for Codex goal instructions, Goal 指令, 目标指令, `/goal` prompts, 中文 Goal 模板, plan-to-goal interviews, success criteria, verification commands, or bounded agent work definitions.
tools
Write, debug, and validate ast-grep structural code search rules. Use this skill when the user needs syntax-aware code search, AST pattern matching, structural refactor discovery, language-construct queries, or searches that plain text tools like rg can miss, such as finding functions with particular descendants, calls inside specific contexts, missing error handling, React hook shapes, decorators, or other Tree-sitter-backed code structures.
development
Use when the user asks to ground an ambitious proposal, avoid over-grand designs, make a bold direction executable, pressure-test feasibility, prevent "too much vision and too little landing", or turn a strategy/refactor/product idea into the smallest verifiable first move with stop rules. Trigger for requests such as 落地, 先落地, 别太飘, 收一收, 可执行, 可验证, 止损, and for follow-ups after geju-style big-picture thinking. Do not trigger for ordinary code review or implementation unless the user explicitly asks to ground or shrink the plan first.
development
Use when the user explicitly asks to think bigger, open up the design space, challenge conservative design, avoid over-indexing on backward compatibility, escape local-detail fixation, or make a bold high-level product or architecture direction call. Use for strategic reframing, not for ordinary code review, PRD writing, implementation planning, or adversarial risk review.