Extract a self-contained subsystem out of keyboards/polykybd/ into a reusable QMK community module under modules/polykybd/ — assess the coupling, scaffold the module, convert consumers to its auto-hooks, add a mocked unit-test suite, and verify with a…
Merge upstream/master into the current branch (typically PolyKybd), resolve any conflicts, and push. Use after mirror-master-with-upstream to bring PolyKybd customisations up to date with the latest QMK changes.
Fast-forward the fork's master branch to match upstream/master exactly, then push it to origin. Use this to keep the fork's master as a clean mirror before or after a merge-upstream-into-branch run.
Measure PolyKybd firmware performance on the HIL rig and interpret the result — main-loop iteration timing, overlay-burst cost split into bridge/render/rest, HID round-trip latency, and boot-to-responsive. Drives the opt-in perf CI job (or a manual…
Cut a GitHub Release for the PolyKybd firmware (qmk_firmware), the host app (PolyKybdHost) or WinCompose (wincompose) — draft customer-facing release notes (newest version first, maintenance-only bumps skipped, concise, informative-over-funny), get the user's…
Build the PolyKybd split72 firmware and hand the user a flashable `.bin` (plus the paired DoomPack `.plyx`) for testing on real hardware. Use whenever the user asks for "a bin", "a build to test", "give me firmware", "can you build that so I can flash it", or…
Scan the current (or a past) Claude Code session for things worth keeping — (1) durable LEARNINGS (gotchas, root causes, environment/toolchain quirks, design decisions, hard-won exact commands) that belong in a CLAUDE.md / docs / memory but aren't recorded…
Adjust the PolyKybd STATUS OLED layout (the 128x64 split72 / 32x128 portrait split42 panel) — move, add, resize or re-space rows and indicator columns, and verify the result before flashing. Use when asked to "distribute the lines better", "give X more…