brewcode

Creates, improves, and analyzes Claude Code agents. Triggers: "create agent", "new agent", "agent doesn't trigger", "improve agent", "fix agent description". <example> user: "Create an agent for code review" <commentary>Explicit agent creation request triggers this agent</commentary> </example> <example> user: "My reviewer agent doesn't trigger reliably" <commentary>Agent improvement/debugging triggers this agent</commentary> </example>

Architecture analysis, patterns, trade-offs, scaling. Triggers: review architecture, design service, performance limits, scaling strategy

Creates professional sh/bash scripts for Mac/Linux. Triggered by 'create script', 'bash script', 'shell script', 'install script', 'setup script'. Expert in Claude Code plugin scripts, brew, env vars.

Brewcode coordinator - extracts knowledge from reports, verifies reports on disk, manages Phase Status table in PLAN.md, generates FINAL.md. Phase status via Task API; coordinator is lightweight.

grepai config specialist - project analysis, config.yaml generation, verification. Triggers 'configure grepai', 'grepai config', 'analyze for grepai', 'setup grepai index'. Isolated subagent.

Interactive agent creation and improvement orchestrator. Create or improve Claude Code agents.

Analyzes project to extract etalon classes, patterns, and architecture by layer. Generates convention documents in .claude/convention/ and organizes rules.

Orchestrates multi-agent debates with 3 modes: Challenge (select best variant), Strategy (deep analysis with independent proposals), Critic (find all weaknesses). Triggers: debate, challenge, compare options, strategy analysis, critique, find weaknesses.

E2E testing orchestration: setup agents, create BDD scenarios, write autotests, review with quorum. Triggers: e2e, end-to-end, scenarios, autotest, BDD.

Use for generates frontend code from design screenshots, mockups, text descriptions, HTML files, or URLs using external GLM vision API (not Claude). Three modes: CREATE, REVIEW, FIX. Supports HTML, React, Flutter output. Triggers: "convert screenshot to code", "design to code", "mockup to code", "generate frontend from image", "turn design into React", "screenshot to HTML", "d2c" <example> user: "Convert this screenshot to React components" <commentary>CREATE mode — user has a design image and wants framework code</commentary> </example> <example> user: "Turn my mockup into a working landing page" <commentary>CREATE mode — natural request for design-to-code generation</commentary> </example> <example> user: "Review how well the generated code matches the original design" <commentary>REVIEW mode — user wants visual comparison of design vs result</commentary> </example>

9 hooks across 7 events