Claude Skills by AntheaLaffy

Compose foundation skills for adding new features to an existing project with regression-first verification. Use when planning, slicing, implementing, scheduling, or reviewing new capabilities that should preserve existing behavior, use acceptance tests, reuse prior test suites, and only opt into parity or dependency alignment when risk requires it.

Compose foundation skills for Python-to-Rust or legacy-to-Rust rewrite loops. Use when planning, slicing, dependency-aligning, bootstrapping, implementing, reviewing, promoting, or coordinating gradual replacement work that needs behavior parity first, reversible ownership, DAG execution, and rollback.

Research Rust crate candidates and their feature, API, dependency, license, build, and runtime paths for any project. Use before dependency alignment when a unit may introduce a Rust crate, use a lower backend crate, replace a capability, or hand-write behavior that an existing crate might cover.

Align dependency choices by capability coverage for any engineering project. Use after crate or library reconnaissance when deciding direct reuse, backend crate use, semantic adapter, handwritten behavior, shared dependency ownership, source expansion, or dependency risk for rewrites, feature additions, or infrastructure work.

Prove a project seam or execution environment before business logic is added. Use for CLI, API, service, Tauri command, library, FFI, subprocess, model/runtime, pipeline, or process boundaries that need smoke tests for parameters, returns, errors, logs, tracing, concurrency, resources, rollback, or disable routes.

Compile and schedule engineering work as a phase DAG. Use when units have phases, artifact dependencies, owned paths, resource locks, capacity limits, stale evidence, Git worktrees, integration waves, or a need to improve throughput without confusing shards with execution order.

Run independent engineering review gates for any work unit or batch. Use for writer/reviewer separation, role selection, compatibility regression, behavior parity, architecture, error diagnostics, IO/concurrency, Rust style, data/algorithm, product ergonomics, review batches, per-unit verdicts, and durable reports.

Teach the user a new skill or concept, within this workspace.

Cut any engineering scope into minimum independently verifiable work units. Use when planning rewrites, feature additions, audits, test work, asset/control-plane work, or any multi-step implementation that needs unit boundaries, verification, rollback, owned paths, artifacts, dependencies, or review needs.

Implement one mvsep-rs backend rewrite batch as the code-writing role. Use when the user asks to write code for a selected migration batch, create AppBackend seams, move config/formats/algorithm cache/transfer/tasks to the rewritten backend, or prepare a batch for independent review. Do not use for review-only requests.

Review one mvsep-rs rewrite batch quality gate without writing production code. Use when the user asks for behavior parity review, error tracing review, async or ergonomics review, data structure or algorithm review, Rust style audit, frontend UX audit, or promotion readiness for a mvsep-rs migration batch.

Coordinate the mvsep-rs gradual backend rewrite. Use when the user asks to continue, plan, implement, audit, or route work for replacing the old Tauri backend with the rewritten Rust backend; when updating migration state, project constraints, rewrite docs, or multi-agent rewrite workflow; or when deciding the next mvsep-rs migration batch.

Expand dependency sources and align canonical shared capabilities, Rust crate reuse, adapters, hand-written Burn gaps, fixtures, and bootstrap records for Vocal2Midi. Use before implementation when imports, native/FFI sources, dependency mismatch, shared model prerequisites, temporary dependency copies, Cargo coordination, or manifest re-cut decisions affect a unit.

Review one Vocal2Midi Rust migration unit quality gate without writing production code. Use for Python/Rust behavior parity, dependency/seam, error tracing, data/algorithm, Rust style, architecture, ergonomics, or promotion readiness.

Coordinate the Vocal2Midi Python-to-Rust rewrite. Use when the user asks to continue, plan, route, re-cut, shard, implement, audit, promote, choose serial or coordinated-parallel execution, or select the next migration unit; when shared Burn gaps, dependency source expansion, capability coverage, or workflow may change the manifest inventory.

Implement exactly one confirmed Vocal2Midi Rust migration unit as the writer role. Use when dependency discovery has accepted the boundary, canonical dependencies, and legacy public behavior seam, and the user asks to add fixtures, port behavior, or prepare one unit for review. Do not use for review-only or shared dependency coordination requests.