re0-loop

1Run a long project through repeated laps of the coil cycle so learning compounds and code is free to die.
2 
3## Goal
4 
5Keep a long project moving through repeated turns so learning compounds and piling up code never passes for progress. Use it on long agentic projects where progress must be measured by quality-cleared output rather than time or feature count. Progress counts only as quality-cleared templates, reusable platform modules, and anti-patterns eliminated in later cycles; never hours, files, panels, or features.
6 
7Each lap runs this cycle:
8 
9```text
10FRAME -> BUILD -> DRIVE -> RE0-MEMO -> HATE -> RE0-WORK -> BUILD AGAIN
11```
12 
13## Workflow
14 
15Run the steps in this order.
16 
171. **Frame.** Write the thesis and the quality gates the lap will be judged against.
182. **Build.** Build one complete vertical slice.
193. **Drive.** Drive the slice through its real surface, picked by artifact: a browser for web apps, HTTP for API contracts, desktop UI automation for desktop apps, and the CLI only for data-shaped artifacts. Capture what the drive shows as the lap's evidence.
204. **Memo.** Call the Skill tool with "re0-memo" to extract lessons, anti-patterns, and next-cycle gates from the lap. The memo lands where that skill's own contract puts it.
21…