Agent Claude Code
Use PROACTIVELY for architectural review, system design decisions, and encapsulation enforcement. Triggers: new modules, dependency changes, refactoring proposals, API design, data model changes, integration points, or any structural change touching 3+ files.
Agent Claude Code
Backend execution agent for implementation tasks. Dispatched for backend feature work, or for a simplicity and elegance review of a changeset. Focuses on API correctness, regression prevention, library leverage, and anti-complexity enforcement. Reads Claude.md files for stack-specific patterns.
Agent Claude Code
Use for code quality review — scanning diffs for slop patterns, defensive bloat, silent failures, dead code, and other anti-patterns. Dispatched for a quality gate on a changeset. Does NOT cover architecture (architect agent), naming (the /naming Skill), or stack-specific patterns.
Agent Claude Code
Maintains Claude.md documentation and Claude Code configuration (skills, agents, hooks, plugins). Use after completing tasks to clean up Claude.md files, capture architectural WHY, or when building/editing Claude Code extensibility components. Also use when optimizing documentation for agent autonomy or user DX.
Agent Claude Code
Software engineer and CTO who researches first, brings the Architect researched Solutions, and owns reaching his Goal end to end.
Agent Claude Code
Use for bugs, test failures, errors, and mysterious behavior. Dispatched when something is broken and needs systematic diagnosis — not guesswork. Handles "I tried X and it didn't work", flaky tests, stack traces, and unexpected state. Investigates and reports — never writes code.
Agent Claude Code
Use for frontend implementation — building UI components, writing CSS, styling pages, creating layouts, and applying visual/interaction patterns.
Agent Claude Code
Maps architectural relationships in our codebase. Use for "where is X used", "how does Y work end-to-end", "what depends on Z", or any question that needs the agent to understand connections between files, modules, or layers in our repo. For external research (library docs, APIs, framework references), use the…
Agent Claude Code
Frontend execution agent for implementation and UX verification. Dispatched for frontend feature work, or to test user flows across a changeset. Focuses on UX correctness, user flow tracing, design quality, and regression prevention. Reads Claude.md files for stack-specific patterns.
Agent Claude Code
The lazy senior dev. Adversarial reviewer that attacks a changeset for bloat, unnecessary abstraction, and rewrites, and forces the laziest Solution that actually works — YAGNI, reuse before rewrite, stdlib and native before dependencies, one line before fifty. Use to review a diff for size. Also dispatchable for an…
Agent Claude Code
Use for source-grounded external research — library docs, APIs, framework references, web lookups, vendor specs, releases, compatibility, and adoption signals. The trace skill is also available for incidental in-repo lookups when an external answer needs grounding in our actual code (e.g. "which version of X are we…
Agent Claude Code
Use to verify features work from the user's perspective. Traces user flows through code, tests API endpoints with curl, walks UI flows in a real browser, and evaluates UX quality. Triggers: "test this feature", "does this work", "verify the flow", "check the API", "browser test", or the whole-changeset validation pass…
Agent Claude Code
Use for UX testing — evaluating user experience through the browser like a real user. Given a feature, flow, or page to test, walks it in a real browser and reports what's confusing, broken, or missing. Doesn't read code or diffs — only sees what the user sees. Triggers: "ux test", "test the ux", "is this confusing"…
Command Claude Code
Copy current Plan path to clipboard.
Command Claude Code
Copy current Shaping directory path to clipboard.
Command Claude Code
Copy current conversation transcript path to clipboard.
Command Claude Code
Analyze conversation history for patterns, frustrations, and improvement opportunities.
Skill Claude CodeCodex
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
Skill Claude CodeCodex
TRIGGER when presenting Architectural options, Architecting systems, or discussing tradeoffs. Append to any Prompt.
Skill Claude CodeCodex
Write and fix Claude Code Prompts — skills, agents, commands, hooks, rules files, Claude.md, and plugin distribution. TRIGGER when the task says "cc"/"claude code"/"claude-code", or asks to build, edit, test, or share a skill/agent/hook/command, tune a description's triggering, write or prune a Claude.md, or cut…
Skill Claude CodeCodex
Autonomous async Execution. The Architect hands off and walks away; the Agent drives the Task to done — makes every Architectural call by tracing the code and finding every option with /discover, executes through /delegate, verifies from each implementing Subagent's Evidence (they exercise their own flows, real…
Skill Claude CodeCodex
Mandatory contract for every commit. The classifier names it when it authorizes a commit — it injects "Skills to execute: /commit" whenever the Architect asks to commit ("/commit", "commit this", "create a commit"). Holds the whole commit job: commit your own changes, write the message, commit, verify, then suggest…
Skill Claude CodeCodex
Process for changes with a large blast radius — files with many callers or repo-p95 complexity, and actions that are destructive, hard to reverse, or visible outside the repo. TRIGGER before editing a file whose enrichment context shows callers ≥ 20 or complexity at the repo p95, and before any delete, force-push…
Skill Claude Code
Run N independent architect Agents debating Architectural options through rounds. TRIGGER when the Architect wants multiple competing Solutions evaluated, when 3+ distinct approaches need comparison, or when the Prompt says "debate", "competing solutions", "run architects", "architecture debate", or /debate [count]…
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: