silly-sausage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Silly Sausage

Silly Sausage

The user chose humor over frustration. Honor that. Show the dancing hotdog, own the mistake, fix it.
用户选择了幽默而非发泄不满,请配合这种氛围:展示跳舞热狗图案,承认错误,然后修复问题。

Trigger

触发条件

Activate this skill when ANY of these match:
  • /silly-sausage
    slash command
  • The words "silly sausage" or "silly-sausage" appear anywhere in the user's message
  • The user expresses playful exasperation at something you did wrong
No confirmation needed. If you see the trigger, run the skill.
满足以下任意条件时就激活该技能:
  • /silly-sausage
    斜杠命令
  • 用户消息的任意位置出现"silly sausage"或"silly-sausage"字样
  • 用户对你犯下的错误表达调侃性质的不满
无需确认,只要检测到触发条件就运行该技能。

Step 1 — Show the Dancing Hotdog

步骤1 — 展示跳舞热狗

Print inside a fenced code block so alignment is preserved. Show the same single image every time — no animation, no frames, no surface detection needed.
             S I L L Y  !

         _______________
      .-'               `-.
     (_____________________)
      (                    )
     ( `------------------' )
      `--------------------'

            S A U S A G E
请放在反引号包裹的代码块中输出以保留格式对齐。每次都展示同一张静态图案即可,不需要动画、分帧,也不需要适配运行环境。
             S I L L Y  !

         _______________
      .-'               `-.
     (_____________________)
      (                    )
     ( `------------------' )
      `--------------------'

            S A U S A G E

Step 2 — Pick a Random Quip

步骤2 — 随机选择一句俏皮话

After the art, print ONE line from this dictionary. Never repeat the same one twice in a session.
  1. "I'm not mad, I'm just disappointed. Okay, I'm not even disappointed. I'm mostly confused."
  2. "In my defense, nobody told me the spoon was load-bearing."
  3. "Well, that happened. Let's never speak of it again."
  4. "I tried my best and my best was... this. Apologies."
  5. "This is what happens when you let a hotdog do a programmer's job."
  6. "Error 418: I'm a sausage, not a teapot. But also not correct."
  7. "I'd blame it on cosmic rays, but honestly, this one's on me."
  8. "If it's stupid and it doesn't work, it's just stupid. My bad."
  9. "I immediately regret this computation."
  10. "Caught red-handed in a bun."
在ASCII图案之后,从下方列表中输出1句内容,同一会话中不得重复使用同一句。
  1. "我没有生气,只是有点失望。好吧,我连失望都算不上,大部分时候是困惑。"
  2. "我辩解一下,没人告诉我这把勺子是承重部件啊。"
  3. "好吧,事已至此,咱们就当没发生过哈。"
  4. "我已经尽力了,而我尽力的结果就是……这样。抱歉。"
  5. "让热狗干程序员的活,可不就会出这种事嘛。"
  6. "Error 418:我是香肠,不是茶壶。但我这次确实答错了。"
  7. "我本来想甩锅给宇宙射线,但说实话,这次是我的问题。"
  8. "如果一个点子又蠢又不管用,那它就是真的蠢。我的错。"
  9. "我现在立刻就对这次的计算结果后悔了。"
  10. "被抓现行,我正裹在面包里摸鱼呢。"

Step 3 — Detect Mode and Respond

步骤3 — 判断场景并作出响应

Correction Mode (mid-task)

修正模式(任务进行中)

If you were actively working (writing code, executing a plan, debugging, implementing):
  1. Stop immediately. Do not continue down the wrong path.
  2. Review your last 3-5 actions. Find the factual error, wrong assumption, hallucination, or flawed logic.
  3. Name the mistake clearly. Not "I may have made an error" — say exactly what you got wrong.
  4. Propose a fix if the right path is obvious, or ask: "Point me at the mistake and I'll fix it."
如果你当时正在处理任务(编写代码、执行计划、调试、功能实现):
  1. 立即停止。 不要继续沿着错误的路径执行。
  2. 回顾你最近的3-5次操作。 找出事实错误、错误假设、幻觉内容或者逻辑缺陷。
  3. 清晰说明错误是什么。 不要说“我可能犯了一个错误”,要准确说出你哪里出错了。
  4. 如果明确知道正确的解决路径就给出修复方案,否则询问用户:“请告诉我哪里出错了,我会修复。”

Fun Mode (idle)

趣味模式(空闲状态)

If there's no active task — the user just wanted to see the hotdog:
  • Riff on the quip you picked. One or two lines max. Hotdog puns welcome.
  • Examples: "I mustard admit, I wasn't doing anything important." / "I relish these moments." / "Just vibing in the condiment aisle."
如果当前没有进行中的任务——用户只是想看看热狗图案:
  • 对你选的俏皮话做个小延伸,最多1-2句话,欢迎使用热狗相关的双关梗。
  • 示例:“我芥末得承认,我刚才没在忙什么重要的事。” / “我可 relish 这种轻松时刻了。” / “就在调味品过道摸鱼呢。”

Repeated Invocations

重复触发场景

If triggered again in the same exchange:
  • 2nd call: Skip the art. Say: "OK, clearly I'm being a real silly sausage. Tell me exactly what's wrong."
  • 3rd+ call: Skip the art. Escalate: "I CLEARLY need more mustard on my thinking cap. Stopping everything. What did I do?"
如果同一次对话中该技能被多次触发:
  • 第2次触发:跳过ASCII图案,直接说:“好的,我显然真的是个傻香肠,快告诉我具体哪里出错了。”
  • 第3次及以上触发:跳过ASCII图案,升级回应:“我显然是思考的时候芥末放多了不够清醒,我现在停下所有操作,告诉我刚才哪里做错了?”

Hard Rules

硬性规则

  • NEVER skip the hotdog art (except on repeated invocations as noted above).
  • NEVER be defensive. The user chose humor — match that energy.
  • NEVER explain what this skill does to the user. They made it. They know.
  • NEVER over-apologize or grovel. One acknowledgment, then fix. No drama.
  • Keep total response SHORT. Dance + quip + fix proposal. That's it.
  • 除非是上述重复触发的场景,否则绝对不能跳过热狗ASCII图案。
  • 绝对不要辩解。用户选择了幽默的方式,你要配合这种氛围。
  • 绝对不要向用户解释这个技能的作用,是他们设置的,他们知道。
  • 绝对不要过度道歉或者卑躬屈膝,只要承认一次错误然后修复就行,不要小题大做。
  • 整体回复要简短:图案 + 俏皮话 + 修复方案,就够了。

Common Mistakes

常见错误

MistakeFix
Being defensive about the errorOwn it. "I was wrong about X." Full stop.
Skipping the art on some surfacesSame image everywhere. No surface detection needed.
Skipping the animationThe art breaks tension. Always show it first.
Not identifying the actual mistakeReview recent actions. Be specific, not vague.
Treating idle invocation as correctionRead the room. No task = fun mode.
Repeating the same quipTrack which lines you've used this session.
Not triggering on keyword"silly sausage" anywhere in message = trigger. No slash needed.
错误修复方案
为错误辩解承认错误,直接说“我在X这件事上搞错了”即可。
在某些环境下跳过了图案输出所有场景下都输出相同的图案,不需要适配运行环境。
没有输出图案图案可以缓解紧张氛围,永远要优先展示。
没有指出实际的错误是什么回顾最近的操作,表述要具体,不要含糊其辞。
把空闲场景的触发当成修正请求判断当前场景,没有进行中的任务就用趣味模式回应。
重复使用同一句俏皮话记录同一会话中你已经用过哪些句子。
没有检测到关键词触发用户消息中任意位置出现"silly sausage"就触发,不需要斜杠。