メニュー
Ganztagshelden Slack workspace communication rules. Use when composing or sending Slack messages to ensure proper thread structure, title formatting, reactions, and channel etiquette. Apply before sending any message via the Slack MCP.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Build interactive canvas-based animations with pixel-art typography, spring physics, mouse/touch interaction, and idle animations. Use when asked to create animated backgrounds, letter grids, particle effects, or any interactive canvas component for React/Next.js sites.
Use when user asks to find, search, look up, or send iMessages, texts, or SMS. Triggers on mentions of iMessage, texts, messages, "what did X text me", "find my conversation with", "send a message to", "text X", or anything involving searching or sending iMessage/SMS/RCS messages.
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. Use when writing code that depends on external packages, verifying API signatures, looking up usage patterns, generating code with specific libraries, or when training data may be outdated. Covers setup questions, migration guides, and version-specific docs.
Use when user asks to find, search, or look up WhatsApp messages, chats, or conversations. Triggers on mentions of WhatsApp, messages, chats, "what did X say", "what did X tell me", or anything involving searching WhatsApp message history.
Copy text to the system clipboard. Use when user asks to copy something to clipboard, copy to pasteboard, or wants to paste something.
Use when user asks to find, search, or look up emails in Apple Mail. Triggers on mentions of emails, inbox, messages, senders, or anything involving searching mail history.
| name | slack-workspace-rules |
| description | Ganztagshelden Slack workspace communication rules. Use when composing or sending Slack messages to ensure proper thread structure, title formatting, reactions, and channel etiquette. Apply before sending any message via the Slack MCP. |
These rules govern how messages are structured in the Ganztagshelden Slack workspace. Apply them every time you compose or send a Slack message.
Every new topic gets its own thread. Never post follow-up messages as separate top-level messages.
The thread header (top-level message) MUST follow this pattern:
:emoji: *[Title of the Topic]*
*[...]* (bold + square brackets)Examples from the workspace:
:clock8: *[Die Zeit drangt: Status Quo Multitenant]*
:burrito: *[Burbach in Altenberge - Actions]*
:slack: *[Slack Communication Design Guidelines]*
:screwdriver: *Status Quo: Multi-Tenant*
Keep discussions in public channels to avoid information silos. Only use DMs for truly private matters.
Use reactions instead of writing short reply messages:
| Reaction | Meaning |
|---|---|
| :+1: | Seen / understood |
| :white_check_mark: | Done |
| :fast_forward: | I'll handle it later |
| :heavy_plus_sign: | I agree |
*[Title]* formatSlack is for discussions, NOT for long-term documentation. Use GitHub, Excalidraw, or other tools for:
When searching Slack:
in:#channel — search within a channelfrom:@person — messages from a specific personhas:link — messages containing linksbefore:2025-09-01 / after:2025-08-01 — date ranges