How do I install the Re0 Loop skill?

Run npx skillmds@latest add lilmgenius/re0-loop in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Re0 Loop safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Re0 Loop?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Re0 Loop free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Re0 Loop?

lilmgenius (@lilmgenius) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Re0 Loop by lilmgenius — Agent Skill

Name: Re0 Loop
Rating: 4.2 (5 reviews)
Author: lilmgenius

Re0 Loop

Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.

lilmgenius a5ccc73 2.3 KB Updated Sep 9, 2026

File contents

Run the cycle so learning compounds and code accumulation does not masquerade as progress.

Goal

re0-loop keeps a project moving through repeated turns:

FRAME -> BUILD -> DRIVE -> RE0-MEMO -> HATE -> RE0-WORK -> BUILD AGAIN

The unit of progress is not hours, files, panels, or features. It is the count of quality-cleared templates, reusable platform modules, and anti-patterns eliminated in later cycles.

Workflow

Frame the thesis and quality gates.
Build one complete vertical slice.
Drive it through the real surface: browser for web apps, HTTP for API contracts, computer-use for desktop apps, and CLI only for data-shaped artifacts.
Run re0-memo to extract lessons, anti-patterns, and next-cycle gates.
Decide whether the next pass iterates in place or uses re0-work; when that call or the next move is unclear, nba reads the cycle state and returns the single next action.
Kill the next plan before build: use the project's adversarial review skill or a human-invoked attack when that skill is user-only.
Version only templates or modules that clear their gates.

Rules

Tests are supporting evidence, not the gate; every turn needs a real-surface proof sized to the artifact.
Do not widen before the core loop clears.
Do not confuse generated variety with structural variety. If many outputs converge to the same shape, the cycle failed the variety gate.
Preserve negative corpus so later cycles can prove the same anti-pattern is gone.
Let code die. A restart that preserves the right lessons is progress.
Stop a lap when no outside truth enters; add evidence before another internal pass.

Verification

Before finishing a lap:

The real surface was driven and evidence was captured.
The re0-memo names at least one lesson, anti-pattern, or gate that affects the next pass.
The keep/iterate/re0-work decision is explicit.
Any version label belongs only to a quality-cleared template or module.

---name: re0-loopdescription: Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.--- Run the cycle so learning compounds and code accumulation does not masquerade as progress. ## Goal `re0-loop` keeps a project moving through repeated turns: ```text FRAME -> BUILD -> DRIVE -> RE0-MEMO -> HATE -> RE0-WORK -> BUILD AGAIN ``` The unit of progress is not hours, files, panels, or features. It is the count of quality-cleared templates, reusable platform modules, and anti-patterns eliminated in later cycles. ## Workflow 1. Frame the thesis and quality gates. 2. Build one complete vertical slice. 3. Drive it through the real surface: browser for web apps, HTTP for API contracts, computer-use for desktop apps, and CLI only for data-shaped artifacts. 4. Run `re0-memo` to extract lessons, anti-patterns, and next-cycle gates. 5. Decide whether the next pass iterates in place or uses `re0-work`; when that call or the next move is unclear, `nba` reads the cycle state and returns the single next action. 6. Kill the next plan before build: use the project's adversarial review skill or a human-invoked attack when that skill is user-only. 7. Version only templates or modules that clear their gates. ## Rules - Tests are supporting evidence, not the gate; every turn needs a real-surface proof sized to the artifact. - Do not widen before the core loop clears. - Do not confuse generated variety with structural variety. If many outputs converge to the same shape, the cycle failed the variety gate. - Preserve negative corpus so later cycles can prove the same anti-pattern is gone. - Let code die. A restart that preserves the right lessons is progress. - Stop a lap when no outside truth enters; add evidence before another internal pass. ## Verification Before finishing a lap: 1. The real surface was driven and evidence was captured. 2. The re0-memo names at least one lesson, anti-pattern, or gate that affects the next pass. 3. The keep/iterate/re0-work decision is explicit. 4. Any version label belongs only to a quality-cleared template or module.

Frequently asked questions