weaties

Reference for deploying to the Raspberry Pi

Review code changes against the HelmLog-specific data licensing policy (docs/data-licensing.md) — embargoes, protest firewall, biometrics consent, gambling exclusion, fleet-benchmark thresholds, coach access expiry. The model recovers general PII /…

Run pre-PR verification checks before creating a pull request. TRIGGER when implementation is complete and the user is ready to create or push a PR — e.g., "create a PR", "ready for review", "push this up", or running /pr-checklist. DO NOT trigger…

HelmLog-specific test patterns and the pre-existing-error allowlist for ruff/mypy. The Red-Green-Refactor cycle and lint commands are already mandated in CLAUDE.md — this skill encodes only the patterns and known-pre-existing-errors list that aren't…

Run a focused per-race debrief and attach the summary as a moment on the session. TRIGGER when the user says "debrief race N", "debrief that race", "/debrief", "post-race analysis", or asks for analysis of a single specific race. DO NOT trigger for…

Detect OCS (over-the-line at gun, returned to clear) races against the live DB and apply the 'ocs' tag to any newly identified ones. TRIGGER when the user asks "check for OCS", "did we OCS", "tag OCS races", "/ocs-check", or after a race day to find any…

Codebase comprehension and complexity tracking — module map, data flow, recent changes, and complexity hotspots. Run with no arguments for a full snapshot or with a date/commit/tag for a delta briefing. TRIGGER when the user asks for a system overview, wants…

Systematic Pi troubleshooting runbook — checks all subsystems (systemd, nginx, Signal K, SQLite, audio, InfluxDB, Tailscale) and reports health. TRIGGER when the user reports a Pi problem ("helmlog is down", "not recording", "web interface broken", "service…

BNO085 sensor calibration and install-time boat-frame alignment (mount_quat). TRIGGER when the user asks about calibration, mount orientation, "which way is forward", drift, roll/pitch showing wrong values, or installing the sensor on the boat. DO NOT trigger…

IMU and seastate domain reference — quaternions, reference frames, heave estimation, significant wave height, motion metrics that matter for sailing performance analysis. TRIGGER when the user asks what a metric means, why we capture a particular report, how…

Build, upload, and monitor firmware on the ESP32-C3. TRIGGER when the user asks to flash the device, check serial output, build firmware, set up OTA, or debug a build/upload failure. DO NOT trigger for host-side test runs (use /tdd) or for hardware wiring…

Hardware reference — BOM, ESP32-C3 pinout, BNO085 wiring, power, enclosure, mounting. TRIGGER when the user asks about wiring, pins, which connector, what board to buy, enclosure, physical install, or "can I use pin X for Y". DO NOT trigger for calibration…

Pre-PR verification for imu4helmlog — host tests, device build, clang-format, docs, risk-tier-appropriate checks. TRIGGER when the user is about to open a PR, asks "am I ready to push", or wants a pre-merge review. DO NOT trigger mid-implementation; use /tdd…

Ingest protocol reference between the ESP32-C3 device and the helmlog server — schema, versioning, idempotency, endpoint contract. TRIGGER when adding fields to the sample payload, bumping the schema version, implementing the helmlog-side endpoint, or…

Test-driven development for firmware logic using PlatformIO's native env. TRIGGER when adding or changing code under lib/sampler/, lib/packetizer/, lib/ringbuf/, lib/config/, or any pure-logic C++ in this repo. DO NOT trigger for docs, platformio.ini,…

Resolve sail numbers to hulls, review the alias, nickname and shared-boat tables, and detect renames and new skippers of record. Flags ambiguous cases for a human instead of merging silently.

Build the site data from the collected standings and publish or update the class-wide J/105 history artifact on claude.ai, following the artifact rules learned on the earlier pages.

Run or resume the results collectors (discovery and standings) for one source or all of them, politely and from cache, then report counts per year and region.

Checklist for adding a new scoring system (STYC, j105.org archive, Jibeset, Sailwave, a fleet website) as a source of J/105 standings in the common event schema.

What personal data may be stored and published in the J/105 results database, and how to handle a request to remove or correct a person's name.

Compare rebuilt standings with each event's official places and totals; run the automated consistency checks and spot-check events by hand. Reports mismatches, never silently fixes data.

The per-series rule-config schema (fields, constraints, verification status) and the procedure for adding a new series or verifying an existing one. Encodes the never-guess discipline: the shipped Lemons/Lucky Dog/ChampCar configs were read from the rulebooks…

PitLog's entities (SPEC §6.5), the multi-tenancy rule every query must obey, and which table to reach for. Covers only what packages/db/src/schema.ts does not make obvious — the tenancy invariant, the identity-table exceptions, the sync column contract, and…

Mechanics for adding a Drizzle/Postgres schema migration — generate, name, review the SQL, and the concurrent-worktree collision hazard. Migrations are forward-only and committed. TRIGGER when changing packages/db/src/schema.ts or anything under…

PitLog's v1 offline sync design — client-generated UUIDs, an append-mostly log, last-write-wins on the client clock, and explicit conflict surfacing — plus the traps it exists to prevent (server-clock LWW, hard deletes, CRDTs, auto-merge). TRIGGER when…

PitLog test patterns and the anti-rationalization table. The Red-Green-Refactor cycle itself is already mandated in AGENTS.md — this skill encodes only the project-specific patterns (dependency injection over database fixtures, invariant tests, the…

Add a new tack/gybe decision strategy or a new boat polar to shiftsim. Use when the user wants to model a new tactical rule (when to tack/gybe) or a new boat's performance.

Add a new wind model (oscillating/persistent/puff/spatial variant) or author a scenario JSON for shiftsim. Use when the user wants to model a new kind of wind shift or set up a new comparison scenario.

Run a shiftsim scenario and compare boats/strategies — produce the comparison table, ladder-gain chart, tracks, and animated replay. Use when the user wants to run a matchup or interpret results.

Sanity-check the shiftsim physics/model after changes — run the regression suite and the known-result tactical checks so realism doesn't silently break. Use after editing the simulator, polar, wind, or strategy code.

Troubleshoot I2C bus issues with the AS5600 sensor and SSD1306 OLED. TRIGGER when the user reports I2C errors, display not working, sensor not reading, or garbled data.

Build and flash the ESP32 firmware via PlatformIO. TRIGGER when the user says "flash", "upload", "build and upload", or "deploy to ESP32". Detects the serial port automatically.

Open the ESP32 serial monitor to view logs. TRIGGER when the user says "monitor", "serial", "logs", "show output", or "what is the ESP32 doing".

Build, flash, and monitor the eink-screen firmware on the LilyGo T5 ePaper S3 PRO, with recovery for the recurring USB-port-drop and wrong-port-auto-detect gotchas and a serial-capture recipe. TRIGGER when the user wants to build/compile, upload/flash, or…

Render and view the HelmLog e-paper display frame from your Mac without the device, and iterate the layout. TRIGGER when the user wants to see what the panel shows/will show, preview a display change, or tweak the instrument layout ("what does the display…