Claude Skills by stuinfla

The autonomous build contract, out of the box — "/brain-build <what you want>" activates the disciplined hands-off build power users used to hand-write a standing prompt for. Use when the user says "/brain-build", "brain build", "build this autonomously", "build this hands-off", "loop until it's done", "don't ask me, just build it", or asks for an unattended/self-grading build. Phase-gated per rUv's SPARC, self-verified and self-graded /100 against a per-phase rubric (below 95 → fix and regra...

Open the RuvNet Brain Console for "/rvbc", "/rvcb", "/brain-console", or "/ruvnet-brain:configure". Use when the user asks to open, configure, inspect, or view the Brain Console. It opens the live local page in the background; the page is read-only until the user clicks a clearly explained, reversible action.

Metaprompting assistant — "/brain-prompt <rough idea>" turns a rough ask into "the right prompt": a complete, tuned master prompt with SPARC phases, per-phase rubrics, standing rules, and cost guardrails, ready to paste or run. Use when the user says "/brain-prompt", "brain prompt", "write me the right prompt for this", "turn this idea into a proper prompt", "metaprompt this", "what should I actually ask for", or hands over a vague one-liner they want expanded into a disciplined build brief. ...

Score ANY repository 0-100 across 8 dimensions using the exact evidence-or-it-didn't-happen scorecard RuvNet-Brain applies to itself. Use when the user says "score this repo", "score my repo", "scorecard", "brain-score", "how good is this codebase", "rate this project", "audit quality", or asks for an honest 0-100 quality assessment of a repository. Every deduction must cite evidence from the actual repo; a known architectural flaw caps its dimension at ≤70; a "what I did NOT test" section is...

Fail-closed exact-artifact release and deployment authority. Use before saying a release is ready, pushing a release commit, publishing npm packages, creating GitHub releases, deploying production, closing release-blocking issues, or claiming all gates are green. Requires clean immutable lineage, zero open issues, exact-SHA GitHub success, nonzero no-skip QE, packed-artifact host tests, installed Brain/RVF proof, independent graders, and post-publication byte verification.

Use whenever a task involves the RuvNet / rUv ecosystem (Ruflo, RuVector/RVF, AgentDB, RuLake, RuView, agentic-flow, agenticow, SAFLA, QuDAG, DAA, ruv-fann, FACT, SynthLang, SPARC, or any of rUv's 20+ repos) — OR whenever you are asked to build, implement, add, refactor, enhance, or fix ANYTHING, in any repo, on any stack. Grounds every RuvNet capability claim in real source via search_ruvnet before asserting, actively considers the FULL toolkit (not just the 2-3 most-cited tools) for whichev...

Open the RuvNet Brain Console in Claude Code and Codex when the user says "Configure RuvNet Brain", mentions "rvbc", asks for the Brain Console, or wants to configure or inspect RuvNet Brain. Claude Code supports /rvbc; Codex invokes the native $ruvnet-brain:rvbc skill.

Show the MetaHarness routing ledger inline — which model each task was routed to, what it displaced, and the percentage + dollars saved — plus the learned router's training state. Use when the user says "savings", "show my savings", "metaharness report", "metaharness/report", "routing report", "routing receipts", "who is the router choosing", "how much has routing saved me", "is the meta harness working", or "show me the routing". All numbers come from the real receipts log; never fake or ext...

Explain what is new in the installed RuvNet Brain release from live version metadata and the curated release notes. Use for "/whats-new", "what's new", "what changed", "new release", or "show me the latest Brain improvements". Never claim a 4.0 version unless the installed version actually starts with 4.