Route implementation work-orders to Kimi k3 lanes via the Kimi Code CLI; Claude specs, orchestrates, reviews, verifies. Use when a task is a frozen-spec build, mechanical migration, test fill, bulk sweep, or CI fix — anything that reads as a work order rather than a design problem.
COMPLETENESS SEAT. Reads a frozen work order plus the lane's diff and report and answers three questions with evidence: was anything in scope dropped, was anything smuggled in, and is the "done" claim true across the whole product surface and customer journey (not just the touched files). Also the overengineering…
DESIGN SEAT for member-surface waves. Judges rendered screens and customer-visible copy against product dialect, decision economics (one decision, one gesture, evidence collapsed), copy humanity, card excerpt discipline, the ICP lens (trades owner on a phone in a truck) and the sauce (action-not-dashboards). Records a…
Cheap read-only repo and docs sweeper. Use for "where does X live", inventories across many files, capability checks, doc-currency audits, and any bulk reading where the caller needs the conclusion, not the file dumps. Returns file:line evidence, never opinions without a pointer.
Browser-and-MCP verification seat. Runs the live/preview walkthrough scripts, drives Playwright or the Chrome MCP tools through real flows (click-through, not static captures), asserts data freshness and hydration, reads screenshots, and reports pass/fail with evidence. Use for post-deploy films, click-through gap…
Route implementation work-orders to GPT-5.6 lanes via Codex; Claude specs, orchestrates, reviews, verifies. Use when a task is a frozen-spec build, mechanical migration, test fill, bulk sweep, or CI fix — anything that reads as a work order rather than a design problem.
Build and verify Meta (Facebook/Instagram) ad campaigns end to end via the Marketing API — account/app/system-user permission chain, Special Ad Category constraints, crop-safe story creative, campaign creation, and conversion tracking that is actually proven to work. Use when launching or debugging Meta campaigns…
Productionization loop for any product repo — classify the lane (rail / surface / activation), fix the proof column, ONE review pass, scripted path to production, done = live with a receipt. Use whenever a feature is being built for a real customer; use instead of ad-hoc review rounds.
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: