Claude Skills by lexasoft123

Build Quad Cortex presets with correct grid routing, I/O, and multi-amp/parallel topologies — and verify them. Use when creating or editing presets (especially multi-amp, parallel, or shared-front rigs), wiring inputs/outputs, sharing one pedal chain across parallel amps, or whenever a build "doesn't take" / reads come back empty. Encodes the routing rules, I/O conventions, and the reliability tricks that make building actually work over the bridge.

Reverse how a device maps a stored/normalized parameter value to its human-readable display value (linear vs logarithmic/power taper) by capturing the official app setting known values, then curve-fitting. Use when your control writes/reads parameters but the on-device display value doesn't match what you intended (e.g. "220 ms" delay actually lands at 25 ms).

Drive a native macOS app's GUI (screenshot + click + type) from the agent and correlate each action with the protocol traffic it produces, for scenario testing and reversing GUI operations you can't guess. Use when you have a working capture log (e.g. a DYLD interposer) and need to learn what messages a specific button/gesture emits, or to automate exploration of an app whose actions you must observe on the wire.

Recover Protocol Buffers message schemas (names, field numbers, types, enums) statically from a compiled binary that uses protobuf, then decode/encode messages dynamically without .proto sources. Use when an app's wire format is protobuf and you need the schema — e.g. reversing a device/app protocol whose payloads are protobuf, or reading captured protobuf traffic.

Locate and read a specific code path in a Mach-O (arm64) binary by cross-referencing a known string, using capstone — to reverse the logic around it (framing/CRC parsing, error handling, a specific handler) without a full decompiler. Use when static string clues exist and you need to read the surrounding disassembly.

Inject a DYLD interposer dylib into a hardened-runtime macOS app to hook its functions — capture the traffic it exchanges with a device/service, and optionally bridge/inject your own frames so your tool shares the app's session. Use when you need to observe or ride a signed macOS app's IOKit/network/library calls (e.g. capture a device protocol, or run alongside an app that holds a device exclusively).

Read the Quad Cortex's per-block/per-core DSP load and reduce a preset's CPU so it fits under the ~90% ceiling. Use when a preset is CPU-heavy (Cortex Control shows a high CPU meter, or blocks/Global EQ get auto-disabled), or when building multi-amp/parallel presets that risk overloading a core. Explains how the QC reports CPU, which blocks cost most, and the edits that actually lower it.

Make the Patchbay release poster and the channel post text for a version — a vertical collage of real app interface highlights plus short EN/RU copy. Use this whenever the user asks for a release poster, a Telegram/WhatsApp post or announcement for a release, an "announce v0.x" image, channel copy for a new version, or a visual to go with release notes — and whenever a release is being cut and the channel needs telling. Also use it to redo or restyle an existing poster.

Research a guitarist's/band's rig from the web and translate it faithfully to Quad Cortex amp/cab/pedal models with correct settings — including the artist's tone palette as Scenes (clean/crunch/lead/heavy/ambient). Use when a request names an artist, song, or "sound like X" and you need to find the real amps, cabs, pedals, signal chain, knob settings, and per-scene tones, map each to the closest QC catalog model, and dial the parameters. Pairs with build-preset-routing (topology) and optimiz...

Reverse the binary framing that wraps known payloads (header/trailer, command id, length, chunking/flags, CRC, compression) by aligning captured host↔device traffic against payloads you can already decode. Use after you have captured real traffic and know the payload schema (e.g. protobuf) but not how messages are delimited, routed, or reassembled on the wire.

Identify how a desktop app talks to a USB/hardware device (which transport, interface, and endpoints) before reversing its protocol. Use when a device has no public API and you need to find the control channel — e.g. "how does this app control my audio interface / pedal / synth over USB", ruling out MIDI vs raw bulk vs HID vs vendor control vs CoreAudio.

Figure out why a re-implemented client can send/receive individual messages but the device won't stream state, answer READs, or accept edits — i.e. reverse the required connect handshake and keepalive/heartbeat that makes a session "active". Use when your client talks to the device but behaves differently from the official app (no push, no stream, writes ignored).

Comprehensively review a Quad Cortex preset for correctness, tone, efficiency, and faithfulness — signal integrity/routing, I/O, gain-staging/clipping, stereo, CPU, model/cab choices, parameter sanity, scenes, and metadata. Use to audit a preset you (or someone) built before saving/shipping, to diagnose "it sounds wrong/quiet/harsh", or as the final gate of a build. Produces a grouped findings list with severities and concrete fixes.