Throw an AI dev at a problem and have it own the outcome. Five Opus agents (router, scout, worker, critic, fresh-eyes) collaborate to investigate, plan, execute, and verify — SSH into systems, spin up infra, edit code, ship features, debug deploys, get airgap bundles working. Worker self-switches between investigating.
★not rated 2 11d agoA
tokens not measured
originalMIT
A mini-foundry — the build-verify-fix engine without the MCP server or the planning interview. You bring a structured spec (requirement IDs + acceptance criteria); crucible builds it and refuses to let it drift. /crucible:build decomposes the spec into units with DISJOINT file ownership, shows you the split.
★not rated 2 11d agoA
tokens not measured
originalMIT
De-AI My UI — strips the tells that make an interface read as 'made by an AI in Tailwind.' Two modes, one shared catalog of 19 slop signatures (font chaos, the purple-on-black AI palette, gratuitous parallax, weird hovers, default/neon gradients, neon gradient borders, recycled stock icons, everything-is-a-24px-card.
★not rated 2 11d agoA
tokens not measured
originalMIT
End-to-end test authoring and maintenance for web apps via Playwright + Playwright MCP. Claude drives a real browser, reads the accessibility tree, and emits .spec.ts files that pass — then keeps them passing. /e2e:init scaffolds Playwright in the cwd and registers the MCP server. /e2e:write drives the browser.
★not rated 2 11d agoA
tokens not measured
originalMIT
Codebase-aware specification engine for Claude Code. Runs parallel codebase research, then a grounded interview that captures implicit facts as A-AUTO-NNN entries, emits typed Global Invariants / State Transitions / Contracts tables, runs an adversarial spec review at R3.5, then writes a foundry-ready spec with…
★not rated 2 11d agoA
tokens not measured
originalMIT
Autonomous build-verify-fix loop for Claude Code. Reads a Forge spec, decomposes it into castings with pre-authored teammate prompts, validates through an 11-dimension F0.9 gate (including F0.7 intent-carrier coverage), builds in parallel waves with server-side evidence re-execution and per-requirement-ID binding…
★not rated 2
changed 13d agoA
tokens not measured
originalMIT
Macro-architecture / design-cohesion review — the senior-engineer 'is this shaped right or accreted?' critique, not bug-hunting or lint. Reads a codebase like Holmes reads a room: deduces the real design problem from the detail that's out of place. /holmes:review runs a Workflow engine that builds a grounded s.
★not rated 2 11d agoA
tokens not measured
originalMIT
Careful low-risk codebase cleanup across 7 focused tracks: deduplication, type consolidation, dead code removal, circular dependency untangling, type strengthening, error-handling cleanup, and deprecated/AI-slop removal. Each track inspects, writes a critical assessment, ranks proposed changes by confidence, and…
★not rated 2 11d agoA
tokens not measured
originalMIT
Always-on response shaping. A SessionStart hook loads a 10-rule ruleset into every new session — first line is the action, numbered multi-step work, restate where we are each turn, one concrete next action, concrete time estimates, visible wins, flat tone on failure, lists capped at 5, no preamble/recap/sign-off …
★not rated 2
changed 10d agoA
tokens not measured
originalMIT
Experiential UX review that drives the RUNNING app as a real user — not a code read. Reading source is a code review and structurally cannot find experience defects (a mode that doesn't do what its label claims, an overlay anchored to the wrong thing, a feature that silently breaks in one state, a table-stakes…
★not rated 2 11d agoA
tokens not measured
originalMIT
Generate really good dynamic Workflow scripts on demand. /weave:make classifies the task into an orchestration archetype (understand / design / review / research / migrate / generic), picks the right fan-out topology (pipeline by default, barrier only when a stage genuinely needs all prior results), and authors.
★not rated 2 11d agoA
tokens not measured
originalMIT
Documentation for the person who has to use the thing, held to the bar of something you could hand a customer without reading it first. Every page declares who it is for, and that decides what the page may be about: a page for a user names screens, buttons and what the product gives back, never a symbol, a route or…
★not rated 2 11d agoA
tokens not measured
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: