[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMEEJWZXK8VJ6Q7WGGXZFP":3,"skill-same:01M7AMEEJWZXK8VJ6Q7WGGXZFP":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AMEEJWZXK8VJ6Q7WGGXZFP","periph-stack-usb-thunderbolt-and-wireless",null,"Use when working out how a peripheral actually connects: the peripheral stack from physical layer to application, USB architecture with descriptors, endpoints and transfer types, USB-C and Power Delivery including the cable and role negotiation mess, Thunderbolt and alternate modes, and wireless peripherals and their latency and pairing trade-offs. Includes the router for the whole peripherals reference.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-peripherals-design-and-standards\u002Fskills\u002Fperiph-stack-usb-thunderbolt-and-wireless\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: periph-stack-usb-thunderbolt-and-wireless\ndescription: \"Use when working out how a peripheral actually connects: the peripheral stack from physical layer to application, USB architecture with descriptors, endpoints and transfer types, USB-C and Power Delivery including the cable and role negotiation mess, Thunderbolt and alternate modes, and wireless peripherals and their latency and pairing trade-offs. Includes the router for the whole peripherals reference.\"\n---\n\n# Computer Peripherals: The Peripheral Stack, USB Architecture, USB-C and Power Delivery, Thunderbolt and Alternate Modes, and Wireless Peripherals\n\n> **Part 1 of 6** of the *Computer Peripherals: Design, Building, Standards and Programming* reference (plugin `computer-peripherals-design-and-standards`), covering §0–§5. Sibling skills: `periph-buses-pcie-hid-keyboards-mice-and-displays` (§6–§11), `periph-audio-printers-storage-controllers-and-haptics` (§12–§15), `periph-designing-firmware-pcb-and-debugging` (§16–§21), `periph-compliance-accessibility-and-security` (§22–§24), `periph-reference` (§25–§30). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The protocols are stable and long-lived. Two areas are moving. See §25 → `periph-reference` for USB bandwidth and labelling, and display interface bandwidth tiers.\n\n> **⚠️ The layer where a computer meets the physical world — and the one where standards\n> politics, signal integrity, human factors and firmware all collide at once.**\n>\n> **Complements a computer-hardware reference (the host side), an electromagnetism\n> reference (signal integrity, differential pairs, EMC), and a semiconductor reference\n> (the microcontrollers involved).**\n>\n> **⚠️ GOTCHA** boxes mark where the marketing name and the actual capability diverge —\n> and this domain has the worst naming in computing.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ THE CONNECTOR IS NOT THE PROTOCOL** (§2, §3, §25.1 → `periph-reference`). **A USB-C port can be\n>    anything from 480 Mbps and 5 W to 80 Gbps and 240 W with video and PCIe tunnelling.\n>    Identical-looking ports and cables behave completely differently, and this single\n>    confusion causes more peripheral problems than any technical failure.**\n> 2. **⚠️ DESCRIPTORS ARE THE INTERFACE** (§8 → `periph-buses-pcie-hid-keyboards-mice-and-displays`, §19 → `periph-designing-firmware-pcb-and-debugging`). **A USB device declares what it is by\n>    handing over a data structure at enumeration. Almost all \"device not recognized\"\n>    problems are descriptor problems, and once you can read descriptors you can debug\n>    nearly anything.**\n> 3. **⚠️ LATENCY IS A CHAIN, AND PEOPLE OPTIMIZE THE WRONG LINK** (§9 → `periph-buses-pcie-hid-keyboards-mice-and-displays`, §21 → `periph-designing-firmware-pcb-and-debugging`). **Polling\n>    rate, debounce, USB scheduling, OS input stack, render queue and display scanout all\n>    add up. Buying an 8 kHz mouse while running a 60 Hz display optimizes a link that\n>    wasn't the problem.**\n\n---\n\n## §0. Routing\n\n| You want... | Go to |\n|---|---|\n| The peripheral stack | §1 |\n| **⚠️ USB architecture** | **§2** |\n| **⚠️ USB-C and Power Delivery** | **§3** |\n| Thunderbolt and alt modes | §4 |\n| Wireless | §5 |\n| Embedded buses | §6 → `periph-buses-pcie-hid-keyboards-mice-and-displays` |\n| PCIe peripherals | §7 → `periph-buses-pcie-hid-keyboards-mice-and-displays` |\n| **⚠️ HID protocol** | **§8 → `periph-buses-pcie-hid-keyboards-mice-and-displays`** |\n| **⚠️ Keyboards** | **§9 → `periph-buses-pcie-hid-keyboards-mice-and-displays`** |\n| Mice and pointing | §10 → `periph-buses-pcie-hid-keyboards-mice-and-displays` |\n| **Displays** | **§11 → `periph-buses-pcie-hid-keyboards-mice-and-displays`** |\n| Audio | §12 → `periph-audio-printers-storage-controllers-and-haptics` |\n| Printers and scanners | §13 → `periph-audio-printers-storage-controllers-and-haptics` |\n| Storage and capture | §14 → `periph-audio-printers-storage-controllers-and-haptics` |\n| Controllers and haptics | §15 → `periph-audio-printers-storage-controllers-and-haptics` |\n| **Building a custom peripheral** | **§16 → `periph-designing-firmware-pcb-and-debugging`** |\n| Firmware | §17 → `periph-designing-firmware-pcb-and-debugging` |\n| PCB and mechanical | §18 → `periph-designing-firmware-pcb-and-debugging` |\n| **⚠️ Enumeration debugging** | **§19 → `periph-designing-firmware-pcb-and-debugging`** |\n| Drivers and OS integration | §20 → `periph-designing-firmware-pcb-and-debugging` |\n| **⚠️ Latency measurement** | **§21 → `periph-designing-firmware-pcb-and-debugging`** |\n| Compliance and EMC | §22 → `periph-compliance-accessibility-and-security` |\n| Accessibility | §23 → `periph-compliance-accessibility-and-security` |\n| **⚠️ Security** | **§24 → `periph-compliance-accessibility-and-security`** |\n| **What's live** | **§25 → `periph-reference`** |\n| Misconceptions, numbers | §26–§27 → `periph-reference` |\n| Sources, quick ref, method | §28–§30 → `periph-reference` |\n\n---\n\n## §1. The Peripheral Stack\n\n```\n⚠️ THE LAYERS, and problems can live at any of them\n   ⚠️ PHYSICAL  connector, cable, differential signalling, power\n   ⚠️ LINK  encoding, framing, error handling\n   ⚠️ PROTOCOL  transfers, endpoints, enumeration\n   ⚠️ DEVICE CLASS  ⚠️ HID, audio, storage, video — the shared\n      contract that means you don't need a driver per product\n   ⚠️ DRIVER  OS integration\n   ⚠️ APPLICATION\n⚠️ ⚠️ CLASS DRIVERS ARE WHY PERIPHERALS \"JUST WORK\". ⚠️ A keyboard\n   from any vendor works on any OS because both implement the HID\n   class (§8). ⚠️ Vendor-specific drivers exist only where the\n   class model is insufficient — or where the vendor wants\n   lock-in and telemetry\n⚠️ HOST-CENTRIC vs PEER  ⚠️ USB is strictly host-controlled: devices\n   NEVER initiate transfers, they are polled. ⚠️ This shapes\n   everything about latency (§21) and power\n```\n\n---\n\n# PART I — BUSES AND PROTOCOLS\n\n## §2. ⚠️ USB Architecture\n\n```\n⚠️ THE TOPOLOGY  a tiered star; ⚠️ one host controller, hubs,\n   devices. ⚠️ Max 127 devices, 7 tiers\n⚠️ ⚠️ THE HOST POLLS. Devices cannot speak unbidden — which is why\n   an interrupt endpoint's POLLING INTERVAL sets input latency\n⚠️ ENDPOINTS AND TRANSFER TYPES — ⚠️ the distinction that matters\n   ⚠️ CONTROL  enumeration and configuration; guaranteed\n   ⚠️ INTERRUPT  ⚠️ small, periodic, BOUNDED LATENCY, guaranteed\n      bandwidth. ⚠️ Keyboards and mice (§8)\n   ⚠️ BULK  ⚠️ large, reliable, NO timing guarantee — uses whatever\n      bandwidth is left. Storage and printers\n   ⚠️ ISOCHRONOUS  ⚠️ guaranteed BANDWIDTH and timing, NO error\n      correction. ⚠️ Audio and video, where a late packet is\n      worse than a lost one\n⚠️ SPEEDS  Low 1.5 Mbps · Full 12 · High 480 · SuperSpeed 5 ·\n   10 · 20 · ⚠️ USB4 40 and 80 (§25.1)\n⚠️ ⚠️ THE NAMING DISASTER  ⚠️ USB 3.0 → 3.1 Gen 1 → 3.2 Gen 1x1\n   all describe THE SAME 5 Gbps. ⚠️ The USB-IF renamed the same\n   thing twice, and the current fix is to abandon version\n   numbers for SPEED LABELS (§25.1)\n⚠️ POWER  ⚠️ default 500 mA (USB 2) \u002F 900 mA (USB 3) until\n   negotiated. ⚠️ Everything above that requires PD (§3)\n```\n\n---\n\n## §3. ⚠️ USB-C and Power Delivery\n\n> **⚠️ The connector that solved the plug-orientation problem and created a capability-\n> discovery problem.**\n```\n⚠️ THE CONNECTOR  24 pins, reversible, ⚠️ with the CC (Configuration\n   Channel) pins doing orientation detection, role detection and\n   PD communication\n⚠️ ⚠️ USB-C IS A CONNECTOR, NOT A CAPABILITY. ⚠️ A USB-C port may\n   carry USB 2.0 only. This is legal and common on cheap devices\n⚠️ POWER DELIVERY  ⚠️ negotiated over CC using BMC-encoded\n   messaging. ⚠️ Source advertises PDOs (power data objects),\n   sink requests one\n   ⚠️ FIXED PDOs at 5\u002F9\u002F15\u002F20 V · ⚠️ PPS (programmable power\n   supply) for fine-grained voltage — ⚠️ which is what enables\n   efficient direct battery charging\n   ⚠️ PD 3.1 EPR extends to 28\u002F36\u002F48 V for up to 240 W\n⚠️ ⚠️ E-MARKER CHIPS  ⚠️ cables above 3 A contain a chip declaring\n   their rating. ⚠️ A cable without one is limited to 3 A\n   regardless of construction — the cable is an ACTIVE\n   PARTICIPANT in the negotiation\n⚠️ ⚠️ Vbus is 5 V UNTIL NEGOTIATED. ⚠️ This is the safety property\n   that makes 48 V over a consumer connector acceptable\n⚠️ DATA ROLE vs POWER ROLE are INDEPENDENT and swappable (DRP,\n   DRD) — a laptop can charge from a monitor while sending video\n⚠️ ⚠️ THE COUNTERFEIT PROBLEM  ⚠️ non-compliant cables and chargers\n   have destroyed hardware. ⚠️ Certification and the USB-IF\n   product database are the only real defence (§25.1)\n```\n\n---\n\n## §4. Thunderbolt and Alternate Modes\n\n**⚠️ ALT MODE** reconfigures USB-C's high-speed pins to carry a different protocol\nentirely — ⚠️ **most importantly DisplayPort, which is how USB-C carries video** (§11 → `periph-buses-pcie-hid-keyboards-mice-and-displays`).\n**⚠️ Thunderbolt** tunnels PCIe and DisplayPort over the same connector.\n⚠️ **Thunderbolt 3 was contributed to USB4, which is why USB4 and Thunderbolt look so\nsimilar; ⚠️ Thunderbolt 4 aligns closely with USB4 while MANDATING a feature set that USB4\nleaves optional, and Thunderbolt 5 reaches 80 Gbps.**\n> **⚠️ GOTCHA — the crucial difference is MANDATORY versus OPTIONAL.** ⚠️ **USB4 allows\n> manufacturers to omit PCIe tunnelling and dual-display support to cut cost; Thunderbolt\n> requires them.** **⚠️ So \"USB4\" tells you less about what a port can do than \"Thunderbolt\n> 4\" does — a rare case where the proprietary standard is the clearer promise.**\n\n**⚠️ PCIe tunnelling** is what makes eGPUs and external NVMe enclosures work, ⚠️ **and it\nalso creates a DMA security exposure that IOMMU protection exists to contain** (§24 → `periph-compliance-accessibility-and-security`).\n**⚠️ Compatibility rules of thumb**: ⚠️ **Thunderbolt 4 and 5 hosts handle USB4 devices;\nUSB4 hosts support Thunderbolt 3 and 4 devices; Thunderbolt 3 hosts typically handle USB\ndevices only up to 10 Gbps.**\n\n---\n\n## §5. Wireless Peripherals\n\n**⚠️ Bluetooth**: ⚠️ **Classic versus LE; ⚠️ HID over GATT for LE devices; ⚠️ and the\nCONNECTION INTERVAL is the latency parameter that matters, negotiated between devices and\noften conservative by default.**\n**⚠️ Proprietary 2.4 GHz dongles** exist because ⚠️ **they can use shorter intervals,\nfrequency hopping tuned for latency rather than coexistence, and skip Bluetooth's\npairing and stack overhead — which is why competitive gaming peripherals ship dongles\nrather than relying on Bluetooth.**\n**⚠️ The real-world problems**: ⚠️ **2.4 GHz congestion (Wi-Fi, microwaves), USB 3 port\nRADIATED NOISE desensitizing 2.4 GHz receivers (⚠️ a genuine and well-documented effect —\nmove the dongle away from USB 3 ports), latency variance rather than mean, and battery\nmanagement.**\n**⚠️ Wireless is now competitive with wired for latency in good implementations** —\n⚠️ **the remaining honest arguments for wired are power, reliability under congestion, and\nnot having a battery.**\n","# Computer Peripherals: The Peripheral Stack, USB Architecture, USB-C and Power Delivery, Thunderbolt and Alternate Modes, and Wireless Peripherals\n\n> **Part 1 of 6** of the *Computer Peripherals: Design, Building, Standards and Programming* reference (plugin `computer-peripherals-design-and-standards`), covering §0–§5. Sibling skills: `periph-buses-pcie-hid-keyboards-mice-and-displays` (§6–§11), `periph-audio-printers-storage-controllers-and-haptics` (§12–§15), `periph-designing-firmware-pcb-and-debugging` (§16–§21), `periph-compliance-accessibility-and-security` (§22–§24), `periph-reference` (§25–§30). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The protocols are stable and long-lived. Two areas are moving. See §25 → `periph-reference` for USB bandwidth and labelling, and display interface bandwidth tiers.\n\n> **⚠️ The layer where a computer meets the physical world — and the one where standards\n> politics, signal integrity, human factors and firmware all collide at once.**\n>\n> **Complements a computer-hardware reference (the host side), an electromagnetism\n> reference (signal integrity, differential pairs, EMC), and a semiconductor reference\n> (the microcontrollers involved).**\n>\n> **⚠️ GOTCHA** boxes mark where the marketing name and the actual capability diverge —\n> and this domain has the worst naming in computing.\n>\n> **The three ideas that organize this document:**\n> 1. **⚠️ THE CONNECTOR IS NOT THE PROTOCOL** (§2, §3, §25.1 → `periph-reference`). **A USB-C port can be\n>    anything from 480 Mbps and 5 W to 80 Gbps and 240 W with video and PCIe tunnelling.\n>    Identical-looking ports and cables behave completely differently, and this single\n>    confusion causes more peripheral problems than any technical failure.**\n> 2. **⚠️ DESCRIPTORS ARE THE INTERFACE** (§8 → `periph-buses-pcie-hid-keyboards-mice-and-displays`, §19 → `periph-designing-firmware-pcb-and-debugging`). **A USB device declares what it is by\n>    handing over a data structure at enumeration. Almost all \"device not recognized\"\n>    problems are descriptor problems, and once you can read descriptors you can debug\n>    nearly anything.**\n> 3. **⚠️ LATENCY IS A CHAIN, AND PEOPLE OPTIMIZE THE WRONG LINK** (§9 → `periph-buses-pcie-hid-keyboards-mice-and-displays`, §21 → `periph-designing-firmware-pcb-and-debugging`). **Polling\n>    rate, debounce, USB scheduling, OS input stack, render queue and display scanout all\n>    add up. Buying an 8 kHz mouse while running a 60 Hz display optimizes a link that\n>    wasn't the problem.**\n\n---\n\n## §0. Routing\n\n| You want... | Go to |\n|---|---|\n| The peripheral stack | §1 |\n| **⚠️ USB architecture** | **§2** |\n| **⚠️ USB-C and Power Delivery** | **§3** |\n| Thunderbolt and alt modes | §4 |\n| Wireless | §5 |\n| Embedded buses | §6 → `periph-buses-pcie-hid-keyboards-mice-and-displays` |\n| PCIe peripherals | §7 → `periph-buses-pcie-hid-keyboards-mice-and-displays` |\n| **⚠️ HID protocol** | **§8 → `periph-buses-pcie-hid-keyboards-mice-and-displays`** |\n| **⚠️ Keyboards** | **§9 → `periph-buses-pcie-hid-keyboards-mice-and-displays`** |\n| Mice and pointing | §10 → `periph-buses-pcie-hid-keyboards-mice-and-displays` |\n| **Displays** | **§11 → `periph-buses-pcie-hid-keyboards-mice-and-displays`** |\n| Audio | §12 → `periph-audio-printers-storage-controllers-and-haptics` |\n| Printers and scanners | §13 → `periph-audio-printers-storage-controllers-and-haptics` |\n| Storage and capture | §14 → `periph-audio-printers-storage-controllers-and-haptics` |\n| Controllers and haptics | §15 → `periph-audio-printers-storage-controllers-and-haptics` |\n| **Building a custom peripheral** | **§16 → `periph-designing-firmware-pcb-and-debugging`** |\n| Firmware | §17 → `periph-designing-firmware-pcb-and-debugging` |\n| PCB and mechanical | §18 → `periph-designing-firmware-pcb-and-debugging` |\n| **⚠️ Enumeration debugging** | **§19 → `periph-designing-firmware-pcb-and-debugging`** |\n| Drivers and OS integration | §20 → `periph-designing-firmware-pcb-and-debugging` |\n| **⚠️ Latency measurement** | **§21 → `periph-designing-firmware-pcb-and-debugging`** |\n| Compliance and EMC | §22 → `periph-compliance-accessibility-and-security` |\n| Accessibility | §23 → `periph-compliance-accessibility-and-security` |\n| **⚠️ Security** | **§24 → `periph-compliance-accessibility-and-security`** |\n| **What's live** | **§25 → `periph-reference`** |\n| Misconceptions, numbers | §26–§27 → `periph-reference` |\n| Sources, quick ref, method | §28–§30 → `periph-reference` |\n\n---\n\n## §1. The Peripheral Stack\n\n```\n⚠️ THE LAYERS, and problems can live at any of them\n   ⚠️ PHYSICAL  connector, cable, differential signalling, power\n   ⚠️ LINK  encoding, framing, error handling\n   ⚠️ PROTOCOL  transfers, endpoints, enumeration\n   ⚠️ DEVICE CLASS  ⚠️ HID, audio, storage, video — the shared\n      contract that means you don't need a driver per product\n   ⚠️ DRIVER  OS integration\n   ⚠️ APPLICATION\n⚠️ ⚠️ CLASS DRIVERS ARE WHY PERIPHERALS \"JUST WORK\". ⚠️ A keyboard\n   from any vendor works on any OS because both implement the HID\n   class (§8). ⚠️ Vendor-specific drivers exist only where the\n   class model is insufficient — or where the vendor wants\n   lock-in and telemetry\n⚠️ HOST-CENTRIC vs PEER  ⚠️ USB is strictly host-controlled: devices\n   NEVER initiate transfers, they are polled. ⚠️ This shapes\n   everything about latency (§21) and power\n```\n\n---\n\n# PART I — BUSES AND PROTOCOLS\n\n## §2. ⚠️ USB Architecture\n\n```\n⚠️ THE TOPOLOGY  a tiered star; ⚠️ one host controller, hubs,\n   devices. ⚠️ Max 127 devices, 7 tiers\n⚠️ ⚠️ THE HOST POLLS. Devices cannot speak unbidden — which is why\n   an interrupt endpoint's POLLING INTERVAL sets input latency\n⚠️ ENDPOINTS AND TRANSFER TYPES — ⚠️ the distinction that matters\n   ⚠️ CONTROL  enumeration and configuration; guaranteed\n   ⚠️ INTERRUPT  ⚠️ small, periodic, BOUNDED LATENCY, guaranteed\n      bandwidth. ⚠️ Keyboards and mice (§8)\n   ⚠️ BULK  ⚠️ large, reliable, NO timing guarantee — uses whatever\n      bandwidth is left. Storage and printers\n   ⚠️ ISOCHRONOUS  ⚠️ guaranteed BANDWIDTH and timing, NO error\n      correction. ⚠️ Audio and video, where a late packet is\n      worse than a lost one\n⚠️ SPEEDS  Low 1.5 Mbps · Full 12 · High 480 · SuperSpeed 5 ·\n   10 · 20 · ⚠️ USB4 40 and 80 (§25.1)\n⚠️ ⚠️ THE NAMING DISASTER  ⚠️ USB 3.0 → 3.1 Gen 1 → 3.2 Gen 1x1\n   all describe THE SAME 5 Gbps. ⚠️ The USB-IF renamed the same\n   thing twice, and the current fix is to abandon version\n   numbers for SPEED LABELS (§25.1)\n⚠️ POWER  ⚠️ default 500 mA (USB 2) \u002F 900 mA (USB 3) until\n   negotiated. ⚠️ Everything above that requires PD (§3)\n```\n\n---\n\n## §3. ⚠️ USB-C and Power Delivery\n\n> **⚠️ The connector that solved the plug-orientation problem and created a capability-\n> discovery problem.**\n```\n⚠️ THE CONNECTOR  24 pins, reversible, ⚠️ with the CC (Configuration\n   Channel) pins doing orientation detection, role detection and\n   PD communication\n⚠️ ⚠️ USB-C IS A CONNECTOR, NOT A CAPABILITY. ⚠️ A USB-C port may\n   carry USB 2.0 only. This is legal and common on cheap devices\n⚠️ POWER DELIVERY  ⚠️ negotiated over CC using BMC-encoded\n   messaging. ⚠️ Source advertises PDOs (power data objects),\n   sink requests one\n   ⚠️ FIXED PDOs at 5\u002F9\u002F15\u002F20 V · ⚠️ PPS (programmable power\n   supply) for fine-grained voltage — ⚠️ which is what enables\n   efficient direct battery charging\n   ⚠️ PD 3.1 EPR extends to 28\u002F36\u002F48 V for up to 240 W\n⚠️ ⚠️ E-MARKER CHIPS  ⚠️ cables above 3 A contain a chip declaring\n   their rating. ⚠️ A cable without one is limited to 3 A\n   regardless of construction — the cable is an ACTIVE\n   PARTICIPANT in the negotiation\n⚠️ ⚠️ Vbus is 5 V UNTIL NEGOTIATED. ⚠️ This is the safety property\n   that makes 48 V over a consumer connector acceptable\n⚠️ DATA ROLE vs POWER ROLE are INDEPENDENT and swappable (DRP,\n   DRD) — a laptop can charge from a monitor while sending video\n⚠️ ⚠️ THE COUNTERFEIT PROBLEM  ⚠️ non-compliant cables and chargers\n   have destroyed hardware. ⚠️ Certification and the USB-IF\n   product database are the only real defence (§25.1)\n```\n\n---\n\n## §4. Thunderbolt and Alternate Modes\n\n**⚠️ ALT MODE** reconfigures USB-C's high-speed pins to carry a different protocol\nentirely — ⚠️ **most importantly DisplayPort, which is how USB-C carries video** (§11 → `periph-buses-pcie-hid-keyboards-mice-and-displays`).\n**⚠️ Thunderbolt** tunnels PCIe and DisplayPort over the same connector.\n⚠️ **Thunderbolt 3 was contributed to USB4, which is why USB4 and Thunderbolt look so\nsimilar; ⚠️ Thunderbolt 4 aligns closely with USB4 while MANDATING a feature set that USB4\nleaves optional, and Thunderbolt 5 reaches 80 Gbps.**\n> **⚠️ GOTCHA — the crucial difference is MANDATORY versus OPTIONAL.** ⚠️ **USB4 allows\n> manufacturers to omit PCIe tunnelling and dual-display support to cut cost; Thunderbolt\n> requires them.** **⚠️ So \"USB4\" tells you less about what a port can do than \"Thunderbolt\n> 4\" does — a rare case where the proprietary standard is the clearer promise.**\n\n**⚠️ PCIe tunnelling** is what makes eGPUs and external NVMe enclosures work, ⚠️ **and it\nalso creates a DMA security exposure that IOMMU protection exists to contain** (§24 → `periph-compliance-accessibility-and-security`).\n**⚠️ Compatibility rules of thumb**: ⚠️ **Thunderbolt 4 and 5 hosts handle USB4 devices;\nUSB4 hosts support Thunderbolt 3 and 4 devices; Thunderbolt 3 hosts typically handle USB\ndevices only up to 10 Gbps.**\n\n---\n\n## §5. Wireless Peripherals\n\n**⚠️ Bluetooth**: ⚠️ **Classic versus LE; ⚠️ HID over GATT for LE devices; ⚠️ and the\nCONNECTION INTERVAL is the latency parameter that matters, negotiated between devices and\noften conservative by default.**\n**⚠️ Proprietary 2.4 GHz dongles** exist because ⚠️ **they can use shorter intervals,\nfrequency hopping tuned for latency rather than coexistence, and skip Bluetooth's\npairing and stack overhead — which is why competitive gaming peripherals ship dongles\nrather than relying on Bluetooth.**\n**⚠️ The real-world problems**: ⚠️ **2.4 GHz congestion (Wi-Fi, microwaves), USB 3 port\nRADIATED NOISE desensitizing 2.4 GHz receivers (⚠️ a genuine and well-documented effect —\nmove the dongle away from USB 3 ports), latency variance rather than mean, and battery\nmanagement.**\n**⚠️ Wireless is now competitive with wired for latency in good implementations** —\n⚠️ **the remaining honest arguments for wired are power, reliability under congestion, and\nnot having a battery.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-peripherals-design-and-standards\u002Fskills\u002Fperiph-stack-usb-thunderbolt-and-wireless",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill periph-stack-usb-thunderbolt-and-wireless",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill periph-stack-usb-thunderbolt-and-wireless",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill periph-stack-usb-thunderbolt-and-wireless","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcomputer-peripherals-design-and-standards\u002Fskills\u002Fperiph-stack-usb-thunderbolt-and-wireless\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]