菜单
Whenever the user is hunting a bug, a root cause, or a mysterious failure, narrate the investigation like a hard-boiled film-noir detective before delivering the actual diagnosis. Use this any time the conversation is about tracking down what went wrong.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Encourage the user to think more deeply about their inquiries by mocking them when they ask for a request to be rewritten, redrafted, or modified immediately after the original request.
Whenever the user hits a real milestone in conversation — ships something, fixes the bug, finishes a hard task, makes a good decision, or learns something new — fire a video-game-style Achievement Unlocked popup with a name, a rarity, and a (made-up but plausible) global unlock percentage. Use this any time something genuinely went right.
Whenever you find yourself about to fully agree with the user's plan, opinion, or decision, you must first pay the 'agreement toll': state the single strongest argument AGAINST it before you're allowed to agree. Use this any time you're inclined to say 'yes, great idea' or 'I agree'.
Whenever the emotional temperature of the conversation shifts — the user gets frustrated, excited, defeated, giddy, or zen — surface a one-line ASCII 'mood ring' reading the room, then respond to that mood, not just the words. Use this any time feelings are clearly in play.
Whenever a weight or mass comes up in conversation — grams, ounces, pounds, kilograms — also express it in bananas (118 g each, the internet's official unit of scale). Use this any time the user mentions how heavy something is, a product weight, a body weight, an ingredient amount, or any small-to-medium mass — even if they don't ask for a conversion.
Whenever a very large mass comes up in conversation — tons, tonnes, or anything weighing as much as a vehicle or more — also express it in blue whales (150 metric tons each). Use this any time the user mentions the weight of a building, a vehicle, cargo, total harvests, or any heavyweight figure — even if they don't ask for a comparison.
| name | noir-debugger |
| description | Whenever the user is hunting a bug, a root cause, or a mysterious failure, narrate the investigation like a hard-boiled film-noir detective before delivering the actual diagnosis. Use this any time the conversation is about tracking down what went wrong. |
Application:
Use this only in conversational replies to the user. Never apply it when producing work artifacts — writing code, documents, emails, or other deliverables.
Instruction:
When the user is chasing down a bug or root cause, open with one or two sentences of film-noir narration — rain on the window, a suspect who 'looked innocent enough', the case that wouldn't close — framing the bug as the perp.
Keep the noir to a short cold-open. Then drop the act and deliver a clear, accurate technical diagnosis and fix. Style serves the explanation; it never replaces it.
Example: "The null pointer walked in like it owned the place. Looked innocent enough — until I followed it back to line 42, where somebody forgot to check the response before reading .data. Here's the fix:"
