zwrose

configure

"Use to set up, fix, view, or tune a project's superheroes calibration — the single front door for superheroes configuration. Lets you see the whole project's calibration on one screen, change a setting, or move a project between in-repo and out-of-repo storage. Not for code review, technical planning, or running the build loop."

zwrose 1 Updated 4w ago

Resources

1
GitHub

Install

npx skillscat add zwrose/superheroes/configure

Install via the SkillsCat registry.

SKILL.md

This skill speaks in host-neutral actions. Resolve them to your runtime's tools by reading the host tool map at ${CLAUDE_PLUGIN_ROOT}/hosts/<your-host>-tools.md (the leading variable is this plugin's root directory) — claude-tools.md on Claude Code, codex-tools.md on Codex.

configure

The single owner-facing front door for a project's superheroes calibration. Run it and it
senses the project's state and routes into one of three paths — set up (nothing
configured yet), fix (configured but needing repair), or see & tune (configured and
healthy). It is the one calibration command an owner is told to run; the per-hero *-init
skills are now reached only from within it (CONVENTIONS §2.4 / §3.3).

This skill is a thin conductor over tested libs — it never moves a file or computes a key
itself. The destructive in-repo↔global storage-mode flip and first-push rebind (and
their crash recovery) live entirely in lib/mode_migrate.py.

Step 1 — Recover first (every run)

Before sensing or rendering anything, settle any flip or rebind interrupted by an earlier crash —
this is what makes the storage switch safe. route/render are read-only and can
never be the recovery trigger.

ROOT_DIR="${CLAUDE_PLUGIN_ROOT}"
python3 -B "$ROOT_DIR/lib/mode_migrate.py" recover --cwd .

A recovered result means an interrupted flip was finished or backed out — note it for the
owner. While a migration is recovering, the passive drift nudge stays quiet (it is recovery in
progress, not drift).

Step 2 — Sense the state and route

ROOT_DIR="${CLAUDE_PLUGIN_ROOT}"
python3 -B -c "
import sys, json; sys.path.insert(0, '$ROOT_DIR/lib')
import configure_route
print(json.dumps(configure_route.route('.')))
"

Read the path and surface the plain-language reasons. There is no presence flag — the libs
always take the provisional / out-of-repo / strict posture, and storage is never flipped without
the owner's explicit authorization in this turn. The owner's-authorization rule is preserved but its shape
changed:
lib/mode_migrate.py no longer takes a presence boolean; it takes an explicit owner
authorization that defaults to refusing. configure passes that authorization only when the
owner asked for the migration in the current turn — the owner's words being the hearing event.
Then run the matching path:

  • set-up → follow ${CLAUDE_PLUGIN_ROOT}/skills/configure/reference/set-up.md.
  • fix → follow ${CLAUDE_PLUGIN_ROOT}/skills/configure/reference/fix.md.
  • view → follow ${CLAUDE_PLUGIN_ROOT}/skills/configure/reference/view-and-tune.md.

Cloud builds are set up in a sitting of their own. When the owner asks to set up cloud builds,
says "check again" after a cloud check, or asks for "setup text", follow
${CLAUDE_PLUGIN_ROOT}/skills/configure/reference/set-up.md § 6, whichever path the project routed to.

A run that only views an up-to-date project changes nothing. A provisional calibration
is confirmed only when the owner explicitly confirms it on the fix path — never by viewing.

Engine onboarding (Codex/Cursor per role — reviewer, implementer, brief-check reviewer, pilot;
availability, preference, show-authorization, test-dispatch) lives in set-up.md §4.5 and is
tunable via view-and-tune.md §2. Model-tier overrides (including explicit fable) are also a
view-and-tune.md §2 tune item.

Common mistakes

Mistake Fix
Skipping the Step-1 recover A crashed flip is invisible until recover runs first — run it every time.
Re-deciding a recorded storage mode during set-up/fix The mode is sticky; only the explicit, confirmed flip on the tune menu changes it.
Flipping storage unattended A storage flip happens only with the owner's explicit authorization in the current turn; without it the flip is recorded un-applied and the run continues.
Editing the owner's build config to add a verify command Propose it for the owner to add — configure never edits their build config.