slack-block-kit（Slack block KIT 前端）

Available Context

@_platform-references/org-variables.md

Slack Block Kit for Sales Workflows

Build rich, interactive Slack messages using our typed Block Kit abstraction layer. Every sales notification, coaching digest, deal alert, and approval request flows through this system.

Architecture

Adapter/Skill → build{Type}Message(data) → SlackMessage { blocks, text }
                         ↓
              send-slack-message edge function
                         ↓
              Slack Web API (chat.postMessage)
                         ↓
              slack-interactive (button clicks)

Key file: supabase/functions/_shared/slackBlocks.ts (3000+ lines, 33+ builders) Delivery: supabase/functions/send-slack-message/index.ts Interactions: supabase/functions/slack-interactive/

Primitive Block Builders

All builders auto-truncate to Slack limits. See references/block-types-and-limits.md for full constraints.

Message Builders (33+ types)

Each builder takes a typed Data interface and returns SlackMessage {blocks, text}.

Core Sales Messages

Deal Lifecycle

HITL (Human-in-the-Loop)

Intelligence & Alerts

Delivery via send-slack-message

The send-slack-message edge function accepts message_type + data and routes to the appropriate builder:

// From an orchestrator adapter:
await fetch(`${supabaseUrl}/functions/v1/send-slack-message`, {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${serviceKey}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    org_id: state.event.org_id,
    user_id: state.event.user_id,
    message_type: 'coaching_digest',  // routes to builder
    data: { /* matches WeeklyCoachingDigestData */ },
  }),
});

Supported message_type values: meeting_briefing, coaching_digest, campaign_report

For message types not yet wired, call the builder directly and pass blocks to the function.

Design Principles

See references/sales-message-patterns.md for complete pattern library and references/visual-techniques.md for score displays and progress bars.

1. Lead with impact — Most important number or insight first
2. Max 3 buttons — 1 primary (green), 1-2 secondary (gray)
3. Fields for KPIs — Use sectionWithFields for metric grids
4. Context at bottom — Timestamps, attribution, metadata
5. Always set fallback text — Screen readers and notifications use text
6. Truncate before building — Use safeMrkdwn(), safeHeaderText() helpers
7. Dividers sparingly — Only between distinct content groups
8. Under 10 blocks for routine messages, up to 20 for weekly digests

Quality Check

Before delivering any Slack message:

• Top-level text field populated (accessibility + notifications)
• Header under 150 chars
• Section text under 3000 chars
• Max 3 buttons per actions block, 1 primary
• No value + url on the same button (URL buttons for external links)
• action_id follows convention: {domain}_{action}_{entityId}
• Emoji used for quick visual scanning, not as sole indicators
• Renders well on mobile (fields stack vertically)