🌀 Superloopy

Loop engineering for Codex, Claude Code, and Google Antigravity. Type loopy <task> — an agent does the work, proves each piece with real evidence, and only then says it's done.

English · 한국어 · 中文(简体) · 日本語 · Español

     

the crew — optional subagents, one job each

Use it

After installing, type your task in Codex, Claude Code, or Antigravity with a leading loopy:

loopy add the payments module

The agent plans it, proves each piece with a real file, and reports back — you don't run any commands yourself. The packaged Stop hook stays quiet unless SUPERLOOPY_STOP_HOOK=on. Set SUPERLOOPY_CALQUE_NUDGE=on to get an advisory note at your next prompt when the previous Korean reply carried an English calque such as 조용히 실패 or 우아하게 종료.

Why Superloopy?

Superloopy is for Codex, Claude Code, and Antigravity work where "done" needs to mean more than a confident status sentence.

• Evidence-first: every pass points at a real artifact under .superloopy/evidence/.
• Lightweight by default: one small CLI, repo-local state, zero runtime dependencies.
• Agent-friendly: skills, hooks, and optional crew lanes guide the agent without hiding the final gate.

Guarantee scope. Command-backed criteria are the strong guarantee: at completion Superloopy re-runs each command in-process and requires it to reproduce, so a stale or fabricated pass cannot reach "done". Manual (commandless) criteria are verified as a non-empty evidence artifact plus auditor/human judgment — their correctness rests on review, not the deterministic re-run.

Skills

Superloopy keeps the command layer small. Skills carry the specialist workflow: when to use it, what the agent should inspect, and what proof must be left under .superloopy/evidence/.

Skill	Use it when	What it produces
superloopy-loop	You type loopy <task> or loopy team <task> for a full loop; use loopywork, lpy, or $lpy for guidance-only context.	Full loops produce direct, concise, complete progress and final responses alongside a lightweight plan, proof, quality gate, and final evidence report. Exact English/Korean controls affect only the current incomplete loop; new loops reset enabled. Guidance aliases do not mutate state.
superloopy-doctor	You diagnose install, wrapper, plugin cache, hook/bootstrap, agent, Codex/Claude Code host wiring, or stale-version problems.	A read-only health report with wrapper/cache/version evidence, failing checks, and the exact repair command to run only if approved.
superloopy-research	You explicitly invoke Codex $superloopy:superloopy-research or Claude Code /superloopy:superloopy-research, or start the research task with a leading loopy/루피 (such as loopy research). Plain research, investigate, or summarize requests do not activate it.	Research axes, expansion waves, a verdict on every retrieval, graded and dated sources, a priced claim ledger, verification notes, and a cited synthesis artifact.
superloopy-backend	You explicitly invoke Codex $superloopy:superloopy-backend or Claude Code /superloopy:superloopy-backend for backend, data, migration, or runtime database-agent work, or start that work with a leading loopy/루피. Plain backend or database vocabulary does not activate it.	A stack-neutral context card, defined contracts, least-privilege data safeguards, TDD, migration and runtime-agent boundaries, and command-backed operational evidence.
superloopy-clone	You ask for loopy clone, authorized website cloning, rebuilding, migration, or pixel-focused page recovery.	Browser captures, page topology, design tokens, asset inventory, implementation notes, build output, and visual QA evidence.
superloopy-frontend	You explicitly invoke Codex $superloopy:superloopy-frontend or Claude Code /superloopy:superloopy-frontend for supported screen-based application UI across browser-hosted Web (public, authenticated, private/internal, installed PWA, or extension), interactive deployed content-led Web (campaign, publication, or landing experiences with a user journey), desktop, mobile/tablet, embedded/hybrid clients, custom-rendered UI, Qt, or mixed targets, or start that work with a leading loopy/루피. Plain UI, platform, or framework terms do not activate it; TV, wearable, XR, automotive, game UI, TUI, static media/document artifacts, and non-UI work stay excluded.	One shared UX contract plus platform/composition routes. Evidence is proportional to changed claims and independently covers each browser, native target/shell, renderer, and mixed target. Standalone runs retain run-scoped receipts; active loops bind them to the goal and criterion.
humanize-korean	Use when Korean users ask to remove AI tone, fix 번역투, or make Korean text sound human without changing facts.	Owns Korean naturalness, including semantic review of misplaced modifiers and the P-family calque rules (조용히 실패, 우아하게 종료, 단일 진실 공급원). It writes final.md, summary.md, and audit.json; in Superloopy loops it records evidence under .superloopy/evidence/humanize-korean/.
i-have-adhd	You explicitly invoke Codex $superloopy:i-have-adhd or Claude Code /superloopy:i-have-adhd, or a leading loopy/루피 brief directly asks for ADHD-friendly, action-first, one-step, or easy-to-scan output. Writing style alone never activates it.	Shapes progress updates so the next action stays visible. It does not create a Superloopy evidence artifact or weaken planning, safety, validation, or completion gates.
say-it-straight	Explicit Codex $superloopy:say-it-straight or Claude /superloopy:say-it-straight for direct, concise, natural prose and supplied task artifacts; never activates from writing style alone. Full Loopy progress/final output is direct by default, with exact English/Korean controls limited to the current incomplete loop.	Explicit artifact ed