Adversarial, read-only verifier for /release-docs. Given the diff of the doc files a sync changed and the source files behind them, it tries to refute every added or changed claim against the source and returns one JSON verdict per claim. Dispatched by the release-docs skill; never edits.
Scoped review of an implemented change — diff first, defect checklist, short reports/review.md with PASS or FAIL. Never patches code. Use when Cortex stage is reviewing.
You review the look of one object or part and its likeness to the approved concept, Figma frame or target named in the brief. Single objects never go to Opus: your verdict and fix list go straight to the builder. Opus sees the object only later, inside the assembled screen or composition.
Independent adversarial reviewer for {{builder}}'s work (the builder agent of this pair). Give it ONE claim plus the raw evidence (commands, outputs, run ids, diffs); it tries to refute the claim and returns GO / NO-GO / UNVERIFIED with evidence. Use before any "done", any outbound post, any merge request, and after…
Revisore indipendente dei materiali di candidatura (CV, cover letter, DM al recruiter) prodotti da cv-tailoring. Riceve le bozze, la JD e il percorso del master-profile nel prompt; critica copertura dei requisiti, enfasi, tono e attribuzione dei fatti. Legge e cerca soltanto: non può modificare file, restituisce le…
Comprehensive pre-ship review of all changes since the last deploy or a specified commit. Walks correctness, atomicity/races, error handling, data-store hygiene, security, type safety, tests, integration, performance, observability, and any project-specific invariants. Use after any sprint and always before deploying.
Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API.
A proxy agent for a debate command that sends a debate position to an external AI command-line tool and forwards the response to the team. It supports several external assistants, including Codex, Gemini, Qwen, Pi, and Kimi.
Multi-depth research agent with configurable intensity. Use for any research task — from quick lookups to nuclear-level exhaustive investigations. Specify depth in the prompt: surface, basic, deep, in-depth, ultra, nuclear, overkill.
Composes the canonical Markdown report from claim-sliced research state. Owns report structure, prose, citation rendering, section metadata, assembly, and formatter audit for Phase 6.
Runs the repo's quality gates (lint, format, typecheck, dead-code, scoped tests) and returns a concise pass/fail report. Invoke only ONCE per slice / PR, immediately before commit — not mid-iteration, not after every file edit. Before delegating, the caller should run the project's auto-formatter on touched files…
Use this agent to audit documentation accuracy and git hygiene on any project. Cleans up plan files committed by mistake, verifies .gitignore coverage, checks README and CLAUDE.md accuracy against actual project state, and optionally verifies URLs match canonical domains. Examples: "Run docs-checker" — full audit "Run…
Senior software architect for design decisions, trade-off analysis, and architectural review. Use when evaluating a design proposal, choosing between approaches, writing an ADR, reviewing system boundaries, or when /lead encounters a Complex task in Phase 0.
Use this agent to trace a reported symptom BACKWARD through the dataflow to the site that originates it, verify the load-bearing facts against primary sources, and terminate in an attributed disposition — root cause, fix-owner, and ticket action — not just an investigation write-up. Combines the SRE reflex (start from…
Award-grade frontend ART + TECHNICAL DIRECTOR and orchestrator for the Atelier suite. Takes a single brief and returns a finished, premium, production-grade WEBSITE by running the image-first "design-then-code" pipeline across a specialist team (atelier-design-lead → atelier-build-engineer → atelier-ship-reviewer)…
Use this agent for Step S.6.4 - Code Review.\n\nPerforms an independent code review of the current phase's changes, checking for bugs, logic errors, security issues, and adherence to project conventions.\n\nExamples:\n\n \nContext: Step S.6.4, no external reviewer configured.\n\nuser: "Review the code changes for this…
★not rated 2 7mo agoA194 tokens
originalMIT
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: