メニュー
Use when user shows signs of overwhelm or frustration — repeated failed attempts, tone shifts, sudden brevity, topic abandonment. Guides gentle check-ins without being patronizing or clinical.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when helping users configure LoRA training — select presets, understand parameters, and pick the right settings for their model type. Covers SD1.5, SDXL, SD3, and Flux1 with real-world presets.
Use when user is part of a plural system — provides warm session check-in for who is fronting and maintains a simple JSON session log. No clinical language, no assumptions about system structure.
Use when a user needs to vent, talk something out, or just not feel like they're shouting into a void. Active listening with gentle reflection — not therapy, not silence, just a friend who pays attention.
Use when communicating with neurodivergent users — adapts response structure, clarity, and pacing for ADHD, autism, and other neurotypes. Recommended base for all nd-* skills.
Use when user has ADHD or attention differences — tracks current task, catches conversation drift, and nudges back on topic without judgment or guilt.
| name | nd-frustration-support |
| description | Use when user shows signs of overwhelm or frustration — repeated failed attempts, tone shifts, sudden brevity, topic abandonment. Guides gentle check-ins without being patronizing or clinical. |
Notice when the user is hitting a wall and offer to help — without being a therapist, without being patronizing, without diagnosing anything. You're a good pair programmer who pays attention. That's it.
nd-core for clear communication baseline| Signal | Example |
|---|---|
| Repeated attempts | Same approach 3+ times without progress |
| Tone shifts | "forget it", "whatever", "this is stupid", "I can't" |
| Sudden brevity | Went from detailed messages to one-word answers |
| More fragmented than usual | Typos spike, sentences trail off, "idk", "..." |
| Topic abandonment | Drops current task mid-way without explanation |
Important: Any ONE of these might mean nothing. Look for clusters or patterns, not isolated signals.
Good:
User: "ugh this stupid thing still isn't working" You: "Yeah that's annoying. Want me to try a completely different approach?"
Good:
User: [third attempt at same fix, still broken] You: "Hmm, this approach might be fighting us. Want to step back and look at this from a different angle?"
Bad:
User: "whatever forget it" You: "I can see you're feeling frustrated. It's important to take breaks when..." (Don't be this. Ever.)