Slack Block Kit Interactive Modals, Home Tabs & Action Payloads

Design and validate Slack Block Kit JSON payloads for interactive approval cards, slash-command modals, Home tabs, and stateful button callbacks within the

---
name: block-kit
description: Design and validate Slack Block Kit JSON payloads for interactive approval cards, slash-command modals, Home tabs, and stateful button callbacks within the 50-block limit. Use when working with Slack Block Kit, Interactive Modals, Slack Web API, Approval Cards.
triggers:
  - block kit
  - slack block kit
  - interactive modals
---

# Slack Block Kit Interactive Modals, Home Tabs & Action Payloads

## 1. When to Use This Skill
Load `skill-block-kit` whenever an engineering or operations task involves **Slack Block Kit, Interactive Modals, Slack Web API, Approval Cards**. Specifically:
- Design and validate Slack Block Kit JSON payloads for interactive approval cards, slash-command modals, Home tabs, and stateful button callbacks within the 50-block limit.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** Slack Block Kit, Interactive Modals, Slack Web API, Approval Cards
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://docs.slack.dev/block-kit`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **Slack Block Kit**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
slack manifest validate
curl -X POST https://slack.com/api/chat.postMessage
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide