ble-gatt-integrationlisted

# BLE GATT Integration ## Overview Use this skill to debug BLE GATT by separating advertising, connection, discovery, attributes, permissions, MTU, security, and data flow. GATT failures are often permission or state-machine mismatches, not radio failures. ## When To Use Use this skill when: - The user is creating or debugging BLE services, characteristics, descriptors, notifications, indications, reads, writes, or subscriptions. - The issue involves missing services, write failures, CCCD problems, MTU, data truncation, pairing, bonding, connection parameters, or low throughput. - The stack is Zephyr, ESP-IDF, nRF Connect SDK, NimBLE, BlueZ, Android, iOS, or a vendor BLE SDK. Do not use this skill when the device cannot advertise or connect at all. Start with platform-specific radio and controller bring-up first. ## First Questions Ask for: - BLE stack, device role, central/client app, peripheral firmware, and logs. - Advertising data, connection status, service UUIDs, characteristic UUIDs, and properties. - Attribute permissions, security level, pairing/bonding state, and CCCD state. - MTU, connection interval, PHY, data length extension, and payload size. - Sniffer trace or client error if available. ## Debug Workflow 1. Prove discovery. Confirm advertising, connection, primary service discovery, and attribute handles using a known BLE client. 1. Check attribute contract. Verify UUIDs, properties, permissions, descriptors, lengths, and endian/un