Menu
CCA protocol reference — packet types, TDMA timing, 8N1 framing, QS Link fields. Points to authoritative sources, no duplication.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Investigate and patch Lutron Designer feature flags. Use when you need to find out what a named flag controls, locate where it is checked in the .NET DLLs, trace a gated UI element back through ViewModel/ModelView/Domain layers, determine whether a flag is consumed at all, or plan a new DLL patch to force-enable a flag. For the build/deploy cycle of patched DLLs, hand off to anthropic-skills:designer-deploy.
Decompile and analyze Lutron Designer .NET DLLs. Use when investigating how Designer implements a feature (account gating, channel entitlements, device model rules, toolbox platform filtering, protocol handlers), tracing an enum/attribute through the assembly stack, or cross-referencing SQLMODELINFO against in-DLL metadata. Complements designer-feature-flags (flag-specific tracing) and designer-project (project-file/DB queries).
Reverse engineer Lutron S19/LDF firmware files — HCS08 MCU, CC1101 radio, CCA protocol extraction using Ghidra and Binary Ninja MCP tools
Open and query Lutron Designer project files (.hw/.ra3) — CCA address maps, zone assignments, device inventory, link topology. Use when analyzing project structure, planning device additions, or mapping CCA zone bytes.
Gather preset/scene zone assignments from a Designer project file (.hw/.ra3) and generate data/preset-zones.json for the CCX-WiZ bridge. Use when scenes change or bridge needs updated preset data.
nRF52840 USB dongle: flash sniffer or OpenThread RCP firmware, capture and analyze Thread/802.15.4 traffic. Use when asked to switch modes, capture packets, or reflash the dongle.
| name | cca-protocol |
| description | CCA protocol reference — packet types, TDMA timing, 8N1 framing, QS Link fields. Points to authoritative sources, no duplication. |
| metadata | {"author":"alex","version":"1.0"} |
| user_invocable | false |
Do not duplicate protocol knowledge here. Read these files directly:
| File | What it contains |
|---|---|
protocol/cca.protocol.ts | The source of truth. All enums, packet types, field layouts, QS Link constants, timing, sequences, pairing presets, device fingerprints |
protocol/protocol-ui.ts | Runtime parsing: identifyPacket(), parseFieldValue(), format discrimination rules |
protocol/shared.ts | Cross-protocol encoding: level ↔ percent, fade ↔ quarter-seconds |
docs/protocols/cca/index.md | Human-readable protocol reference (packet types, addressing, commands, pairing flows) |
docs/devices/qsm.md | RE findings from QSM firmware: trampoline table, TDMA, 8N1 codec, CRC, CC1101 config, dispatch tables |
docs/protocols/qslink.md | QS Link protocol + CCA field naming mapping appendix |
# Find a packet type or constant by name
grep -n "BEACON\|beacon" protocol/cca.protocol.ts
# Find all QS Link constants
grep -n "Qs\|QS_" protocol/cca.protocol.ts
# Find field layout for a specific packet type
grep -A 20 "BTN_SHORT_A" protocol/cca.protocol.ts
# Find timing constants
grep -n "timing\|repeat\|interval\|Timing" protocol/cca.protocol.ts
# Find how a packet type is identified at runtime
grep -A 10 "0x88\|BTN_SHORT" protocol/protocol-ui.ts
# Find what C constants are generated for firmware
grep "define\|const" firmware/src/cca/cca_generated.h | head -40