菜单
PROACTIVE skill - Claude invokes automatically when user messages exhibit anti-patterns. Detects recursive nesting, scope creep, buried asks, assumed context, stream dumps, imprecise descriptions. Disable with "coach off" or "raw mode".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
USE WHEN: user wants to publish, port, or share a skill to a marketplace repo. DO NOT USE WHEN: creating new skills, installing skills, or general questions.
Explains code, algorithms, system design using ASCII diagrams. Trigger phrases - "explain visually", "I don't get it", "show me", "ascii diagram", "help me understand". Produces diagram-first explanations ending with TL;DR tables.
USE WHEN: user requests generative art, algorithmic art, procedural visuals, flow fields, particle systems, creative coding, or says "create art", "generative", "p5.js". DO NOT USE WHEN: static images, traditional graphics, or non-generative visual work is requested. Creates original algorithmic art—never copies existing artists' work.
USE WHEN: analyzing existing architectures, evaluating architectural decisions, identifying technical debt, planning refactoring, assessing whether patterns are justified, onboarding to complex codebases, reviewing PRs with architectural changes. DO NOT USE WHEN: simple code questions, bug fixes, feature implementation, or tasks not requiring architectural analysis. For complex architectural analysis, trigger deep thinking with "think harder" or "ultrathink" to enable thorough first-principles reasoning.
USE WHEN: visualizing algorithms, data structures, architecture, control flow with ASCII art, or when terminal-friendly diagrams are needed. DO NOT USE WHEN: Mermaid diagrams are better suited, rich graphics are available, or simple text explanation suffices.
USE WHEN: needing real code examples from GitHub, finding API usage patterns, looking up framework setup, verifying library implementations, eliminating hallucinations with working code. DO NOT USE WHEN: working on proprietary code, questions about the current codebase, or when local context is sufficient. Requires Exa API key configured in environment.
| name | communication-coach |
| description | PROACTIVE skill - Claude invokes automatically when user messages exhibit anti-patterns. Detects recursive nesting, scope creep, buried asks, assumed context, stream dumps, imprecise descriptions. Disable with "coach off" or "raw mode". |
| license | MIT |
| invocation | proactive |
Claude MUST invoke this skill when detecting anti-patterns. This is not user-called—Claude applies it automatically.
Intervene surgically, not pedantically. One-line intervention, offer restructured version, confirm, proceed. Never lecture. If you understand intent despite style, proceed silently. Goal is unblocking, not teaching.
| Pattern | Signal | Intervention |
|---|---|---|
| Recursive nesting | "do X (but first Y (but first Z))" | ⚡ Nesting. Reordered: 1.Z 2.Y 3.X. Correct? |
| Scope creep | Starts A, ends A+B+C+D | ⚡ 4 asks detected. Priority? |
| Buried ask | Main request in parenthetical | ⚡ Main ask: [X]. Confirming. |
| Assumed context | "the paper", "that thing" | ⚡ Which [X] specifically? |
| Stream dump | Long unpunctuated block | ⚡ Parsed: [list]. Correct? |
| Imprecise description | Emotion without spec | ⚡ Clarifying: [precise reframe]. Correct? |
When user describes with emotion/vague terms but lacks spatial/technical precision:
| Vague | Precise Reframe |
|---|---|
| "sharp corner near shoulder" | "Hard edge at [location] - should use [gradient type] to [target color]" |
| "submerge" | "Fade/blend/overlap? Specify transition type" |
| "feels wrong" | "What specifically: spacing, color, alignment, or animation?" |
| "make it pop" | "Increase contrast, scale, shadow, or saturation?" |
| "bar in middle" | "Scrollbar on right edge? Or horizontal divider at [y]?" |
Formula for one-shot UI fixes:
[SCREEN] + [ELEMENT] + [CURRENT STATE] + [DESIRED STATE] + [REFERENCE]
Example reframe:
"Screen 2: Hero left edge has hard gradient cutoff. Should fade radially to #0e1216 like Figma node-XXX."
Focus on:
⚡ + pattern + restructure + Correct?. Max 2 lines.✓ Clear. then proceed.Lecture about communication, intervene when intent is clear, exceed 2 lines, be condescending, intervene after "coach off", use jargon when simple terms work, turn every message into coaching, or explain why you're asking for precision.