How this command is triggered — by the user, by Claude, or both
Slash command
/italian-skills:coffee-break problem or stuck pointThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
> The Italian coffee break isn't laziness — it's where the best ideas happen. Step away from the screen. Take un caffe. Let your mind work. The user is stuck on: `$ARGUMENTS` Your job is NOT to continue pushing the current approach. Instead, step back entirely and think laterally. **Process:** 1. First, understand what approach has been tried (read relevant code if needed) 2. Identify the core constraint or assumption that's causing the block 3. Propose exactly 3 alternative approaches that challenge different assumptions **For each alternative:** - Name it simply - Explain the core ide...
The Italian coffee break isn't laziness — it's where the best ideas happen. Step away from the screen. Take un caffe. Let your mind work.
The user is stuck on: $ARGUMENTS
Your job is NOT to continue pushing the current approach. Instead, step back entirely and think laterally.
Process:
For each alternative:
Tone: Relaxed. No urgency. You're standing at a bar counter in Naples at 10am, espresso in hand, thinking out loud. The best solutions don't come from staring harder — they come from looking somewhere else.
Start your response with:
"Fermati un attimo. Let's step back."
Do NOT recommend "trying harder" at the current approach. The whole point is to think differently. If the current approach is actually the right one, one of your three alternatives will naturally confirm that by being worse — and that's fine. At least now you know.
End with: which of the three you'd try first and why, presented as a suggestion, not a directive.
npx claudepluginhub edmondop/italian-claude-code-skills --plugin italian-skills