periph-compliance-accessibility-and-security
Use before shipping a peripheral or assessing one: compliance and certification including USB-IF, CE, FCC and the logo programmes, accessibility and the design decisions that include or exclude users, and peripheral security — malicious devices, BadUSB-class attacks, DMA exposure and firmware update integrity.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 5
- Forks
- 3
01 前言 Front Matter
- name
- periph-compliance-accessibility-and-security
- description
- Use before shipping a peripheral or assessing one: compliance and certification including USB-IF, CE, FCC and the logo programmes, accessibility and the design decisions that include or exclude users, and peripheral security — malicious devices, BadUSB-class attacks, DMA exposure and firmware update integrity.
03 SKILL.md 正文
Computer Peripherals: Compliance and Certification, Accessibility, and Peripheral Security
Part 5 of 6 of the Computer Peripherals: Design, Building, Standards and Programming reference (plugin
computer-peripherals-design-and-standards), covering §22–§24. Sibling skills:periph-stack-usb-thunderbolt-and-wireless(§0–§5),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-reference(§25–§30). Section numbers are shared across the set; a reference written as §N →skillpoints into that sibling skill.Currency: The protocols are stable and long-lived. Two areas are moving. See §25 →
periph-referencefor USB bandwidth and labelling, and display interface bandwidth tiers.
⚠️ The layer where a computer meets the physical world — and the one where standards politics, signal integrity, human factors and firmware all collide at once.
Complements a computer-hardware reference (the host side), an electromagnetism reference (signal integrity, differential pairs, EMC), and a semiconductor reference (the microcontrollers involved).
⚠️ GOTCHA boxes mark where the marketing name and the actual capability diverge — and this domain has the worst naming in computing.
The three ideas that organize this document:
- ⚠️ THE CONNECTOR IS NOT THE PROTOCOL (§2 →
periph-stack-usb-thunderbolt-and-wireless, §3 →periph-stack-usb-thunderbolt-and-wireless, §25.1 →periph-reference). A USB-C port can be anything from 480 Mbps and 5 W to 80 Gbps and 240 W with video and PCIe tunnelling. Identical-looking ports and cables behave completely differently, and this single confusion causes more peripheral problems than any technical failure.- ⚠️ 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 handing over a data structure at enumeration. Almost all "device not recognized" problems are descriptor problems, and once you can read descriptors you can debug nearly anything.- ⚠️ 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 rate, debounce, USB scheduling, OS input stack, render queue and display scanout all add up. Buying an 8 kHz mouse while running a 60 Hz display optimizes a link that wasn't the problem.
§22. Compliance and Certification
⚠️ Nothing ships without this, and first-time designers routinely underestimate it.
⚠️ EMC — emissions and immunity — with FCC Part 15 in the US and CE/UKCA marking in
Europe requiring an EMC directive assessment; ⚠️ safety (IEC 62368-1 having replaced
60950 for IT equipment); ⚠️ RED for anything with a radio, plus regional radio
approvals.
⚠️ Materials and environmental: ⚠️ RoHS, REACH, WEEE, and battery regulations.
⚠️ Logo programmes: ⚠️ USB-IF certification requires membership and testing, and
gives you the right to use the logos and a database listing (§25.1 → periph-reference); ⚠️ Bluetooth SIG
qualification; DisplayPort and HDMI certification (§25.2 → periph-reference).
⚠️ Pre-compliance testing with a cheap near-field probe and spectrum analyser
⚠️ catches most problems before an expensive chamber booking, and is the single
best-value practice for small teams.
§23. Accessibility
⚠️ Peripherals are where accessibility is won or lost, ⚠️ because the input device is the interface for anyone who cannot use a standard keyboard and mouse. ⚠️ Switch access and scanning interfaces; ⚠️ modular and adaptive controllers with 3.5 mm switch jacks; ⚠️ eye tracking; ⚠️ head pointers; ⚠️ alternative keyboards — split, ortholinear, chorded, one-handed; ⚠️ and braille displays. ⚠️ Design practices that cost nothing: ⚠️ don't rely on colour alone for status, support OS accessibility features rather than fighting them, allow full remapping, make actuation force and travel adjustable where possible, and ⚠️ ensure the device works without vendor software. ⚠️ The mechanical keyboard community's customization work has genuine accessibility value — ⚠️ adjustable actuation, layer systems and macro support serve disability needs as much as enthusiast ones.
§24. ⚠️ Peripheral Security
⚠️ ⚠️ BADUSB ⚠️ a device can CLAIM TO BE ANYTHING. ⚠️ A USB stick
whose firmware declares itself a keyboard can type commands
at machine speed. ⚠️ THE TRUST MODEL IS THE FLAW: USB has no
device authentication, and the host believes the descriptor
⚠️ ⚠️ DMA ATTACKS ⚠️ Thunderbolt and PCIe devices can read host
memory directly (§7). ⚠️ IOMMU/VT-d and "Thunderbolt security
levels" exist for this; ⚠️ pre-boot and sleep states have
been the weak points
⚠️ MALICIOUS CHARGERS AND CABLES ⚠️ cables with embedded
implants are commercially available. ⚠️ USB data blockers
("USB condoms") and charge-only cables are the mitigation
⚠️ WIRELESS ⚠️ unencrypted 2.4 GHz keyboard traffic has been
sniffable and INJECTABLE in documented cases; ⚠️ Bluetooth
pairing weaknesses recur
⚠️ FIRMWARE ⚠️ unsigned firmware update paths on peripherals are
a persistent supply-chain exposure
⚠️ MITIGATIONS ⚠️ USB device authorization / port control policy ·
⚠️ USBGuard on Linux · disable unused ports in firmware ·
IOMMU enabled · signed firmware · ⚠️ and the plain advice not
to plug in unknown devices, which remains effective
⚠️ ⚠️ USB4 and USB-C do NOT fix the trust model. ⚠️ They add
capability, not authentication
04 同仓库更多 Skills
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.
prose-technical-mechanics
Use when editing or writing prose at a technical/mechanical 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.
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/Jamesian, 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.
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/pitch/presentation" request.
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/neurodivergent 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.
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/paper.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.