rr

153

rileyhilliard

Sync code and run commands on remote machines. Use when running tests, builds, or commands remotely, syncing files to hosts, setting up remote development, or troubleshooting rr configuration.

migrating-code

91

rileyhilliard

Safe code migrations with backward compatibility and reversibility. Use when upgrading dependencies, changing database schemas, API versioning, or transitioning between technologies.

verification-before-completion

91

rileyhilliard

Run verification commands before claiming work is complete or fixed. Use before asserting any task is done, bug is fixed, tests pass, or feature works.

visualizing-with-mermaid

91

rileyhilliard

Creates professional Mermaid diagrams with semantic styling and visual hierarchy. Use when creating flowcharts, sequence diagrams, state machines, class diagrams, or architecture visualizations.

handling-errors

91

rileyhilliard

Prevents silent failures and context loss in error handling. Use when writing try-catch blocks, designing error propagation, reviewing catch blocks, or implementing Result patterns.

fixing-flaky-tests

91

rileyhilliard

Diagnose and fix tests that pass in isolation but fail when run concurrently. Covers shared state isolation and resource conflicts. References condition-based-waiting for timing issues.

architecting-systems

91

rileyhilliard

Guides clean, scalable system architecture during the build phase. Use when designing modules, defining boundaries, structuring projects, managing dependencies, or preventing tight coupling and brittleness as systems grow.

writing-tests

91

rileyhilliard

Writes behavior-focused tests using Testing Trophy model with real dependencies. Use when writing tests, choosing test types, or avoiding anti-patterns like testing mocks.

documenting-code-comments

91

rileyhilliard

Standards for self-documenting code and minimal comments. Use when auditing inline documentation or deciding when comments add value vs clutter.

writing-plans

91

rileyhilliard

Create implementation plans with tasks grouped by subsystem. Related tasks share agent context; groups parallelize across subsystems.

design

91

rileyhilliard

Enforces precise, minimal design for dashboards and admin interfaces. Use when building SaaS UIs, data-heavy interfaces, or any product needing Jony Ive-level craft.

optimizing-performance

91

rileyhilliard

Measure-first performance optimization that balances gains against complexity. Use when addressing slow code, profiling issues, or evaluating optimization trade-offs.

condition-based-waiting

91

rileyhilliard

Fixes flaky tests by replacing arbitrary timeouts with condition polling. Use when tests fail intermittently, have setTimeout delays, or involve async operations that need proper wait conditions.

writer

91

rileyhilliard

Writing style and tone guide for human-sounding content. Use when writing documentation, READMEs, commit messages, PR descriptions, blog posts, or any user-facing content.

reading-logs

91

rileyhilliard

Analyzes logs efficiently through targeted search and iterative refinement. Use when investigating errors, debugging incidents, or analyzing patterns in application logs.

documenting-systems

91

rileyhilliard

Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation.

executing-plans

91

rileyhilliard

Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.

refactoring-code

91

rileyhilliard

Improves code structure while preserving behavior through test verification. Use when cleaning up code, reducing duplication, simplifying complexity, or reorganizing modules.

systematic-debugging

91

rileyhilliard

Four-phase debugging framework that finds root causes before proposing fixes. Use when investigating bugs, errors, unexpected behavior, failed tests, or when previous fixes haven't worked.