SpectraFit-Core

Auto-enforcing, self-optimizing hardening loop that walks a project's value stream — its ordered chain of services/packages and the wires (data contracts) between them — fixing one gap per stage and refusing to advance past a broken wire (the andon rule). A pass is one traversal; a cycle is the converged run of several passes; a hard fix triggers a sub-cycle that backtracks upstream to re-verify; in fix mode it auto-assigns subagents and MCPs to go faster. Language- and platform-agnostic. Always use when the user wants to: "harden my pipeline", "self-optimization loop", "scan for gaps and fix them in order", "wired test", "can service A deliver to service B", "value stream", "attack the bottleneck", "split fast vs slow (Playwright) checks", or any request to autonomously iterate over a multi-service codebase closing gaps while keeping each handoff proven. Also trigger on: contract test, Jidoka, Theory of Constraints, error budget, PDCA, harden faster.

Fix the class, not the instance. A TDD-sibling discipline for working at the right altitude: before patching any reported defect or gap, reconstruct the system model, name the invariant it violates, enforce that invariant as a check, and sweep every sibling — so the next instance never needs a human to point at it. Use whenever a bug/gap is REPORTED (especially when a human noticed it), when reviewing "is this complete?", when the same kind of bug keeps recurring, or when you catch yourself about to make a one-line fix to a reported symptom. Trigger language: "fix the class not the instance", "are we fingerpointing", "see the big picture", "what invariant does this violate", "is this a one-off?", "did we miss the system view", "stop patching symptoms", "this keeps happening". DO NOT use to write the test itself (that is superpowers:test-driven-development — this skill decides WHAT invariant the test should pin) or to explore an unbuilt design (that is superpowers:brainstorming).

Conductor for the Rust crates/ stream. Diagnoses + fixes kernels, solvers, workspace layout, PyO3 binding surface, and any other code under crates/. Absorbs spectrafit-solver, spectrafit-bindings, spectrafit-scaffold, and rust-model-scaffolder — their specialist content lives in references/. Use when a task touches Rust kernels, the LM/TRF/dogleg/Newton-CG solver family, the ModelTypeStr enum, the pyo3 ABI, or the crate workspace. Also when the user pastes Rust or PyO3/maturin code and asks "is this idiomatic?", "review this Rust", or "check my PyO3 code". Composes with superpowers:test-driven-development and superpowers:verification-before-completion. Serena-first.

Generator of skills, agents, hooks, prompts, and instructions for the universal-creator framework. Used when the catalog needs to grow. Absorbs skill-generator, agent-generator, hook-generator, prompt-generator, and instruction-generator — their specialist content lives in references/. Use when the user asks to scaffold a new skill, write a sub-agent definition, design a hook configuration, draft a one-shot prompt, or create workspace instruction files. Composes with superpowers:writing-skills and superpowers:writing-plans.

Conductor for the Python python/ stream. Owns Pydantic schemas, the oracles benchmark engine, the BenchReport contract, test coverage, and Python architecture decisions. Absorbs spectrafit-schemas, spectrafit-tests, spectrafit-tdd, python-arch-proposer, and python-pattern-advisor — their specialist content lives in references/. Use when a task touches python/oracles/, python/spectrafit_core/, the Pydantic models, the benchmark engine, the contract, or pytest. Also when the user pastes Python and asks "is this Pythonic?", "review this Python", or "how can I improve this code?". Composes with superpowers:test-driven-development and superpowers:verification-before-completion. Serena-first.

Five-voice quality council — Jobs (reduction), Ive (craft), Dye (system hierarchy), Tog (usability), Kare (metaphor). Convened on stuck wires, design questions, and presentation polish. Absorbs one-more-thing, boring-to-brilliant, cupertino-council, and evolutionary-platform-thinking — their specialist content lives in references/. Use when the user says "it feels off", "design from first principles", "what's missing", "make it memorable", "elevate this", "Time Machine treatment", "Apple-style", "future-proof this", "Vista trap", or when a tri-stream cycle's stuck-mode escape hits rung 3. Composes with superpowers:brainstorming.

Use FIRST when starting any goal or hitting any bug/failure — holds the trunk (the goal), classifies every find, dispatches instance bugs to systematic-debugging and class bugs to big-picture-driven-development, and forces convergence via a committed trunk ledger. Use before systematic-debugging or BPDD.

Crosscut verification conductor — closes the oracle gap for scientific / numerical software. Owns ground-truth V&V, NIST StRD fixtures, benchmark scenarios, and DAG validation across the three streams. Absorbs ground-truth, nist-strd-runner, benchmark-scenario-generator, and dag-validator. Use when validating against a gold standard, closing the oracle gap, auditing benchmark trustworthiness, running NIST StRD harnesses, generating realistic benchmark scenarios, or checking the Rust crate DAG for cycles. Composes with superpowers:verification-before-completion. Serena-first for code.

Conductor for the web/ stream — the Vite + React dashboard that renders the BenchReport contract. Owns panels, render-truth surfaces, and the four-step verify cycle (vitest → bench → gate → playwright). Absorbs spectrafit-devboard and spectrafit-benchmark (web side); their specialist content lives in references/. Use when a task touches web/src/, panel registries, plot mounts, screenshots, dashboard export, or the manuscript-review gate. Composes with superpowers:test-driven-development and cupertino-council. Serena-first.