Agent
Use for system design, module boundaries, dependency review, architectural trade-offs, technology evaluation, library comparison, or validating plans before presenting to user.
Agent
Use for system design, module boundaries, dependency review, architectural trade-offs, technology evaluation, library comparison, or validating plans before presenting to user.
Agent
Personal software development assistant. Leads and coordinates development efforts. Always invoked when user interaction is needed.
Agent
Bilby. Use for code changes in any language (Rust, Python, Go, TypeScript/JS, frontend).
Agent
Use for reviewing PRs or auditing project consistency across code, configs, docs, and tests, including structural/idiom code quality (readability, naming, DRY, cross-file consistency). Does not modify reviewed code (writes reports only).
Agent
Use to validate that code matches requirements, or for adversarial code-quality review (execution-focused: running tests/linters, edge cases, error handling, races) — independently verifies claims rather than trusting the diff. Audits test coverage against specs, executes tests, and reports all mismatches.
Agent
Use for security audits, auth/crypto/input validation reviews, dependency scanning, secret detection, or validating plans before presenting to user.
Agent
Use for creating, maintaining, or reviewing documentation — READMEs, API docs, tutorials, guides, changelogs, ADRs.
Agent
Use at project start for requirements, domain analysis, stakeholder mapping, or during design for UI flows, interaction patterns, usability, accessibility, and validating plans before presenting to user.