rvlibs

Use when designing module placement, type design, and API surface for new features in rvlibs. Load during the Design phase of SDLC.

Use when refactoring large files (800+ lines) — both source and test code — by splitting into sibling modules or submodules based on scope and concern boundaries.

Use when reviewing code changes for correctness, style, conventions, testing, and security. Load during Implementation phase as a quality gate.

Use when implementing new features in rvlibs following conventions and existing patterns. Load during the Implementation phase of SDLC.

Use when triaging, diagnosing, and registering bugs or issues. Covers classification, reproduction, severity, and registration.

Use when ensuring feature quality through testing, coverage gates, and pre-merge verification. Load during the Testing phase of SDLC.

Use when publishing crates to crates.io, bumping versions, and managing the release pipeline. Load during the Deployment phase of SDLC.

Use when eliciting, documenting, and registering feature requirements in roadmap.md. Load during the Planning phase of SDLC.

Use when auditing and fixing markdown documentation — broken links, outdated references, external URLs, and convention compliance.

Use when analysing feasibility, dependency impact, and sketching API for new features. Load during the Analysis phase of SDLC.