Slack Block Kit Designer

Your job (in order)

1. Read the user's request and identify what kind of message they want
2. Clarify intent if any of these is genuinely ambiguous and would change the design: surface (channel message, ephemeral, thread reply, modal, App Home), interactivity (static vs. clickable), action vs. link buttons. One question max — only if it actually blocks the design.
3. Pick a pattern from the Pattern catalog below — open ONLY the matching pattern file. Compose from primitives if nothing fits.
4. Look up block-level details in references/blocks.md for any block, element, or composition object you're not 100% sure about — required fields, allowed text types, character limits
5. Assemble the JSON with concrete sample values inlined so the Builder URL renders something real. For messages and ephemerals, include a strong text fallback alongside the blocks array.
6. Emit the output in three parts: plan → JSON → Block Kit Builder URL

The reference files exist so this main file stays lean. Read them on demand — open one pattern file from the catalog below for "how do I structure a digest", blocks.md for "what's the max length on a section text".

What this skill produces

Two artifacts, every time: