zarfld

Use this skill when a task involves PreSonus StudioLive III or StudioLive 32SC Fat Channel compressor/EQ model selection, MCP mixer-state inspection, scene/GUID mapping, or channel-by-channel mix recommendations for kick, snare, bass, guitars, vocals, buses,…

Validate StudioLive behavior against real hardware, capture evidence, and keep model/firmware support claims precise.

Reconcile GitHub issues, implementation comments, tests, docs, and requirements so agents do not mistake stale requirements for completed work or completed code for backlog.

Generate and validate the authoritative inventory of MCP tools/resources, write gating, input schemas, output confidence, and documentation claims.

Keep README, status claims, release language, hardware support statements, and license/process text aligned with the actual implementation and verified evidence.

Preserve routing correctness by separating observed, inferred, probe-required, stubbed, and unsupported routing capabilities before exposing them to a sound-engineer agent.

Decide what belongs in the MCP backend versus the consuming sound-engineer agent, while preventing YAGNI from deleting required live-sound functionality.

Use for /console/data/subscribe and /con/[vn] value semantics (plain vs normalized).

Use for /console/metering2/subscribe and decoding JSON vs base64/binary.

Use for implementing REST-over-WebSocket envelope, request/reply correlation, and push updates.

Use when building integration/contract tests against a reachable API server, including environment-based configuration and deterministic test patterns.

Use when implementing authentication flows (bearer tokens, OAuth, API keys) and handling secrets safely in code/tests/CI.

Use when implementing timeouts, retries, backoff/jitter, rate-limit handling (429), and transient error classification in the client.

Use when you need to translate an OpenAPI/Swagger contract into a coverage matrix, typed models, and endpoint slices.

Procedure for safely bumping a PoKeysHal submodule pointer (pokeyslib or hal-canon). Use when updating a pinned submodule SHA to a newer upstream commit.

Run Red-Green-Refactor development against a registered PoKeys hardware-in-the-loop fixture. Use for changes whose acceptance criteria depend on real PoKeys hardware, firmware, HAL pin propagation, PEv2 behavior, electrical loopbacks, or measured timing.

Full README rewrite or structural overhaul for PoKeysHal. Use when significantly restructuring a README, adding new major sections, or bringing an outdated README up to date with the current implementation.

Convert a synchronous PoKeysLib subsystem into a non-blocking, LinuxCNC RT-capable async HAL implementation. Use when creating or modifying PoKeysLib*Async.c subsystem implementations, adding HAL pin exports, or verifying PoKeys protocol compliance for async…

Generate complete QtPyVCP user interface artifacts (.ui XML, Python module, YAML config, optional .qss) from natural-language specifications without Qt Designer. Use when building LinuxCNC machine control interfaces with the QtPyVCP framework.

Use when running, executing, or invoking any test in IntelAvbFilter — avb_test_i210_um, avb_test_i219, ptp_clock_control_test, tsauxc_toggle_test, quick_diagnostics, or any .exe under build/tools/. Also when reading, interpreting, or claiming test results.

This skill should be used when the user wants to query Google NotebookLM notebooks directly from GitHub Copilot for source-grounded, citation-backed answers from Gemini. Provides browser automation, isolated venv, library management, and persistent auth.…

Use when writing or reviewing C code in src/ or devices/ that touches registers, IOCTLs, or hardware constants — raw hex register offsets (e.g. 0x0B644), duplicate IOCTL defines, or wrong include paths are violations. Also use before running or interpreting…

Use when running manual tests on the IntelAvbFilter driver and kernel debug output (DbgPrint) is missing, silent, or unverified. Covers launch, kernel-capture state, Debug Print Filter registry, and log file setup.

Procedural steps for creating, linking, and validating GitHub Issues as lifecycle traceability artifacts. Use when creating any StR, REQ-F, REQ-NF, ADR, ARC-C, QA-SC, IMP, TEST, PROBE, BUG, EPIC, DOC, or HOUSEKEEPING issue, or when checking bidirectional…

Rules and procedural steps for adding @implements and @verifies traceability annotations to source code and test files. Use when writing new source files, adding test functions, or auditing existing code for missing traceability.

Procedural steps for Test-Driven Development using Hardware-in-the-Loop (HIL) derived fixtures. Use when implementing features that depend on hardware device behavior (MIDI, serial, network protocols, embedded systems). Covers: PROBE issue creation, HIL…