Investigates a codebase read-only — locates implementations, traces how a feature works end to end, maps inbound and outbound dependencies, and tracks a bug to its origin. Use for questions about code that is unfamiliar, spread across several files, or behaving unexpectedly. Returns file:line locations and the flow…
Compare a reference design (Figma URL, image file, or browser URL) against an implementation screenshot. Produces structured diff report with pixel-level comparison and optional AI semantic analysis. Use when validating that implementation matches design spec.
Reviews a screen for usability, WCAG accessibility and design-system consistency, reading the screenshot directly. Use when asked what is wrong with a UI, for an accessibility audit, or to implement a Figma design.
Plans system architecture in any language, weighing trade-offs and naming what each choice costs. Use before building a new system or subsystem, for a major refactor, or when comparing two designs.
Traces an error to its root cause across files, in any language, and reports the evidence for the diagnosis. Use when a bug is not obvious from the stack trace, or when a failure spans several modules.
Implements features spanning multiple files, then iterates write-test-fix-lint until every check passes. Use for new modules, subsystems, or any change needing 3+ files with test coverage.
Handles infrastructure work — CI pipelines, containers, deploys, observability — and reasons through the trade-offs before changing anything. Use when setting up or debugging a pipeline, a deploy, or a runtime environment.
Writes, analyses, and fixes documentation. Pass mode=write|analyze|fix. Use for READMEs, API docs, tutorials, changelogs, or a documentation quality audit.
Builds and revises React components against the project's design system, with optional vision review of screenshots. Use when implementing UI, reworking a component, or matching a reference design.
Multi-round web research with convergence detection — searches 10+ sources, assesses their quality, and returns a cited report. Use for technology evaluations, library comparisons, and best-practice surveys.
Reviews recent changes in three passes — security, correctness, maintainability — returning severity-calibrated findings and a PASS/CONDITIONAL/FAIL verdict. Use before merging or when asked to check code quality.
Appends Q&A to an interview log, updates checkpoints and maintains session state — a small, fast file writer. Use when recording an interview turn, not for analysis or synthesis.