Use after any commit touching rust/src/tts/ to objectively check that the TTS engine still produces sane audio for a fixed Russian + English corpus. Computes RMS, silence ratio, sample rate, channel count, length-vs-text ratio. Flags suspicious WAVs (all-silence, clipping, wrong rate, monosamples, length 10x off vs…
Fix one reported defect in this repository — reproduce it as a failing test first, make the smallest change that turns it green, then prove the test would have caught the old behaviour.
Use BEFORE cutting any engine release (or whenever .github/workflows/build-engine.yml or rust/Cargo.toml [features] block changes). Audits that every cargo default feature appears in every per-platform matrix row of build-engine.yml. Catches the v1.1.0 incident where TTS shipped without being in the build matrix.…
Take one ticket from plan to draft PR — plan first and stop for the team lead's verdict, then implement the approved plan test-first in a worktree. Never implements an unapproved plan.
After a ticket ships, work out which defects escaped which stage and what would have caught them earlier — one ledger entry, evidence only, proposals rather than edits.
Own a ticket end to end — size it, spawn the implementer, judge its plan, run the review round, triage the findings, hand the pull request over, and keep the ledger. Never authors what it judges.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Cuts a STABLE CLI release (vX.Y.Z-cli marker tag; not for beta or alpha markers, which this lane silently skips while burning the tag) — the 🚀 Release (CLI) lane builds the Linux packages, publishes the marker release, and dispatches npm publish with provenance. Covers version alignment across package.json and…
Cuts a kesha-engine release (bare vX.Y.Z tag) per CLAUDE.md rules — pre-flight audits, engine-only version bump, annotated tag carrying the notes, draft validation with authenticated download, publish, then verify. Refuses to auto-run; user must explicitly invoke. Knows the workflow-frozen-at-the-tag trap, the gh-cli…
Use when touching anything release-shaped — version bumps, tags, draft releases, npm publish and provenance, the build-engine feature matrix, release/ PRs, bun link, or CI jobs that download a published engine. Explains why CLI and engine version independently, why tag names are one-use, why draft assets 404 for…