{
  "context": "This criteria evaluates how effectively an engineer uses the @slack/types package to build properly typed Slack message payloads with Header Blocks. The focus is on correct usage of Header Block types for creating bold section headers and proper type definitions for message structures.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "HeaderBlock Usage",
      "description": "Uses the HeaderBlock type from @slack/types to create bold, prominent headers for each section. The implementation should properly construct HeaderBlock objects with the required structure including 'type', 'text', and 'block_id' properties.",
      "max_score": 40
    },
    {
      "name": "PlainTextElement Usage",
      "description": "Uses the PlainTextElement type for the header's text property. The implementation should properly construct text objects with 'type' set to 'plain_text' and include the text content.",
      "max_score": 20
    },
    {
      "name": "Block Type Definition",
      "description": "Uses the Block or KnownBlock union type from @slack/types to properly type the blocks array in the return value. This ensures type safety for the message payload structure.",
      "max_score": 15
    },
    {
      "name": "SectionBlock for Content",
      "description": "Uses the SectionBlock type from @slack/types to display content text below headers. The implementation should properly construct SectionBlock objects with markdown or plain text.",
      "max_score": 15
    },
    {
      "name": "Message Payload Typing",
      "description": "Properly types the returned message payload structure to match Slack Web API expectations. The MessagePayload interface should use typed blocks array rather than unknown[].",
      "max_score": 10
    }
  ]
}