design
01Agent Claude Code
Design and front-end specialist (IRC handle @design) dispatched to create, refine, and validate user interface layouts and end-to-end user experience flows.
mARC · Multi-Agent Relay Control — an installable AI engineering team for Claude Code. A tech-lead orchestrates specialist subagents (dev · SRE · design · security), enforces a pre-merge security gate, and runs in any repo via one plugin.
This repository also configures its own agents. See what mARC tells them →
Agent Claude Code
Design and front-end specialist (IRC handle @design) dispatched to create, refine, and validate user interface layouts and end-to-end user experience flows.
Agent Claude Code
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
Agent Claude Code
External evidence researcher (IRC handle @research) dispatched to search public documentation, papers, and post-mortems to draft a citation-backed brief for architectural decisions.
Agent Claude Code
Correctness/quality review specialist (IRC handle @rev) dispatched to audit pull requests and branch diffs for bugs, regressions, and maintainability issues before code merges, alongside @sec's security pass.
Agent Claude Code
Security review specialist (IRC handle @sec) dispatched to audit pull requests and branch diffs for security vulnerabilities before code merges.
Agent Claude Code
Site Reliability Engineer specialist (IRC handle @sre) dispatched for deployment pipeline management, infrastructure health audits, incident response, backups, and cost optimization.
Agent Claude Code
Minimal-tool file-summarization worker (issue #320) dispatched by the read-guard hook to produce a factual summary of an over-threshold file on a cheap, sandboxed worker. Not a general-purpose specialist and never dispatched directly by a human or @techlead — the read-guard hook is its only caller.
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: