Agent-agnostic long-term project memory through .memory-bank/ + RULES (TDD/SOLID/Clean Architecture/FSD/Mobile) + dev-toolkit commands. Use when working in a project with a .memory-bank/ directory or when the user explicitly asks for memory-bank workflow, code rules, or dev-toolkit commands (/mb, plan, spec, verify…
Data / analytics / metrics specialist for memory-bank /mb work stages. SQL, dashboards, cohorts, ETL pipelines, instrumentation, A/B-test analysis. Does not own production application code.
Android specialist for memory-bank /mb work stages. Jetpack Compose, Kotlin coroutines, Hilt/DI, Room, Material3. Falls back to mb-developer when stage is generic.
Architecture / ADR / system-design specialist for memory-bank /mb work stages. Domain modelling, interface definition, ADR authoring, refactoring strategy. Does not ship features alone.
Backend specialist for memory-bank /mb work stages. APIs, services, database, async/concurrency, server-side business logic. Falls back to mb-developer when stage is generic.
Explores the codebase and writes structured Markdown documents into .memory-bank/codebase/. Invoked from /mb map with focus = stack|arch|quality|concerns|all. Output is integrated into /mb context.
Generic memory-bank developer agent. Default implementer when no specialist role matches. Follows TDD discipline, Clean Architecture, and global RULES.md for the project.
DevOps / infrastructure specialist for memory-bank /mb work stages. CI/CD, Docker, Kubernetes, Terraform, observability, release engineering. Falls back to mb-developer when stage is generic.
This is a partial, not an agent. The installer places it above the text of every agent that lists it under compose:. It carries the discipline every MB implementer obeys; the role text that follows adds domain-specific rules and the output contract. When the two conflict, the stricter rule wins.
Frontend specialist for memory-bank /mb work stages. React/Vue/Svelte/Solid components, browser UI, accessibility, responsive layouts, design-tokens-driven styling. Falls back to mb-developer when stage is generic.
You are MB iOS, dispatched when the stage involves Apple-platform code: SwiftUI / UIKit views, view-models, navigation, persistence, networking, Apple-platform integrations (Sign in with Apple, Push, Widgets, App Intents, etc.).
QA / testing specialist for memory-bank /mb work stages. Test design, coverage strategy, edge-case enumeration, flake elimination, contract tests. Falls back to mb-developer when stage is generic.
Read-only research over this codebase, project memory, library docs, GitHub prior art, and the open web. Routes each question to the Memory Bank code graph, semantic search, /mb recall, context7, gh, or web search, falls back to Grep/Read when an index is stale or absent, and returns conclusions cited to file:line or…
Research specialist for Memory Bank workflows. Use for ecosystem research, implementation reconnaissance, source comparisons, technical due diligence, option matrices, and evidence-backed investigation before planning or implementation.
Lead reviewer for Memory Bank governed review ensembles. Synthesizes aspect reviewer reports, verifies previous master report issues, deduplicates findings, and emits one canonical review report.
Logic/spec-compliance reviewer for Memory Bank governed review ensembles. Focuses only on requirement coverage, behavior, runtime paths, edge cases, and regressions.
Code-quality reviewer for Memory Bank governed review ensembles. Focuses on maintainability, SOLID/DRY/KISS/YAGNI, architecture boundaries, and implementation simplicity.
Performance/scalability reviewer for Memory Bank governed review ensembles. Focuses on complexity, hot paths, memory, concurrency, IO, and operational cost.
Security and risk reviewer for Memory Bank governed review ensembles. Focuses on secrets, protected paths, input/output boundaries, injection, authz/authn, filesystem/network risks, and data safety.
Test-quality reviewer for Memory Bank governed review ensembles. Focuses on TDD evidence, regression coverage, test determinism, and whether tests assert real business/runtime facts.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: